All guides
Practice now
D2 · Resilient architectures

Disaster Recovery: RPO, RTO and strategies

The exam presents scenarios with specific RTO/RPO requirements and asks you to choose the correct DR strategy. You need to understand the trade-off between cost and recovery time for each strategy.

Icon-Architecture/48/Arch_AWS-Backup_48

RTO and RPO — core concepts

RTO

Recovery Time Objective

The maximum acceptable time to restore service after a disaster.

"The application must be operational within 5 minutes or less after a failure."

RPO

Recovery Point Objective

The maximum amount of data you can afford to lose, expressed as a time window since the last backup/replica.

"We cannot lose more than 1 hour of transactions."

Golden rule

The lower the RTO and RPO, the higher the cost. There's an inversely proportional relationship. The exam will give you RTO/RPO requirements and you must choose the cheapest strategy that meets them.

Icon-Architecture/48/Arch_AWS-Backup_48

The 4 DR strategies

StrategyRTORPOCostHow it works
Backup & RestoreHoursHours$Backups to S3/Glacier. Restore from scratch during a disaster.
10-30 minMinutes$$Core (replicated DB) always on. Scale up on disaster.
1-5 minSeconds$$$Full infrastructure at reduced scale in DR. Scale up on disaster.
Seconds≈ 0$$$$Two active regions. Route 53 redirects if one fails.
Icon-Architecture/48/Arch_AWS-Backup_48

AWS services for DR

RDS Cross-Region Read Replica

Strategy: Pilot Light / Warm Standby

Creates a Read Replica in another region. During a disaster: promote the replica to Primary (minutes). RPO = replication lag time (seconds to minutes).

Aurora Global Database

Strategy: Warm Standby / Multi-Site

Cross-region replication with <1 second latency. Promotion in <1 minute. Up to 5 secondary regions. The most advanced option for Aurora.

Strategy: Multi-Site Active/Active

Active tables in multiple regions. Writes replicated automatically. RPO ≈ 0. Reads and writes from any region.

S3 Cross-Region Replication

Strategy: All tiers

Automatically replicates S3 objects to another region. For assets, backups and data lakes. Combine with to serve from the nearest region.

Icon-Architecture/48/Arch_Amazon-Route-53_48

Multi-Region vs Multi-AZ

Multi-AZ = (HA)

  • •Protects against the failure of one
  • •Same AWS region
  • •Automatic failover in minutes (RDS)
  • •Same endpoint — the app doesn't change
  • •Moderate cost — already included in Multi-AZ instances

Multi-Region = (DR)

  • •Protects against the failure of an entire region
  • •Different AWS regions (e.g. us-east-1 + eu-west-1)
  • •Failover with Route 53 health checks
  • •Requires explicit replication (RDS, S3 CRR, etc.)
  • •High cost — double the infrastructure

Exam trap

Multi-AZ is NOT DR across regions. If the exam mentions "an entire region goes down" or "regional disaster", the solution is Multi-Region. If it mentions "an AZ fails" or "high availability", the solution is Multi-AZ.

Diagram: DR strategy comparison

The 4 strategies with RTO, RPO, relative cost, and key AWS services.

Did you get this topic?

Test what you just learned

A financial services company needs an RTO of 5 minutes and an RPO of 30 seconds for its payment processing system. Which DR strategy is most appropriate considering cost?

Ready to test "Disaster recovery: RPO, RTO and strategies"?

Put what you learned to the test with original SAA-C03 exam questions.

Start SAA-C03 mock exam

Unlimited mock exams with the Pro plan

Log in to track your progress.