An online retail platform's transaction processing system must be migrated to a multi-region disaster recovery (DR) architecture. The database layer uses a multi-AZ Amazon Aurora PostgreSQL cluster, and the application tier runs on Amazon EC2 instances in an Auto Scaling group. The compliance team mandates a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 5 minutes. The solution must be highly cost-effective, keeping the secondary Region's compute footprint minimal during normal operations.
Which combination of actions should a SysOps Administrator take to meet these requirements? (Select TWO.)
- Configure an Amazon Aurora Global Database with the primary cluster in the active Region and a secondary cluster in the recovery Region, deploying a single low-spec DB instance in the secondary cluster to serve as a pilot light.Answer
- Deploy the application tier in the recovery Region using an Auto Scaling group with the desired capacity set to 0, and configure an AWS CloudFormation template to deploy the application resources and scale up the group during failover.Answer
- CConfigure a cross-region Aurora Read Replica in the recovery Region, and rely on RDS Multi-AZ automatic failover to redirect database write traffic to the replica in the secondary Region during a disaster.
- DConfigure Route 53 with an active-active latency routing policy to distribute traffic across both Regions, ensuring that client requests are routed to the recovery Region only when the primary Region's latency increases.
- EConfigure Amazon S3 Cross-Region Replication (CRR) to replicate application configuration backups to the recovery Region, without enabling versioning on either the source or destination buckets to minimize storage costs.
Answer
The correct combination is to configure an Amazon Aurora Global Database with a low-spec DB instance as a pilot light in the secondary cluster, and deploy the application tier using an Auto Scaling group with a desired capacity of 0 in the recovery Region, using AWS CloudFormation templates to scale it during failover.
The correct strategy combines Amazon Aurora Global Database for sub-second database replication (meeting the 5-minute RPO) with a pilot light (single low-spec instance) to minimize database compute costs. For the application tier, deploying an Auto Scaling group with a desired capacity of 0 in the secondary Region avoids active compute costs, and using AWS CloudFormation ensures the infrastructure can be scaled up quickly during a disaster to meet the 15-minute RTO.
Step-by-Step Solution
Key Concept
Disaster Recovery Strategies
Estimated Time:2m 30s