AWS Certified Solutions Architect Professional SAP-C02 Practice Question
An insurance company runs a three-tier claims-processing application in its on-premises data center. The disaster-recovery team must achieve an RPO of 15 minutes and an RTO of 1 hour while keeping ongoing AWS costs as low as possible. The team has chosen a pilot-light strategy in a secondary AWS Region by using AWS Elastic Disaster Recovery (AWS DRS). Which approach will meet these requirements?
Provision a scaled-down warm-standby environment in the DR Region, including one running EC2 instance per tier and a Multi-AZ Amazon RDS database, and use AWS Database Migration Service for ongoing data replication.
Install the AWS Replication Agent on each on-premises server to replicate data continuously to a low-cost staging area subnet in the DR Region. Allow AWS DRS to use its default t3.small replication servers and pre-configure EC2 launch templates with production instance sizes, keeping application servers powered off until a recovery drill or failover is initiated.
Deploy a fully active-active architecture across two AWS Regions by using Amazon Route 53 weighted routing and AWS Global Accelerator health checks to distribute traffic and fail over automatically.
Configure daily AWS Backup jobs that copy EBS snapshots and AMIs to Amazon S3 in the DR Region, then use an AWS CloudFormation stack to restore the snapshots and launch new EC2 instances during a disaster.
With a pilot-light strategy the only resources that stay active in the recovery Region are those required for data replication and backup. AWS Elastic Disaster Recovery continuously replicates block-level changes from the on-premises servers to low-cost Amazon EBS staging volumes that are attached to automatically managed t3.small replication servers. No workload compute instances are launched until a recovery drill or real failover occurs. Pre-defining production-sized EC2 launch templates allows AWS DRS to create fully sized recovery instances quickly, keeping ongoing spend minimal and still meeting the 15-minute RPO and 1-hour RTO.
Daily backup jobs that rely on snapshot restores (option B) cannot guarantee a 15-minute RPO and require manual orchestration that typically exceeds a 1-hour RTO. A warm-standby stack that keeps EC2 instances and a Multi-AZ database running (option C) incurs higher steady-state cost and does not follow the pilot-light pattern. An active-active deployment across two Regions (option D) provides continuous availability but is the most expensive approach and also does not align with the pilot-light strategy.
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 pilot-light strategy in disaster recovery?
Open an interactive chat with Bash
How does AWS Elastic Disaster Recovery (AWS DRS) achieve low RPO and RTO?
Open an interactive chat with Bash
Why is using daily AWS Backup jobs not suitable for a 15-minute RPO and 1-hour RTO?
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