AWS Certified Solutions Architect Professional SAP-C02 Practice Question
An online equities-trading platform is deployed in the us-east-1 Region. The architecture includes an Application Load Balancer, an Auto Scaling group of Amazon EC2 instances that span three Availability Zones, and an Amazon Aurora PostgreSQL Multi-AZ DB cluster. AZ-level failover currently meets a 90-second RTO, but a resilience review showed the workload cannot survive a Regional outage. New requirements mandate an RPO of under 1 minute and an RTO of under 5 minutes if the entire primary Region becomes unavailable, while adding the least possible operational overhead and requiring no major application code changes. Which combination of actions best meets these requirements?
Replatform the database layer to Amazon DynamoDB and enable global tables in us-east-1 and us-west-2; refactor the application to use DynamoDB APIs; use Route 53 latency-based routing so users connect to the nearest Region.
Use AWS Database Migration Service for continuous replication to an Aurora PostgreSQL instance in us-west-1 and maintain custom scripts that update security groups and Route 53 records to cut traffic over to the secondary Region after an outage is confirmed.
Convert the Aurora cluster to an Aurora Global Database and add a secondary cluster in us-west-2 with global write forwarding enabled; deploy the same application stack in us-west-2 using infrastructure-as-code; configure Amazon Route 53 Application Recovery Controller routing controls with failover DNS records that automatically redirect traffic to the secondary Region when health checks fail.
Retain the Aurora Multi-AZ cluster, create a cross-Region Amazon RDS read replica in us-west-2, copy automated snapshots nightly, and invoke an AWS Lambda function from a CloudWatch alarm to promote the replica and update Route 53 failover DNS records after a Regional outage.
Aurora Global Database uses dedicated storage-layer replication that keeps secondary clusters within typically 1 second of the primary and can promote a secondary Region for full read/write operations in under 1 minute, satisfying the <1-minute RPO and <5-minute RTO targets. Enabling global write forwarding lets existing JDBC/ODBC connections continue to send writes through the reader endpoint after failover, avoiding application rewrites. Deploying the same compute layer in the secondary Region with infrastructure-as-code ensures capacity is ready, and Route 53 ARC routing controls with health-check-based DNS failover shift traffic automatically, eliminating manual steps.
Cross-Region RDS read replicas (choice B) replicate asynchronously, can lag for minutes, and require manual promotion, so RPO/RTO objectives are not guaranteed. DynamoDB global tables (choice C) provide excellent RPO/RTO but force a complete database re-platform and significant code changes, violating the constraint. Continuous replication with AWS DMS and custom scripting (choice D) adds operational complexity, relies on asynchronous change data capture, and offers no managed, sub-minute promotion mechanism, so it cannot ensure the required objectives.
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?
Open an interactive chat with Bash
How does Route 53 Application Recovery Controller manage failover?
Open an interactive chat with Bash
What is global write forwarding in Aurora Global Database?
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