Examkin

Question

Difficulty: MediumIdentify design principles of the AWS Cloud

A healthcare company is designing a system on AWS to process patient telemetry data from wearable devices. The system must ingest incoming data streams, store them securely, and automatically generate reports when new data arrives. The architecture should minimize operational overhead and ensure that a failure in the reporting component does not disrupt the ingestion of patient data.

Which of the following architectural decisions align with AWS Cloud design principles to meet these requirements? (Select TWO.)

  1. Deploy Amazon Simple Queue Service (Amazon SQS) to decouple the telemetry data ingestion layer from the report generation process.Answer
  2. Use AWS Lambda to run the report generation code instead of provisioning and managing persistent virtual servers.Answer
  3. C
    Design the report generation service to communicate synchronously with the ingestion service via direct API calls to guarantee real-time delivery.
  4. D
    Manually scale a fixed fleet of Amazon EC2 instances to the maximum expected peak capacity to handle ingestion spikes.
  5. E
    Consolidate the ingestion and reporting software into a single monolithic application on a large EC2 instance to reduce network latency.

Answer

Deploying Amazon SQS to decouple the layers and using AWS Lambda to run report generation code instead of managing servers.
The correct options are deploying Amazon SQS to decouple the ingestion layer from the report generation process and using AWS Lambda to run report generation serverlessly. The SQS option demonstrates loose coupling, which prevents failures in downstream components from affecting upstream ingestion. The Lambda option aligns with the 'services, not servers' principle, eliminating server administration tasks and scaling automatically.

Step-by-Step Solution

1
Analyze the requirements to identify the core AWS design principles needed.
The requirements ask to decouple components (preventing reporting failures from affecting ingestion) and minimize operational overhead (avoiding server management).
This maps directly to the design principles of loose coupling and using managed services (services, not servers).
2
Evaluate the architectural options against the design principle of loose coupling.
Using an asynchronous queue like Amazon SQS decouples the services, ensuring that a failure in report generation doesn't block ingestion. Direct API calls (synchronous) or monolithic deployment violate this principle.
Loose coupling ensures components can scale and fail independently.
3
Evaluate the architectural options against the design principle of 'services, not servers' or reducing operational overhead.
Using AWS Lambda allows running code serverlessly without managing underlying operating systems or virtual instances. Managing or over-provisioning EC2 instances manually violates this principle.
Using managed services reduces administrative burden and increases agility.

Key Concept

AWS Cloud design principles such as loose coupling, design for failure, and services not servers.
Rate this question

Topics

Identify design principles of the AWS Cloud

More questions from this topic