A global financial enterprise is updating its Disaster Recovery (DR) governance standards on AWS. The Chief Technology Officer asks the solutions architect to rank the four official AWS Disaster Recovery strategies in order from LOWEST cost (highest RTO/RPO) to HIGHEST availability (near-zero RTO/RPO): 1. Warm Standby (scaled-down but always-running functional copy of the production environment in a secondary Region). 2. Backup and Restore (periodic snapshots and data backups replicated to Amazon S3 in a secondary Region). 3. Multi-Site Active/Active (full-scale production capacity serving live traffic simultaneously across two or more Regions). 4. Pilot Light (core database replicated in real time to a secondary Region while compute instances remain stopped until failover). What is the correct sequence from lowest cost to lowest RTO/RPO?
- A. 2 -> 4 -> 1 -> 3
- B. 4 -> 2 -> 1 -> 3
- C. 2 -> 1 -> 4 -> 3
- D. 3 -> 1 -> 4 -> 2
Reveal Verified Answer (A), Technical Explanation & Exam Hack
Correct Answer: Option A
The AWS Disaster Recovery spectrum ordered from lowest cost / longest recovery time to highest cost / near-zero recovery time is: Backup and Restore (hours, 2) -> Pilot Light (tens of minutes, 4) -> Warm Standby (minutes, 1) -> Multi-Site Active/Active (real-time / seconds, 3). Architectural Deep Dive: For database resiliency and performance: Amazon RDS Multi-AZ provides synchronous standby replication for High Availability and automated failover (not read scaling), whereas Read Replicas use asynchronous replication to offload read-heavy reporting queries; Amazon Aurora provides 6-copy storage across 3 AZs, up to 15 low-latency Read Replicas, Aurora Serverless v2 for instant autoscaling, and Aurora Global Database for sub-second cross-region DR; Amazon DynamoDB delivers serverless single-digit millisecond NoSQL at any scale (accelerated to microseconds via DAX and replicated active-active worldwide via Global Tables); and Amazon ElastiCache for Redis provides sub-millisecond in-memory caching, sorted sets/leaderboards, and HIPAA-compliant encryption + Redis AUTH. Why the distractors fail: Option B is incorrect because this option either misapplies the AWS service outside its intended architectural pattern or violates the primary constraint (operational simplicity, cost efficiency, or target accuracy) specified in the scenario. Option C is incorrect because this option either misapplies the AWS service outside its intended architectural pattern or violates the primary constraint (operational simplicity, cost efficiency, or target accuracy) specified in the scenario. Option D is incorrect because this option either misapplies the AWS service outside its intended architectural pattern or violates the primary constraint (operational simplicity, cost efficiency, or target accuracy) specified in the scenario.