Before production use, prepare a DynamoDB table to recover from future incorrect updates to a chosen point within seven days of continuously protected history. Weekly manual backups leave gaps.
After an incident, check the available restore window and restore data from just before the update to a new table. Reconfiguring the application target and operational settings is acceptable.
Which configuration is most appropriate?
Enable PITR before an incident, check configured retention and actual restorable times, and restore to a new table.
Detailed explanation
Enabling protection later cannot recreate earlier history.
Enabling protection later cannot recreate earlier history.
On-demand backups restore captured points rather than continuous history between them.
On-demand backups restore captured points rather than continuous history between them.
PITR creates a new table; prepare validation and application cutover.
PITR creates a new table; prepare validation and application cutover.
Restore to a chosen time within the continuous-backup window; check EarliestRestorableDateTime and LatestRestorableDateTime.
Restore to a chosen time within the continuous-backup window; check EarliestRestorableDateTime and LatestRestorableDateTime.
Check official documentation
Compare the following points with the official documentation.
Review the linked AWS documentation for retention, capture, restore targets, and required operational configuration.
Official references
What to confirm
Explain when protection starts, which recovery points exist, and what must be prepared after restoration.
Key points
- Point-in-time recovery
- Continuous backup
- DynamoDB
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-05.
Foundation review
Retention does not create earlier history
RecoveryPeriodInDays can be 1–35. Setting seven-day retention does not immediately provide seven days of history. Check EarliestRestorableDateTime and LatestRestorableDateTime; the latter is typically about five minutes behind. ContinuousBackupsStatus ENABLED alone does not establish that PointInTimeRecoveryStatus is enabled.
Prepare the restored table for use
PITR creates a new table while the source remains available. Data size and indexes affect duration; completion time is not fixed. Validate data and prepare the application target, IAM, Auto Scaling, TTL, Streams, alarms, and PITR before cutover.