An IoT asset tracking platform for a cold chain logistics company runs its application tier on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer in the us-east-1 Region. The database tier uses a Single-AZ Amazon RDS for PostgreSQL DB instance. The company needs to design a disaster recovery (DR) strategy in the us-west-2 Region that achieves a Recovery Point Objective (RPO) of minutes and a Recovery Time Objective (RTO) of minutes, while minimizing ongoing run costs. Which combination of actions should a solutions architect recommend to meet these requirements? (Select TWO.)
- Configure a cross-region read replica for the Amazon RDS for PostgreSQL DB instance in us-west-2 to replicate data asynchronously.Answer
- BConfigure Amazon RDS Multi-AZ replication directly between us-east-1 and us-west-2 to enable automatic, synchronous database failover to the secondary region.
- Pre-deploy the Application Load Balancer in us-west-2, configure an Auto Scaling group with a minimum capacity of instance, and use Amazon Route 53 failover routing with active health checks.Answer
- DDeploy an Amazon Route 53 latency routing policy to distribute traffic across both regions, and use AWS CloudFormation to provision the Application Load Balancer and Auto Scaling group in us-west-2 from scratch upon detecting a failure.
- EBack up the database daily using AWS Backup, copy the recovery points to an Amazon S3 Glacier Flexible Retrieval vault in us-west-2, and restore the database to a new instance during a failover.
Answer
The correct strategy combines configuring an Amazon RDS for PostgreSQL cross-region read replica in the standby region with pre-deploying the Application Load Balancer and a scaled-down Auto Scaling group (minimum capacity of instance) in that region, combined with Route 53 failover routing and health checks.
To meet both the -minute RPO and -minute RTO cost-effectively, a Warm Standby disaster recovery pattern is required. The database tier uses asynchronous cross-region read replication to keep replica lag under a few minutes, meeting the RPO. Promoting the replica to primary takes under minutes. The compute tier pre-deploys the Application Load Balancer and keeps a minimum of EC2 instance active in the Auto Scaling group, enabling immediate request handling upon failover and rapid scale-out, satisfying the RTO. Route 53 failover routing automatically detects primary region failure and routes traffic to the standby load balancer.
Step-by-Step Solution
Key Concept
Warm Standby Disaster Recovery Pattern