Examkin

Question

Difficulty: MediumHigh Availability and Disaster Recovery Design

A logistics company is designing a new multi-region package tracking application to be deployed across two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The public web tier uses Application Load Balancers (ALBs) in both regions. The internal microservices communicate with one another using private domain names managed via a single Amazon Route 53 Private Hosted Zone. The database tier uses Amazon Aurora PostgreSQL.

The architecture must meet a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 55 minutes. Under normal operations, public users should be routed to the region that provides the lowest network latency. If a regional outage occurs, traffic must fail over automatically to the healthy region, and internal microservices in the secondary region must be able to resolve each other's endpoints using the same private domain names.

Which configuration will meet these requirements with the least operational complexity?

  1. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Create Amazon Route 53 latency routing records pointing to the public ALBs in each region, and associate them with Route 53 health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both us-east-1 and us-west-2.Answer
  2. B
    Configure cross-region database snapshot replication to copy Amazon Aurora PostgreSQL snapshots from us-east-1 to us-west-2 every 44 hours. Create Route 53 failover routing records pointing to the public ALBs in each region, and associate them with Route 53 health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both us-east-1 and us-west-2.
  3. C
    Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Create Route 53 latency routing records pointing to the public ALBs in each region, and associate them with Route 53 health checks. Associate the Route 53 Private Hosted Zone only with the VPC in us-east-1.
  4. D
    Deploy an Amazon Aurora PostgreSQL cluster in us-east-1 and configure Aurora Auto Scaling to dynamically create new reader replicas in us-west-2 when global database load increases. Create Route 53 latency routing records pointing to the public ALBs in each region, and associate them with Route 53 health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both us-east-1 and us-west-2.

Answer

The correct configuration is to use Amazon Aurora Global Database for sub-second database replication, Route 53 latency routing with health checks for public endpoint failover, and associate the shared Route 53 Private Hosted Zone with the VPCs in both regions to enable internal name resolution.
The configuration utilizing Amazon Aurora Global Database achieves a near-zero RPO (under 1 second) and an RTO of under 1 minute for database promotion, satisfying the 15-minute RTO and 5-minute RPO. Route 53 latency-based routing with health checks ensures public traffic is routed to the region with the lowest latency under normal conditions and automatically redirects to the healthy region during a failure. Finally, associating the Route 53 Private Hosted Zone with the VPCs in both regions ensures internal microservices can resolve endpoints cross-region using the same private DNS names.

Step-by-Step Solution

1
Determine the disaster recovery pattern required to satisfy the 55-minute RPO and 1515-minute RTO.
Select Amazon Aurora Global Database, which offers sub-second replication latency (RPO) and can be promoted in less than 11 minute (RTO).
Traditional backup-and-restore or snapshot copy methods (e.g., every 44 hours) exceed the 55-minute RPO.
2
Design the DNS routing configuration for routing users based on lowest latency with automatic failover.
Use Route 53 latency-based routing records for public ALBs, associated with Route 53 health checks.
Route 53 Latency routing routes traffic to the closest region, and health checks ensure Route 53 automatically stops sending traffic to an unhealthy region.
3
Configure private name resolution for internal microservices across both regions.
Associate the shared Route 53 Private Hosted Zone with the VPCs in both the primary and secondary regions.
Route 53 Private Hosted Zones must be explicitly associated with any VPC that requires resolution of those private records.

Key Concept

High Availability and Disaster Recovery Design
Estimated Time:2m 0s
Rate this question

Topics

High Availability and Disaster Recovery Design

More questions from this topic