Question

Difficulty: MediumCloud Architecture and Deployment Models

Match each enterprise security management scenario to the cloud service model that reflects its allocation of customer responsibilities under the Shared Responsibility Model.

  • Managing virtual machine operating system patches, guest firewall rules, and persistent storage volume encryptionInfrastructure as a Service (IaaS)
  • Configuring application logic, database access controls, and custom API endpoints while the provider manages runtime binariesPlatform as a Service (PaaS)
  • Managing user identity governance, role-based permissions, and data loss prevention policies for a vendor-hosted turn-key applicationSoftware as a Service (SaaS)
  • Securing event-driven execution code and trigger definitions while the provider handles automatic container scaling and host OS managementFunction as a Service (FaaS)

Answer

Operating system patching and guest firewall configuration match Infrastructure as a Service (IaaS). Application logic and database access control configuration match Platform as a Service (PaaS). User identity governance and data loss prevention for pre-built applications match Software as a Service (SaaS). Event-driven code execution and trigger definitions match Function as a Service (FaaS).
Each cloud service model defines a distinct boundary of ownership under the Shared Responsibility Model: IaaS grants customer control over guest OS and virtual networking; PaaS isolates customer control to application logic and data schemas; SaaS restricts customer management to user access, data protection, and client devices; and FaaS delegates container scaling and OS maintenance to the provider while the customer provides serverless code functions.

Step-by-Step Solution

1
Analyze the customer control boundary for each administrative task scenario.
Tasks range from low-level OS management to high-level application access governance and serverless trigger setup.
The cloud shared responsibility model dictates customer responsibilities based on the abstraction layer of the chosen service model.
2
Associate lower-level infrastructure administration with compute-focused delivery models.
Guest operating system patching and virtual storage encryption belong to IaaS.
IaaS provides virtualized hardware resources where OS maintenance falls on the tenant.
3
Differentiate application runtime management from ephemeral execution.
Persistent application configuration maps to PaaS, while short-lived event-driven function management maps to FaaS.
PaaS abstracts OS management for hosted application frameworks, whereas FaaS abstracts long-running servers completely.
4
Identify complete vendor-hosted software management.
Turn-key applications where the customer manages only access permissions and data map to SaaS.
SaaS abstracts all infrastructure and software maintenance away from the cloud consumer.

Key Concept

Cloud Shared Responsibility Model across Service Models
Rate this question