Free SAA-C03 practice scenarios: disaster recovery strategies

The DR ladder and the numbers that pick a rung — RTO, RPO and the cheapest strategy that meets them. Six scenarios, SAA-C03, 2026 edition.

Try 6 free disaster-recovery scenarios in the exam's own style — every answer explained, no sign-up.

Straight to the 6 free questions ↓

Disaster recovery is a signature SAA-C03 pattern, and it is almost always a selection problem: a scenario states an RTO, an RPO and a cost posture, and asks which of four strategies fits. Get the two objectives straight, then pick the cheapest rung that meets them.

RTO vs RPO

Two numbers, two axes:

RPO (Recovery Point Objective) — the maximum acceptable data loss, as a point in time. RPO of 5 minutes = lose at most the last 5 minutes.
RTO (Recovery Time Objective) — the maximum acceptable downtime, how long recovery may take.

The exam routinely offers the wrong one as a distractor, so read the question’s phrasing carefully: “how much data can we lose” is RPO; “how long can we be down” is RTO.

The ladder, cheapest to fastest

Backup and restore — only backups kept; rebuild at recovery time. RTO in hours, lowest cost.
Pilot light — data replicated, only the core (the database) kept running; the rest provisioned at failover. RTO in tens of minutes.
Warm standby — a scaled-down but fully functional copy always running, scaled up on failover. RTO in minutes.
Multi-site active-active — both Regions serve live traffic. Near-zero RTO and RPO, highest cost.

The selection rule

Pick the cheapest strategy that satisfies the numbers — not the fastest on the list. Warm standby beating a stated RTO does not make it right when pilot light also meets it for less. Overshooting the requirement at extra standing cost is the most elegant trap this topic sets. And do not confuse a Multi-AZ deployment (which survives an Availability Zone failure inside one Region) with a cross-Region DR strategy — they solve different failures.

Centralising backups

When the scenario is about backups themselves — policies, scheduling, monitoring, cross-Region copy across EBS, RDS, DynamoDB and more — the answer is AWS Backup, which manages all of it centrally instead of per-service snapshots by hand.

How to use the six scenarios below

Answer each one before opening the explanation, and when you miss, name the number that decided it — the RTO, the RPO, or the cost ceiling — and check you did not overshoot. Every explanation states the deciding constraint and dismantles the distractors, which are usually a neighbouring rung on the ladder. For the domain overview, see Design Resilient Architectures.

The four disaster-recovery strategies ordered by rising cost and falling recovery time. Backup and restore keeps only backups and rebuilds at recovery time, with a recovery time objective in hours and the lowest cost. Pilot light keeps data replicated and only core services such as the database running, provisioning the rest at failover, with recovery in tens of minutes. Warm standby keeps a scaled-down but fully functional copy always running, recovering in minutes. Multi-site active-active runs both environments live for near-zero recovery time and point objectives at the highest cost.

6 free SAA-C03 practice questions

Answers and explanations — no email wall

SAA-C03 Question 1 of 6

A company defines its disaster-recovery targets. Which term describes the maximum amount of data, measured in time, the business can afford to lose in an incident?

Answer: A — Recovery Point Objective (RPO).

RPO is the maximum acceptable data loss expressed as a point in time — an RPO of five minutes means losing at most the last five minutes of data. Why not the others: RTO is the maximum acceptable downtime, how long recovery may take — a different axis. MTTR is an average repair time metric, not a target for data loss. An SLA is a commitment about service levels, not specifically the data-loss window. Maximum data loss is the RPO; maximum downtime is the RTO — keeping these two apart is essential on DR questions.

SAA-C03 Question 2 of 6

A workload can tolerate several hours of downtime after a disaster, and the company wants the lowest-cost DR approach with almost no standing infrastructure in the recovery Region. Which strategy fits?

Answer: A — Backup and restore.

Backup and restore keeps only backups in the recovery Region and rebuilds the environment when disaster strikes — the cheapest strategy, with a recovery time measured in hours, matching 'several hours acceptable, lowest cost, minimal standing infrastructure'. Why not the others: warm standby and multi-site keep infrastructure running continuously, costing more than the requirement wants. Pilot light keeps core services alive and recovers faster, again at more cost than needed. When hours of downtime are acceptable and cost is paramount, it is backup and restore.

SAA-C03 Question 3 of 6

