AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A global financial services company runs a critical trading application on AWS, which must remain available during a regional outage. The business has mandated a Recovery Time Objective (RTO) of less than 1 minute. The current deployment uses a fleet of Amazon EC2 instances and an Amazon Aurora database in a single AWS Region. A solutions architect needs to design a disaster recovery strategy to meet this strict RTO requirement. Which approach should the architect recommend?
Replicate the Aurora database to a second AWS Region. In a disaster, use AWS CloudFormation to provision new EC2 instances and other resources in the second region, then manually update DNS records.
In a second AWS Region, deploy a scaled-down but fully functional version of the production environment. In a disaster, scale up the environment and use a Route 53 failover routing policy to redirect traffic.
Take regular snapshots of the Aurora database and copy them to an Amazon S3 bucket in a different AWS Region. In a disaster, restore the database from a snapshot and launch new EC2 instances from a pre-configured AMI.
Deploy a second, full-scale production environment in a different AWS Region. Use Amazon Route 53 with latency-based routing and health checks to distribute traffic between the two active regions.
The correct answer is to deploy a multi-site active-active architecture. A Recovery Time Objective (RTO) of less than 1 minute requires a strategy where failover is nearly instantaneous and automatic. The multi-site active-active approach achieves this by running full, independent production stacks in two or more AWS Regions and distributing traffic between them. Using Amazon Route 53 with latency-based routing and health checks allows traffic to be automatically redirected away from a failing region to a healthy one, meeting the sub-one-minute RTO.
A warm standby approach involves a scaled-down, but functional, environment in the DR region. Failing over requires scaling up the resources, which typically takes several minutes, thereby exceeding the RTO.
The pilot light approach involves replicating data and having core infrastructure defined (e.g., as code), but the application servers are not running. In a disaster, the infrastructure must be provisioned and started, a process that takes tens of minutes to hours, which is too long for the specified RTO.
Backup and restore is the slowest DR strategy, with an RTO measured in hours or even days, as it requires restoring data from backups and rebuilding the entire environment from scratch. This is completely unsuitable for a critical application with a sub-one-minute RTO 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 latency-based routing in Amazon Route 53?
Open an interactive chat with Bash
How does health checking work in Amazon Route 53?
Open an interactive chat with Bash
What is a multi-site active-active architecture?
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