Data Backup And Recovery Architecture — AWS Solutions Architect Pro (SAP-C02)
A Healthcare App with RPO 4h and RTO 30min Needs Two Mechanisms
A healthcare application must recover with no more than four hours of data loss and be operational within thirty minutes of a failure. These two constraints are independent and each requires its own design. The RPO drives backup frequency: snapshots or replication with no more than a four-hour lag satisfy the data loss limit. The RTO drives the standby strategy: a warm standby or pre-promoted read replica that accepts traffic without a multi-step restore satisfies the thirty-minute operational target. A single automated snapshot with restore-from-snapshot recovery satisfies the RPO but violates the RTO. SAP-C02 scenarios that specify both values expect an architecture that addresses each constraint independently.
What This Pattern Tests
The exam tests backup architecture decisions: snapshot frequency (drives RPO), retention period (drives compliance), cross-region copy (drives DR), and point-in-time recovery (PITR) capability. RDS automated backups support PITR to any second within the retention window. DynamoDB PITR provides continuous backups with 35-day retention. EBS snapshots are incremental. The trap is relying on automated backups without verifying the retention period meets the RPO or assuming PITR is enabled by default on DynamoDB (it requires explicit activation).
Decision Axis
RPO target determines backup frequency and method. Compliance requirements determine retention. DR requirements determine cross-region copy.
Associated Traps
More Top Traps on This Exam
Decision Rules
Determine whether the stated RPO/RTO pair (4 h / 2 h) requires the continuous-replication cost of Aurora Global Database or cross-Region read replicas, or whether automated cross-Region backup copies via AWS Backup combined with Aurora PITR fully satisfies both targets at backup-restore tier pricing.
Domain Coverage
Difficulty Breakdown