A production RDS table was updated incorrectly.
Restore a new DB instance to a point just before the update within the automated-backup retention period.
Which recovery method is most appropriate?
Use RDS point-in-time recovery to restore a new instance from automated backups and transaction logs.
Detailed explanation
S3 object versions do not restore relational transaction history.
S3 object versions do not restore relational transaction history.
PITR reconstructs a new instance at a selected time within the backup retention window.
PITR reconstructs a new instance at a selected time within the backup retention window.
A DynamoDB expiry setting does not affect RDS backup recovery.
A DynamoDB expiry setting does not affect RDS backup recovery.
Audit events are not a backup of rows and transaction logs.
Audit events are not a backup of rows and transaction logs.
Check official documentation
Compare the following points with the official documentation.
Amazon RDS automated backups、PITR、復元先インスタンスの公式説明を確認する。
What to confirm
S3版管理・DynamoDB TTL・監査ログとRDS時点復元を区別できる。
Key points
- Point-in-time recovery
- Automated backup
- Transaction log
- RDS
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Recovery workflow
Restore, validate, isolate, and cut over deliberately rather than overwriting the original instance.
Retention window
A point outside automated-backup retention cannot be recovered with PITR.