Question

Difficulty: HardAWS Global Infrastructure

An organization is designing a high-frequency financial analytics platform. The architecture has two primary requirements:

1. The relational database tier must support synchronous replication and automatic failover across physically separated facilities while remaining within a single national boundary for compliance.
2. The data ingestion compute tier must run as close as possible to users in metropolitan areas that do not host a full AWS Region, to minimize network latency.

Which of the following deployment strategies should the organization use to meet these requirements? (Select TWO.)

  1. A
    Deploy the relational database tier across multiple AWS Regions to achieve synchronous replication.
  2. Deploy the relational database tier across multiple Availability Zones in a single AWS Region.Answer
  3. Deploy the data ingestion compute tier in AWS Local Zones located in the targeted metropolitan areas.Answer
  4. D
    Deploy the data ingestion compute tier in AWS Edge Locations using Amazon CloudFront.
  5. E
    Deploy the relational database tier in AWS Wavelength Zones to guarantee ultra-low latency.

Answer

Deploying the relational database tier across multiple Availability Zones in a single AWS Region, and deploying the data ingestion compute tier in AWS Local Zones located in the targeted metropolitan areas.
To achieve high availability with synchronous replication and automatic failover within a single national boundary, the database must be deployed across multiple Availability Zones within a single AWS Region. To deliver ultra-low latency compute to metropolitan areas without a local AWS Region, AWS Local Zones should be utilized to host the data ingestion tier close to the end-users.

Step-by-Step Solution

1
Analyze database requirements
Identified that synchronous replication, physical isolation, and data residency require a multi-AZ deployment within a single AWS Region.
Regions offer data sovereignty boundaries, and Availability Zones within a Region provide the low-latency physical isolation necessary for synchronous database replication.
2
Analyze compute placement requirements
Identified that low-latency compute in metropolitan areas without a full Region requires the use of AWS Local Zones.
AWS Local Zones extend AWS Regions to bring compute resources closer to metropolitan areas, minimizing latency for local end-users.

Key Concept

Understanding the distinct use cases and architectural properties of AWS Regions, Availability Zones, Local Zones, and Edge Locations.
Rate this question