AWS Certified Solutions Architect Professional SAP-C02 Practice Question
Your company runs a revenue-critical order-processing application on EC2 Auto Scaling groups behind an Application Load Balancer. Transactional data is stored in an Amazon RDS for MySQL Multi-AZ DB instance in the us-east-1 Region. Compliance requires that the workload remain available if an entire AWS Region fails.
Business stakeholders have defined these recovery objectives:
RTO: 10 minutes
RPO: 1 minute
The finance team wants the most cost-effective solution that still meets the recovery objectives and keeps operational overhead low. Which disaster-recovery strategy should you recommend?
Deploy a multi-Region active-active architecture with Route 53 latency-based routing and an Amazon Aurora Global Database.
Implement a pilot-light approach that replicates EC2 servers with AWS Elastic Disaster Recovery and relies on CloudFormation to create the application tier on demand; create scheduled cross-Region RDS snapshots for the database.
Use AWS Backup to copy daily AMI and RDS snapshots to another Region and restore the infrastructure with AWS CloudFormation when a disaster is declared.
Maintain a warm standby stack in a secondary Region: run one instance per application tier at reduced capacity, configure Auto Scaling to scale out after failover, and replicate the RDS data to a cross-Region read replica that you promote during a disaster.
A warm-standby design keeps a scaled-down but fully functional copy of the workload running in the recovery Region. Data is replicated continuously, so the replica is only seconds behind (easily meeting the 1-minute RPO), and the stack can be scaled out within minutes, keeping the RTO under 10 minutes. Because only minimal capacity is running until a failover, costs are far lower than an active-active deployment.
An active-active multi-Region pattern also satisfies the objectives but runs full production capacity in two Regions, driving costs much higher than required. Backup-and-restore depends on snapshot copies and infrastructure creation after an event, so its RTO is typically measured in hours-far exceeding 10 minutes. A pilot-light approach leaves application servers undeployed and generally has an RTO in the tens of minutes, which risks overshooting the 10-minute requirement.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a warm standby disaster recovery strategy?
Open an interactive chat with Bash
How does RPO and RTO influence disaster recovery planning?
Open an interactive chat with Bash
What is the purpose of a cross-Region read replica in RDS?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design Solutions for Organizational Complexity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access