AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A company hosts a high-traffic ecommerce platform in the us-east-1 Region. The workload comprises:
Stateless web and API tiers on Amazon EC2 instances managed by an Auto Scaling group
A 1 TiB Amazon RDS for PostgreSQL database
The business requires disaster-recovery capabilities in the us-west-2 Region that meet these goals:
RPO ≤ 5 minutes
RTO ≤ 2 hours
Keep recurring DR costs as low as possible while still allowing rapid recovery
Provision all infrastructure through code when failover is initiated
Which design best satisfies the requirements by using the pilot light strategy?
Maintain an RDS cross-Region read replica and S3 Cross-Region Replication in us-west-2. Store encrypted AMIs and launch templates, and configure an Auto Scaling group with desired capacity 0. Use AWS CloudFormation to deploy EC2 capacity on failover, promote the replica to primary, and update Route 53 to point traffic to us-west-2.
Deploy identical fully scaled stacks in both Regions behind Route 53 active-active routing and use an Aurora global database for low-latency global reads and fast failover.
Run the full stack in us-west-2 at 50% of production capacity, including a Multi-AZ RDS instance, and use Route 53 latency-based routing. Scale out the stack during failover.
Keep nightly Amazon EBS and RDS snapshots in us-west-2, with no active resources. During a disaster, restore the snapshots and manually deploy the environment with CloudFormation.
The pilot-light pattern keeps only core, data-bearing services running in the recovery Region, while other infrastructure is provisioned only when a disaster occurs. The correct option meets this definition by maintaining a cross-Region RDS read replica and replicating data to S3, which keeps data current and supports the ≤ 5-minute RPO. All compute capacity is kept at zero desired instances, with AMIs and launch templates ready for deployment. In a disaster, CloudFormation can quickly deploy the compute layer, the RDS replica can be promoted, and Route 53 can redirect traffic-achieving the ≤ 2-hour RTO with minimal steady-state cost.
The other options represent different DR strategies that do not meet all the requirements:
One incorrect option describes backup and restore. With this method, no resources are active in the DR region, and the environment is built from snapshots. This typically results in an RTO that would exceed the 2-hour requirement.
Another incorrect option describes warm standby. This involves running application servers at reduced capacity in the DR region. While providing a faster RTO than pilot light, it incurs higher costs than necessary, violating the cost-optimization requirement.
The final incorrect option describes a multi-site active-active strategy. Deploying a fully scaled stack in both regions provides the lowest RTO but also the highest ongoing cost, which directly contradicts the requirement to keep DR costs as low as possible.
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 the pilot light strategy in disaster recovery?
Open an interactive chat with Bash
What is RPO and RTO in disaster recovery?
Open an interactive chat with Bash
How do cross-Region RDS read replicas help in disaster recovery?
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