A mistaken update changed data in an RDS database.
Create a new database instance restored to an arbitrary point within the retention period.
Which feature is most appropriate?
Use RDS automated backups and point-in-time restore to create a new instance at the selected time.
Detailed explanation
Performance analysis does not restore database contents.
Performance analysis does not restore database contents.
Automated backups and transaction logs support a restore to a selected time within the retention window.
Automated backups and transaction logs support a restore to a selected time within the retention window.
DNS failover changes routing and does not restore database rows.
DNS failover changes routing and does not restore database rows.
A CDN cache is not an RDS recovery point.
A CDN cache is not an RDS recovery point.
Check official documentation
Compare the following points with the official documentation.
Amazon RDS point-in-time restoreの公式説明を確認する。
What to confirm
スナップショット復元とPITRの違いを説明できる。
Key points
- RDS automated backups
- Point-in-time restore
- Transaction log
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Snapshot versus PITR
A snapshot restores its capture time, while PITR can use logs to reach a later selected time.
New restore target
The restore operation creates another DB instance so the source can be preserved for comparison.