Question

Difficulty: MediumCloud Architecture and Deployment Models

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

1
Analyze the hardware and control requirements for the database scenario.
Identified direct hardware control, hypervisor management, and physical isolation as characteristics of Private Cloud (IaaS).
IaaS provides maximum architectural control to the organization, while private deployment guarantees dedicated isolation.
2
Evaluate the management boundary for web services with managed runtime and OS patching.
Identified abstraction of OS and runtime environment as characteristics of PaaS.
Under PaaS, the provider handles infrastructure maintenance and middleware, leaving application code to the consumer.
3
Examine the operational mechanics of transient event-triggered microservices.
Matched zero-server management and event execution to Serverless (FaaS).
FaaS abstracts server instances completely, executing logic on demand in response to events.
4
Determine the cloud deployment model for joint industry collaboration under common compliance standards.
Matched shared infrastructure between partner institutions to Community Cloud.
Community clouds are designed for multi-tenant access restricted to organizations bound by shared mission goals or compliance standards.

Key Concept

Cloud Deployment Models and Shared Responsibility Boundaries
Rate this question