Examkin

Question

Difficulty: MediumHigh Availability and Disaster Recovery Design

A gaming company is designing a multiplayer game backend to store user profile states and matchmaking configurations. The primary infrastructure is located in the `us-east-1` Region, consisting of an Application Load Balancer (ALB), an Auto Scaling Group (ASG) of Amazon EC2 instances in private subnets, and an Amazon Aurora MySQL database cluster. To prepare for a regional outage, the company is designing a disaster recovery (DR) solution in the `us-west-2` Region. The DR solution must achieve a Recovery Time Objective (RTO) of less than 1515 minutes and a Recovery Point Objective (RPO) of less than 22 minutes. The design must also minimize ongoing compute costs in the disaster recovery region. Which architecture meets these requirements?

  1. A
    Configure an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2` containing a single reader instance. Deploy an ALB and an ASG in `us-west-2` with the capacity set to 00. Create a Route 53 Private Hosted Zone (PHZ) for internal database endpoint resolution and associate it with the VPCs in both regions. In both regions, deploy a single NAT Gateway in 11 Availability Zone to route outbound private subnet traffic. Configure Route 53 Failover routing records with health checks pointing to the `us-east-1` ALB.
  2. B
    Configure Amazon Aurora database backups in `us-east-1` and schedule copies of these snapshots to `us-west-2` every 3030 minutes. Deploy an ALB and an ASG in `us-west-2` with the capacity set to 00. Create a Route 53 Private Hosted Zone (PHZ) associated with the VPCs in both regions. Configure Route 53 Failover routing records with health checks pointing to the `us-east-1` ALB. Upon failover, restore the database in `us-west-2` from the latest copied snapshot, scale up the ASG in `us-west-2` to the required capacity, and update the database endpoint in the PHZ.
  3. Configure an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2` containing a single reader instance. Deploy an ALB and an ASG in `us-west-2` with the capacity set to 00. Create a Route 53 Private Hosted Zone (PHZ) for internal database endpoint resolution and associate it with the VPCs in both `us-east-1` and `us-west-2`. Configure Route 53 Failover routing records with health checks pointing to the `us-east-1` ALB, with the primary record targeting `us-east-1` and the secondary record targeting the `us-west-2` ALB. Upon failover, promote the secondary database cluster and scale up the ASG in `us-west-2`.Answer
  4. D
    Configure an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2` containing a single reader instance. Deploy an ALB and an ASG in `us-west-2` with the capacity set to 00. Create a Route 53 Private Hosted Zone (PHZ) in `us-east-1` for database endpoint resolution, leaving it unassociated with the `us-west-2` VPC. Configure Route 53 Failover routing records with health checks pointing to the `us-east-1` ALB, with the primary record targeting `us-east-1` and the secondary record targeting the `us-west-2` ALB. Upon failover, promote the secondary database cluster and scale up the ASG in `us-west-2`.

Answer

The architecture that configures an Aurora Global Database, sets the secondary region's Auto Scaling Group capacity to 00, associates the Route 53 Private Hosted Zone with both region VPCs, and configures Route 53 Failover routing.
The correct architecture uses Amazon Aurora Global Database, which replicates data asynchronously to the secondary region with a typical latency of less than 11 second, easily meeting the RPO of less than 22 minutes. Setting the standby Auto Scaling Group's capacity to 00 minimizes ongoing EC2 compute costs. Route 53 Failover routing correctly detects primary region degradation via health checks and automatically redirects traffic to the standby ALB. Once failover is initiated, the secondary database cluster is promoted to primary, and the ASG is scaled up, which can be accomplished well within the 1515-minute RTO. Associating the Private Hosted Zone with VPCs in both regions ensures internal database endpoint resolution continues to work in the disaster recovery region.

Step-by-Step Solution

1
Select a replication strategy that meets the RPO constraint of less than 22 minutes.
Amazon Aurora Global Database provides sub-second cross-region replication, satisfying the RPO, whereas snapshot copies fail to meet it.
Physical snapshot copying and restoration cannot guarantee sub-minute data sync.
2
Determine the compute configuration in the recovery region to minimize cost while meeting the RTO.
Set the Auto Scaling Group capacity in `us-west-2` to 00 and scale it up only during a failover event.
Keeping instances at 00 avoids active compute costs, and scaling up takes only a few minutes, which is well within the 1515-minute RTO.
3
Ensure DNS resolution for database endpoints works in both regions.
Associate the Route 53 Private Hosted Zone with the VPCs in both `us-east-1` and `us-west-2`.
Private Hosted Zones must be associated with a VPC to allow DNS queries originating from that VPC to resolve successfully.
4
Evaluate outbound internet routing resiliency in the VPC design.
Deploy NAT Gateways redundantly in each Availability Zone where application instances reside.
A single NAT Gateway per VPC creates a single point of failure that compromises high availability if its hosting zone experiences an outage.

Key Concept

High Availability and Disaster Recovery Design for Multi-Region Architectures
Rate this question

Topics

High Availability and Disaster Recovery Design

More questions from this topic