Question

Difficulty: HardAWS Global Infrastructure

A startup is launching a real-time multiplayer gaming application. The architecture must satisfy three requirements:
1. Provide single-digit millisecond latency for compute workloads to users in a specific metropolitan area that does not have an AWS Region.
2. Provide high availability and fault tolerance for the central database, protecting against physical data center disasters.
3. Cache static game assets globally to reduce load times for international players.

Which of the following deployment strategies correctly leverage AWS Global Infrastructure components to meet these requirements? (Select TWO.)

  1. Deploy the latency-sensitive game server workloads in an AWS Local Zone located in the target metropolitan area.Answer
  2. Deploy the central database across multiple Availability Zones in the nearest AWS Region.Answer
  3. C
    Deploy the database inside AWS Edge Locations to enable low-latency read and write operations globally.
  4. D
    Deploy the database across multiple AWS Regions to achieve synchronous replication and zero-latency failover during an Availability Zone outage.
  5. E
    Deploy the game servers in a single Availability Zone and use Amazon CloudFront to automatically mirror and scale the compute instances to other Availability Zones.

Answer

Deploying the latency-sensitive game server workloads in an AWS Local Zone located in the target metropolitan area, and deploying the central database across multiple Availability Zones in the nearest AWS Region.
Deploying game servers in AWS Local Zones allows the application to achieve single-digit millisecond latency close to users in metropolitan areas where there is no primary AWS Region. Deploying the database across multiple Availability Zones within the nearest AWS Region provides physical redundancy and automatic failover capability to protect against local data center disasters.

Step-by-Step Solution

1
Analyze the requirement for single-digit millisecond latency in a metropolitan area without an AWS Region.
Identify AWS Local Zones as the infrastructure component designed to bring compute, storage, and database services close to major population centers for low-latency requirements.
Regions are geographically dispersed, and when a Region is not present in a metropolitan area, AWS Local Zones fill this gap.
2
Analyze the requirement for database high availability and disaster protection against data center failures.
Identify Multi-AZ deployment as the solution.
Availability Zones are physically isolated data centers within a Region with redundant power, networking, and connectivity, making them the standard choice for localized high availability.
3
Evaluate the distractors based on the roles of Edge Locations, Regions, and CloudFront.
Eliminate options proposing databases in Edge Locations, multi-Region synchronous replication for AZ failovers, and CloudFront-managed EC2 instance replication.
Edge locations cache content rather than host databases, Regions replicate asynchronously, and CloudFront handles content delivery rather than server mirroring.

Key Concept

AWS Global Infrastructure components (Regions, Availability Zones, Local Zones, Edge Locations) and their distinct architectural purposes.
Estimated Time:2m 0s
Rate this question