Question

Difficulty: HardCloud Architecture and Deployment Models

A regional health insurance organization is migrating its claims processing engine to a cloud provider using a Serverless Function-as-a-Service (FaaS) execution model connected to a managed Database-as-a-Service (DBaaS) backend. During a compliance audit, the security team is asked to document control ownership across the deployment layers. Which of the following statements correctly identifies the customer's operational responsibility in this deployment architecture?

  1. Managing application source code security, data classification, and fine-grained identity and access policies.Answer
  2. B
    Applying operating system security patches and kernel hotfixes to the instances executing the serverless functions.
  3. C
    Establishing physical perimeter defenses and microsegmentation for the physical hardware hosting the database service.
  4. D
    Configuring hypervisor isolation boundaries to prevent cross-tenant memory leakage between function executions.

Answer

The customer is responsible for managing application source code security, data classification, and fine-grained identity and access policies.
Under the cloud shared responsibility model for serverless (FaaS) and managed database (PaaS) architectures, the cloud service provider manages all underlying hardware, hypervisors, OS patching, and engine runtimes. The customer retains full responsibility for securing their application logic/code, classifying their data, and configuring identity and access management permissions.

Step-by-Step Solution

1
Analyze the specified cloud service models in the scenario
The architecture utilizes Serverless (FaaS) and Database-as-a-Service (DBaaS), both falling under Platform as a Service (PaaS) abstract execution models.
Determining the exact service model dictates the boundary line in the Cloud Shared Responsibility Model.
2
Evaluate cloud service provider (CSP) responsibilities for PaaS/FaaS
The CSP manages physical data centers, hardware, hypervisors, OS patching, database software engine maintenance, and runtime environments.
Abstracted environments offload infrastructure and host maintenance away from the customer.
3
Identify non-transferable customer responsibilities
Regardless of cloud abstraction, data ownership, identity management, access control configurations, and application code security always remain the responsibility of the cloud customer.
The customer owns customer data and the code deployed onto provider platforms.

Key Concept

Cloud Shared Responsibility Model in Serverless and PaaS Environments
Estimated Time:1m 40s
Rate this question