AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company runs a critical trade-processing application on AWS. The application uses a fleet of Amazon EC2 instances and an Amazon Aurora PostgreSQL database. Due to the critical nature of the application, the business has mandated a Recovery Time Objective (RTO) of less than 1 minute and a Recovery Point Objective (RPO) of less than 1 second. The disaster recovery (DR) plan must account for a full AWS Region failure.
Which DR strategy should a solutions architect recommend to meet these requirements?
Deploy the application and a scaled-down version of the EC2 fleet in a secondary region as a Warm Standby. Use Amazon Aurora Global Database, with the secondary region hosting a read replica.
Use AWS Backup with Cross-Region Replication to copy Aurora snapshots and AMIs to a secondary region. In a disaster, restore the environment using the replicated backups.
Configure a Pilot Light architecture by replicating the Aurora database to a secondary region. Provision the application tier infrastructure only upon a failover event.
Use AWS Elastic Disaster Recovery (DRS) to continuously replicate the EC2 instances and the attached database volumes to a staging area in a secondary region.
The correct answer is to use Amazon Aurora Global Database and a Warm Standby application tier. Amazon Aurora Global Database is specifically designed for cross-region disaster recovery, providing a typical RPO of under one second and an RTO of under one minute, which precisely meets the stated requirements. The Warm Standby approach for the application tier ensures that a scaled-down but fully functional version of the environment is always running in the DR region, allowing for a rapid failover and scaling to full capacity within the one-minute RTO.
Using a Pilot Light strategy would not meet the RTO. While the data layer might be replicated, the application infrastructure in the DR region would need to be provisioned and scaled from a minimal state, a process that typically takes several minutes, exceeding the one-minute RTO.
Implementing a Backup and Restore strategy would fail to meet either the RTO or the RPO. Restoring from backups, even with Cross-Region Replication, is a process that takes hours, not minutes. The RPO would also be, at best, the time between snapshots, which is far greater than one second.
Using AWS Elastic Disaster Recovery (DRS) is a strong but incorrect option. While DRS provides an excellent RPO of seconds by using continuous block-level replication, its RTO is typically in the range of minutes (e.g., 5-20 minutes) because it needs to launch new recovery instances from replicated data. This would not meet the stringent 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 an Amazon Aurora Global Database, and why is it suitable for cross-region disaster recovery?
Open an interactive chat with Bash
How does a Warm Standby strategy work, and why is it effective for meeting critical RTO requirements?
Open an interactive chat with Bash
Why don't Pilot Light and Backup/Restore strategies meet stringent RTO and RPO requirements?
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