A SysOps Administrator is managing a critical reporting application that requires high availability and multi-Region disaster recovery. The database layer consists of an Amazon RDS for MySQL DB instance in us-east-1 configured with Multi-AZ, and a cross-Region read replica in us-west-2. The administrator wants to configure Amazon Route 53 DNS Failover to automatically route write traffic to the database in us-west-2 if us-east-1 experiences a complete regional outage. Which approach will achieve this objective while ensuring the database can accept write operations after failover?
- AConfigure a Route 53 Failover routing policy with the primary record pointing to the primary DB instance endpoint and the secondary record pointing directly to the read replica endpoint. Rely on Amazon Route 53 health checks to redirect write traffic to the replica, which will automatically begin accepting write operations.
- Configure a Route 53 Failover routing policy with the primary record pointing to the primary DB instance endpoint and the secondary record pointing to the promoted DB instance endpoint. Deploy an AWS Lambda function triggered by Amazon Route 53 health check alarms to promote the read replica in the secondary Region to a standalone DB instance during an outage.Answer
- CConfigure Route 53 Weighted routing records with equal weights pointing to both the primary DB instance in the primary Region and the read replica in the secondary Region. Enable Route 53 health checks on both records to automatically shift write traffic to the secondary Region if the primary instance becomes unhealthy.
- DModify the RDS DB instance configuration to enable Multi-AZ replication targeting a standby replica in the secondary Region. Configure Route 53 with a Latency routing policy so that client write requests are automatically routed to the active replica with the lowest network latency.
Answer
Configure a Route 53 Failover routing policy with the primary record pointing to the primary DB instance endpoint and the secondary record pointing to the promoted DB instance endpoint, and deploy an AWS Lambda function triggered by Route 53 health check alarms to promote the read replica in the secondary Region during an outage.
The correct approach involves configuring a Route 53 Failover routing policy to manage the DNS switchover and using an AWS Lambda function triggered by Route 53 health check alarms to promote the cross-Region read replica to a standalone DB instance. Because cross-Region read replicas use asynchronous replication and are read-only, Route 53 alone cannot enable write operations on the secondary DB; the database replica must be promoted to standalone status via the AWS API to begin accepting writes.
Step-by-Step Solution
Key Concept
Automating Multi-Region database failover requires active-passive Route 53 DNS routing and automated replica promotion using AWS SDK or Lambda, because cross-Region read replicas are read-only and do not promote automatically.
Estimated Time:3m 0s