In which disaster-recovery strategy is only a minimal core — typically the replicated database — kept running in the recovery Region, while the rest of the environment is provisioned only when a failover occurs?

Answer: A — Pilot light.

Pilot light keeps the data continuously replicated and only the core (usually the database) alive, spinning up the remaining infrastructure at failover — a faster recovery than backup and restore at a modest standing cost. Why not the others: warm standby keeps a scaled-down but fully functional copy of the whole stack running, not just the core. Backup and restore keeps nothing running, only backups. Multi-site runs everything live in both Regions. 'Only the core kept warm' is the definition of pilot light.

SAA-C03 Question 4 of 6

A company needs recovery within minutes and is willing to run a scaled-down but fully functional copy of its entire environment continuously, scaling it up on failover. Which strategy is this?

Answer: A — Warm standby.

Warm standby keeps a smaller but complete copy of the workload always running in the recovery Region, ready to take traffic and scale up quickly — a recovery time in minutes. Why not the others: pilot light keeps only the core running, so more must be built at failover, making it slower. Backup and restore keeps nothing live. A Multi-AZ deployment protects against an Availability Zone failure within one Region — it is not a cross-Region DR strategy. A always-on, scaled-down full copy is warm standby.

SAA-C03 Question 5 of 6

A mission-critical application must survive a Region failure with near-zero downtime and near-zero data loss, and cost is not a primary concern. Which DR strategy meets this?

Answer: A — Multi-site active-active (both Regions serving live traffic).

Multi-site active-active runs the workload live in both Regions simultaneously, so a Region failure causes almost no downtime or data loss — the only strategy that meets near-zero RTO and RPO, at the highest cost the requirement accepts. Why not the others: backup and restore, pilot light and warm standby all involve some recovery step and therefore more downtime than 'near-zero'. When RTO and RPO must both approach zero and cost is secondary, it is multi-site active-active.

SAA-C03 Question 6 of 6

A company wants to centrally automate and monitor backups across many services — Amazon EBS, Amazon RDS, DynamoDB and more — with backup policies and cross-Region copy for DR. Which service should it use?

Answer: A — AWS Backup.

AWS Backup centralises backup policies, scheduling, monitoring and cross-Region (and cross-account) copy across many AWS services from one place — exactly the centralised, policy-driven backup described. Why not the others: scheduling snapshots per service manually is the fragmented toil AWS Backup replaces. S3 lifecycle policies manage object storage transitions, not backups of EBS, RDS and DynamoDB. CloudFormation provisions infrastructure; it is not a backup manager. Centralised, policy-based backups across services are AWS Backup.

That is exactly how every question in the course works — answer, explanation, why-not. The real set continues in the practice player: 10 free questions, no sign-up.

Continue with the 10 free questions →

Those 6 questions were the start.

The exam does not test whether you recognise a term — it tests whether you can rule out three plausible answers under time pressure. That is what the explanations above are for, and there are 780 more questions built exactly like them.

Collecting questions yourself

Scattered across forums, of unknown age
Answer keys without reasoning
No idea which domain you are weak in

Practising with a system

780 questions in 12 full tests, SAA-C03 (2026)
Every option explained — including the wrong ones
Readiness per exam domain, and drills for your weakest

Start free — 10 questions

Straight into the player. No account, no email.

Frequently asked questions

How does the SAA-C03 test disaster recovery?

Usually by giving you an RTO, an RPO and a cost posture, and asking which of the four strategies fits. The discipline is to pick the cheapest strategy that satisfies the numbers — overshooting the requirement with a faster, pricier strategy is the classic trap.

What is the order of the four strategies?

By rising cost and falling recovery time: backup and restore (cheapest, RTO in hours), pilot light (only the core running, RTO in tens of minutes), warm standby (scaled-down full copy, RTO in minutes), multi-site active-active (both live, near-zero RTO/RPO, most expensive).

Are these real exam questions?

No. They are original scenarios written for this page in the exam's style and difficulty. Reproducing real exam items violates the AWS certification agreement and can cost a candidate their certification — ours come with the reasoning attached instead.

What is the one-line takeaway?

RPO is data loss, RTO is downtime. Pick the cheapest of backup-and-restore, pilot light, warm standby or multi-site that meets both numbers, and centralise backups with AWS Backup.

Updated for SAA-C03 (July 2026). The sample questions above are our own work in the style of the exam — not real exam items. The exam itself is set and marked by the certification body.