A bug incorrectly updated items during the last few hours.
Restore the table to a selected point rather than reverting an entire offline backup.
Which recovery method is most appropriate?
Use DynamoDB Point-in-Time Recovery to restore a new table from continuous backups.
Detailed explanation
S3 object generations are separate from DynamoDB table backups.
S3 object generations are separate from DynamoDB table backups.
PITR restores a new table to a selected time within the continuous-backup retention window.
PITR restores a new table to a selected time within the continuous-backup retention window.
Stopping expiry does not restore previous item values.
Stopping expiry does not restore previous item values.
Audit events are not a safe inverse transaction log for table restoration.
Audit events are not a safe inverse transaction log for table restoration.
Check official documentation
Compare the following points with the official documentation.
DynamoDB Point-in-Time Recovery、continuous backups、restoreの公式説明を確認する。
What to confirm
TTL停止・S3版管理・監査イベント再生とPITRの違いを説明できる。
Key points
- DynamoDB PITR
- Continuous backup
- Restore point
- Retention window
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
New-table restore
PITR creates a separate table, so application routing and validation are explicit.
Recovery granularity
Point-in-time recovery differs from an on-demand full backup at one fixed instant.