A company hosts a public-facing application across two AWS Regions in an active-passive disaster recovery configuration. The primary region (us-east-1) and the secondary region (us-west-2) each have an Application Load Balancer (ALB) that routes traffic to Amazon EC2 instances. The company wants to configure Amazon Route 53 to automatically redirect client traffic to the secondary region if the primary region's application becomes unhealthy.
Which configuration should the solutions architect implement to achieve automatic failover to the secondary region?
- Create failover routing records in a Route 53 public hosted zone. Configure the primary record to point to the primary ALB with 'Evaluate Target Health' set to Yes and associate it with a health check that monitors the application's status. Configure the secondary record to point to the secondary ALB.Answer
- BCreate failover routing records in a Route 53 public hosted zone. Configure the primary record to point to the primary ALB, but set 'Evaluate Target Health' to No and omit the health check association to minimize DNS query overhead.
- CCreate failover routing records in a Route 53 private hosted zone. Configure the primary and secondary records to point to their respective ALBs, and associate the private hosted zone with the VPC in the primary region only.
- DCreate weighted routing records in a Route 53 public hosted zone with equal weights of 50 for both regions. Implement a database replication strategy where the secondary database is in a cold state and must be manually promoted before serving traffic.
Answer
Create failover routing records in a Route 53 public hosted zone, setting 'Evaluate Target Health' to Yes and associating the primary record with an application health check.
The correct configuration uses Route 53 public hosted zones with failover routing records. By setting 'Evaluate Target Health' to Yes and associating the primary record with an application health check, Route 53 can monitor the endpoint's health and failover to the secondary record when the primary endpoint is degraded.
Step-by-Step Solution
Key Concept
Active-Passive Disaster Recovery Failover with Route 53
Estimated Time:1m 0s