An enterprise security architect is establishing operational boundaries across a multi-cloud enterprise ecosystem. Match each cloud security implementation task on the left with the corresponding cloud service model on the right.
- Configuring execution timeouts, API gateway triggers, and event-driven permissions for stateless microservices without managing any OS or web server.Function as a Service (FaaS) / Serverless
- Applying security updates to guest operating systems, configuring virtual network firewalls, and managing persistent block storage volumes.Infrastructure as a Service (IaaS)
- Enforcing enterprise data loss prevention (DLP) rules and tenant access control via API integrations for a vendor-hosted productivity suite.Software as a Service (SaaS)
- Managing application source code security, database table permissions, and runtime framework configurations while the underlying OS is patched by the cloud vendor.Platform as a Service (PaaS)
Answer
Task 1 matches Function as a Service (FaaS) / Serverless; Task 2 matches Infrastructure as a Service (IaaS); Task 3 matches Software as a Service (SaaS); Task 4 matches Platform as a Service (PaaS).
Each cloud service model defines a specific division of responsibilities under the Shared Responsibility Model: IaaS delegates OS, virtual network, and storage controls to the customer; PaaS delegates application runtime and database configuration to the customer while automating OS management; SaaS limits customer responsibility to data access and identity management; FaaS abstracts all infrastructure and server runtimes, focusing strictly on stateless event execution.
Step-by-Step Solution
Key Concept
Cloud Shared Responsibility Model across Service Models (IaaS, PaaS, SaaS, FaaS)