Protect a Redshift cluster from failure or operator error.
Retain the previous seven days and eliminate manual daily snapshots.
Which feature is most appropriate?
Configure Redshift automated snapshots with the required frequency and retention period.
Detailed explanation
Redshift can create snapshots automatically and retain them for cluster recovery.
Redshift can create snapshots automatically and retain them for cluster recovery.
S3 Lifecycle does not control Redshift snapshot retention.
S3 Lifecycle does not control Redshift snapshot retention.
DynamoDB TTL applies to items, not Redshift backups.
DynamoDB TTL applies to items, not Redshift backups.
API audit records are not a copy of Redshift table blocks.
API audit records are not a copy of Redshift table blocks.
Check official documentation
Compare the following points with the official documentation.
Amazon Redshift automated snapshot、retention、restoreの公式説明を確認する。
What to confirm
S3・DynamoDB・監査ログとRedshiftスナップショットの違いを説明できる。
Key points
- Automated snapshot
- Retention
- Redshift
- Restore
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Recovery coverage
Snapshot frequency and retention determine which failure and operator-error points can be recovered.
Operational automation
Managed snapshots remove manual work but still require restore testing and cost review.