Data Backup And Recovery Architecture — AWS SysOps Administrator (SOA-C03)
Backup Frequency Is Not Recovery Guarantee
SOA-C03 backup questions hinge on two phrases: "point-in-time recovery" and "automated backup." Point-in-time recovery implies continuous log shipping — relevant for RDS and DynamoDB — not daily snapshots. Candidates who focus on backup frequency miss the RPO constraint. If the scenario states a one-hour RPO, a daily snapshot fails regardless of how reliably it executes. Read RPO as a ceiling, not a preference.
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
Decision Rules
Whether to enable RDS automated backups (enabling PITR via continuous transaction-log replay) versus relying on periodic manual snapshots, where the recovery-point gap is bounded only by snapshot frequency and cannot guarantee a 5-minute RPO.
Whether to rely on native RDS automated backups — which are deleted on instance deletion by default — versus AWS Backup managed plans that decouple backup retention from the RDS instance lifecycle, making persistence guarantees the deciding constraint rather than RPO or PITR capability.
Whether Multi-AZ high availability satisfies a 15-minute RPO for logical data corruption versus enabling automated backups to unlock continuous transaction-log-based PITR, which is the only mechanism that constrains data-loss window for application-layer errors.
Whether enabling RDS automated backups and relying on native PITR satisfies the five-minute RPO with lower operational burden than scheduling and managing frequent manual snapshots, given that manual snapshots are point-in-time copies only and cannot recover to an arbitrary second within the gap between two snapshots.
Domain Coverage
Difficulty Breakdown