Examkin

Soru

Zorluk: Çok zorIdentify design principles of the AWS Cloud

An organization is designing a financial transaction processing pipeline on AWS. The system must handle highly unpredictable transaction volumes, ensure that downstream failures in third-party settlement APIs do not disrupt upstream transaction ingestion, and allow developers to test changes in isolated environments that match production scale without incurring permanent infrastructure costs. Which of the following design choices align with AWS Cloud design principles to meet these requirements? (Select TWO.)

  1. Decouple the ingestion layer from the settlement processing layer using message queues to ensure downstream API failures do not block transaction intake.Cevap
  2. Use infrastructure as code to provision and terminate temporary, full-scale testing environments on demand, rather than keeping a dedicated staging environment active.Cevap
  3. C
    Consolidate the ingestion and settlement layers into a single large Amazon EC2 instance to minimize latency and simplify the network architecture.
  4. D
    Pre-provision the maximum required compute capacity for the ingestion layer based on historical peak transaction volume to prevent scale-out delays.
  5. E
    Rely on AWS to automatically manage and apply operating system patches for all customer-managed Amazon EC2 instances running the ingestion application.

Cevap

Decouple the ingestion layer from the settlement processing layer using message queues to ensure downstream API failures do not block transaction intake; and Use infrastructure as code to provision and terminate temporary, full-scale testing environments on demand, rather than keeping a dedicated staging environment active.
The correct choices are to decouple the ingestion and settlement layers using message queues, and to use infrastructure as code to manage temporary testing environments. Using message queues allows the system to achieve loose coupling, meaning the components act independently, and downstream failures do not prevent upstream data ingestion. Utilizing infrastructure as code to spin up and tear down test environments implements the principle of disposable resources, allowing the organization to test at scale only when needed without paying for idle assets.

Adım Adım Çözüm

1
Identify the system requirement for handling downstream failures without affecting ingestion.
Downstream settlement failure isolation is needed, indicating a loose coupling and design for failure architecture.
This isolates independent components so that a failure in one does not cascade.
2
Identify the requirement for testing at scale without permanent costs.
The environments must be treated as disposable resources, created on-demand and terminated when finished.
This aligns with the principle of disposable resources, replacing fixed staging servers with temporary ones.
3
Evaluate the architectural options to determine which align with these cloud design principles.
Decoupling with message queues and using infrastructure as code to provision/terminate environments on-demand are selected.
These directly manifest the target AWS design principles.
4
Eliminate choices that represent anti-patterns.
Consolidating layers is a monolithic anti-pattern; pre-provisioning capacity ignores elasticity; expecting AWS to patch EC2 OS violates the shared responsibility model.
These options run counter to core AWS cloud concepts and security frameworks.

Anahtar Kavram

AWS Cloud Design Principles (Loose Coupling, Disposable Resources)
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Identify design principles of the AWS Cloud

Bu konudan daha fazla soru