AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A fintech company runs its mission-critical transaction-processing platform in the us-east-1 Region. The architecture includes an Amazon EC2 Auto Scaling group behind an Application Load Balancer (ALB) and an Amazon Aurora MySQL cluster configured for Multi-AZ. After a recent risk assessment, the business mandates that the workload must stay operational if an entire AWS Region becomes unavailable and sets these objectives:
Recovery Time Objective (RTO) must not exceed 5 minutes.
Recovery Point Objective (RPO) must not exceed 1 minute.
The ongoing operational effort must be kept to a minimum.
Which solution will meet these requirements?
Schedule nightly Amazon RDS automated snapshots and AMI backups to copy to us-west-2. Use AWS CloudFormation to restore the database and launch the application stack after updating DNS manually during a disaster.
Deploy an active Aurora cluster in us-west-2 and configure AWS Database Migration Service (AWS DMS) to batch-replicate changes every 15 minutes. Distribute user traffic with AWS Global Accelerator and manually redirect traffic away from an impaired Region.
Convert the Aurora cluster to an Aurora Global Database with a secondary cluster in us-west-2. Enable AWS Elastic Disaster Recovery to continuously replicate the EC2 instances to us-west-2. Pre-deploy a scaled-down ALB and Auto Scaling group in that Region and create an Amazon Route 53 failover record that evaluates the us-east-1 ALB target health.
Keep the existing Aurora cluster and create a cross-Region Aurora read replica in us-west-2. Use an AWS Lambda function to promote the replica and launch the application stack from AWS CloudFormation templates when a CloudWatch alarm detects a Regional failure.
Aurora Global Database uses storage-based replication that typically keeps secondary clusters within 1 second of the primary and can promote a secondary Region in less than 1 minute, satisfying the 1-minute RPO and the 5-minute RTO. AWS Elastic Disaster Recovery provides continuous block-level replication of the EC2 instances with an RPO measured in seconds and an RTO measured in minutes, so the application tier can also be recovered well within the required window. By pre-deploying a scaled-down ALB and Auto Scaling group in the secondary Region and using a Route 53 failover record that evaluates the primary ALB's target health, traffic switches automatically when the primary Region is unreachable. This combination achieves the objectives with very little day-to-day administration-the services handle replication and health monitoring automatically.
The cross-Region read-replica approach relies on asynchronous replication and manual promotion, so RPO can exceed 1 minute and failover actions increase RTO. Snapshot-based backup and restore cannot meet either the 5-minute RTO or 1-minute RPO. Running an active cluster replicated by scheduled AWS DMS tasks still leaves up to 15 minutes of data exposure and requires manual traffic steering, raising both RPO and operational overhead.
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 an Aurora Global Database and how does it maintain low RPO and fast failover?
Open an interactive chat with Bash
What is AWS Elastic Disaster Recovery and how does it support low RTO?
Open an interactive chat with Bash
How does a Route 53 failover record work in achieving high availability?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access