Warm Standby Disaster Recovery: Meeting RPO of 15 Minutes and RTO of 2 Hours
A fintech startup uses AWS to run a web API and a PostgreSQL database. They must meet an RPO of 15 minutes and an RTO of 2 hours for a Region-wide disaster. Budget allows running a small, always-on set of infrastructure in a secondary Region, but not full production capacity. The team wants a DR approach that is regularly testable without large manual effort.
Which disaster recovery strategy is the best fit?
Quick Answer
The answer is warm standby, as it is the only strategy that balances a 15-minute RPO and 2-hour RTO with a scaled-down, always-on secondary environment. This approach uses active database replication—such as PostgreSQL streaming replication—to keep data loss under 15 minutes, while automated failover controls like Route 53 health checks and Lambda functions enable recovery within two hours without manual intervention. On the SAA-C03 exam, this scenario tests your ability to match recovery objectives to DR patterns, with a common trap being the pilot light strategy, which lacks the pre-warmed compute needed for a 2-hour RTO. Remember that warm standby is essentially a “mini-production” region: you pay for a smaller footprint but gain faster failover and easier testing. A useful memory tip is “warm = waiting, ready, and minimal”—the environment is active but not at full scale, making it the perfect fit for budget-conscious, testable disaster recovery.
⚠ Common exam trap
Test-takers frequently confuse pilot light with warm standby, assuming minimal infrastructure is sufficient for a 2-hour RTO, but pilot light requires provisioning and configuring application servers during failover, which typically takes longer than 2 hours, whereas warm standby already has the application running and only needs scaling.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Warm standby: keep a scaled-down application environment and database replication active in the secondary Region, using automated failover controls.
Warm standby (B) is the best fit because it maintains a scaled-down but fully functional application environment in the secondary Region with active database replication, meeting the RPO of 15 minutes (via synchronous or near-synchronous replication like PostgreSQL streaming replication) and RTO of 2 hours (via automated failover controls such as Route 53 health checks and AWS Lambda automation). This approach allows regular testing without large manual effort by simply promoting the standby environment, and the budget constraint is satisfied by running only minimal compute resources (e.g., smaller EC2 instances) in the secondary Region.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pilot light: replicate databases and store backups, keep only minimal infrastructure in the secondary Region, and scale up fully during failover.
Why it's wrong here
Pilot light can work for some RTO goals, but fully scaling dependencies within 2 hours may be difficult depending on application initialization and data warm-up.
When this WOULD be correct
A scenario where the RTO is longer (e.g., 4-6 hours) and the budget is extremely limited, allowing only a small database replica and no pre-provisioned application servers. The team can accept manual scaling steps during failover.
- ✓
Warm standby: keep a scaled-down application environment and database replication active in the secondary Region, using automated failover controls.
Why this is correct
Warm standby aligns with moderate RTO requirements by having ready-to-run resources plus continuous replication to meet the RPO target during failover.
- ✗
Backup and restore only: rely on daily automated backups and restore into the secondary Region during an incident.
Why it's wrong here
Daily backups cannot meet a 15-minute RPO, and restoration time would likely exceed the 2-hour RTO.
When this WOULD be correct
A company with an RPO of 24 hours and an RTO of 12 hours, where cost is the primary constraint and the application is not critical, would find backup and restore appropriate. For example, a development environment that can tolerate longer recovery times.
- ✗
Multi-site active-active: run both Regions at full capacity and route live traffic to both simultaneously.
Why it's wrong here
Active-active typically costs more than allowed, and it adds complexity beyond what the budget and requirements describe.
When this WOULD be correct
A company requires zero RPO and near-zero RTO for a critical application, has sufficient budget to run full production capacity in two Regions, and needs to handle sudden traffic spikes by distributing load across both Regions.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Warm standby: keep a scaled-down application environment and database replication active in the secondary Region, using automated failover controls.Correct answer▾
Why this is correct
Warm standby aligns with moderate RTO requirements by having ready-to-run resources plus continuous replication to meet the RPO target during failover.
✗Pilot light: replicate databases and store backups, keep only minimal infrastructure in the secondary Region, and scale up fully during failover.Wrong answer — click to see why▾
Why this is wrong here
Pilot light keeps minimal infrastructure in the secondary Region, which does not meet the RTO of 2 hours because scaling up from minimal to full capacity takes longer than 2 hours. The question requires a scaled-down but always-on environment to achieve the RTO.
★ When this WOULD be the correct answer
A scenario where the RTO is longer (e.g., 4-6 hours) and the budget is extremely limited, allowing only a small database replica and no pre-provisioned application servers. The team can accept manual scaling steps during failover.
Why candidates choose this
Pilot light is a well-known AWS DR pattern that balances cost and recovery time, and candidates may overestimate how quickly they can scale up from minimal infrastructure, ignoring the strict 2-hour RTO constraint.
✗Backup and restore only: rely on daily automated backups and restore into the secondary Region during an incident.Wrong answer — click to see why▾
Why this is wrong here
The RPO of 15 minutes cannot be met with daily backups, as data loss could be up to 24 hours. Additionally, restoring from backups would likely exceed the 2-hour RTO due to manual restore and provisioning time.
★ When this WOULD be the correct answer
A company with an RPO of 24 hours and an RTO of 12 hours, where cost is the primary constraint and the application is not critical, would find backup and restore appropriate. For example, a development environment that can tolerate longer recovery times.
Why candidates choose this
Candidates may think backup and restore is the simplest and cheapest option, overlooking the strict RPO and RTO requirements in the question. They might assume automated backups can be restored quickly without considering the manual effort and time involved.
✗Multi-site active-active: run both Regions at full capacity and route live traffic to both simultaneously.Wrong answer — click to see why▾
Why this is wrong here
Multi-site active-active requires both Regions to run at full production capacity simultaneously, which exceeds the budget constraint of running only a small, always-on infrastructure in the secondary Region.
★ When this WOULD be the correct answer
A company requires zero RPO and near-zero RTO for a critical application, has sufficient budget to run full production capacity in two Regions, and needs to handle sudden traffic spikes by distributing load across both Regions.
Why candidates choose this
Candidates may think active-active provides the best availability and failover speed, overlooking the cost implications and the specific budget limitation in the question.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A fintech startup uses AWS to run a web API and a PostgreSQL database. They must meet an RPO of 15 minutes and an RTO of 2 hours for a Region-wide disaster. Budget allows running a small, always-on set of infrastructure in a secondary Region, but not full production capacity. The team wants a DR approach that is regularly testable without large manual effort. Which disaster recovery strategy is the best fit?
medium- A.Pilot light: replicate databases and store backups, keep only minimal infrastructure in the secondary Region, and scale up fully during failover.
- ✓ B.Warm standby: keep a scaled-down application environment and database replication active in the secondary Region, using automated failover controls.
- C.Backup and restore only: rely on daily automated backups and restore into the secondary Region during an incident.
- D.Multi-site active-active: run both Regions at full capacity and route live traffic to both simultaneously.
Why B: Warm standby (B) is the best fit because it maintains a scaled-down but fully functional application environment in the secondary Region with active database replication, meeting the RPO of 15 minutes via synchronous or near-synchronous replication (e.g., PostgreSQL streaming replication or AWS DMS with ongoing replication). Automated failover controls (e.g., Route 53 health checks and Lambda automation) can achieve the RTO of 2 hours by scaling up the standby environment, and the always-on infrastructure allows regular, low-effort testing of the failover process without manual intervention.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.