Question

Difficulty: EasyMulti-AZ, Multi-Region Architectures and Disaster Recovery (DR)

An online ticketing platform hosts its application on Amazon EC2 instances and its database on an Amazon RDS for MySQL DB instance in the us-east-1 Region. The platform needs to implement a disaster recovery (DR) strategy in the us-west-2 Region. The strategy must support a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 30 minutes. Which combination of actions should a solutions architect recommend to meet these requirements? (Select TWO.)

  1. Create a cross-region read replica of the RDS DB instance in the us-west-2 Region.Answer
  2. Configure Amazon Route 53 with a failover routing policy and associate it with health checks to route traffic to the secondary Region.Answer
  3. C
    Deploy a cross-region RDS read replica and configure it as the automatic Multi-AZ failover target for the primary DB instance.
  4. D
    Set up Route 53 latency-based routing without health checks to automatically redirect traffic to the secondary Region if the primary Region fails.
  5. E
    Back up database transaction logs to Amazon S3 Glacier Flexible Retrieval and use standard retrieval to restore data in the secondary Region.

Answer

Create a cross-region read replica of the RDS DB instance in the secondary Region, and configure Amazon Route 53 with a failover routing policy and health checks to route traffic to the secondary Region.
Creating a cross-region read replica of the database satisfies the 5-minute RPO requirement because data is replicated asynchronously to the secondary Region. Promoting the replica to a primary instance takes under 30 minutes. Concurrently, Route 53 failover routing with health checks detects primary region outages and automatically redirects client application traffic to the secondary Region, keeping overall RTO under 30 minutes.

Step-by-Step Solution

1
Address the 5-minute RPO constraint for database replication.
Create a cross-region read replica of the RDS MySQL DB instance in the target DR Region.
This establishes asynchronous replication across Regions, keeping data lag down to seconds or minutes and meeting the RPO.
2
Address the 30-minute RTO constraint for traffic failover.
Configure Route 53 with a failover routing policy and configure active health checks on the primary endpoints.
Health checks monitor endpoint status and failover routing redirects traffic to the DR Region within minutes of a detected failure.

Key Concept

Combining cross-region database replication with Route 53 failover routing to meet low RTO and RPO disaster recovery objectives.
Rate this question