An enterprise security architecture team is evaluating cloud deployment and service models for a multi-cloud initiative. Match each operational requirement on the left with the most appropriate cloud architecture or service model on the right.
- Deploying a highly customized legacy database requiring direct control over hypervisor settings, hardware isolation, and dedicated host resources.Private Cloud (IaaS)
- Developing customer-facing web services where the cloud provider maintains the underlying runtime, operating system patching, and web server framework.Platform as a Service (PaaS)
- Executing transient, event-driven payment processing code that scales automatically without maintaining active server instances.Serverless (FaaS)
- Sharing a specialized regional threat intelligence pool co-hosted and governed by several partner financial institutions under common regulatory compliance standards.Community Cloud
Answer
1. Custom legacy database requiring physical host isolation -> Private Cloud (IaaS); 2. Web services with provider-managed runtime and OS patching -> Platform as a Service (PaaS); 3. Transient event-driven code execution -> Serverless (FaaS); 4. Co-hosted platform shared by partner financial institutions -> Community Cloud.
Matching each requirement accurately aligns business demands with cloud service abstraction boundaries. Private Cloud (IaaS) provides dedicated hardware control; PaaS offloads OS/runtime maintenance while hosting persistent apps; Serverless (FaaS) executes code transiently without server management; and Community Cloud serves multi-organizational groups sharing specific compliance and functional goals.
Step-by-Step Solution
Key Concept
Cloud Deployment Models and Shared Responsibility Boundaries