Back up production EC2, RDS, and EFS resources every day.
Automatically include newly added resources by tag and apply one retention policy.
Which configuration is most appropriate?
Use an AWS Backup plan with a tag-based resource assignment to automate backups across the target services.
Detailed explanation
A plan centralizes the schedule and retention, while tags automatically select resources across supported services.
A plan centralizes the schedule and retention, while tags automatically select resources across supported services.
Implementation and retention become fragmented, and new resources still require manual enrollment.
Implementation and retention become fragmented, and new resources still require manual enrollment.
Log collection does not create restorable snapshots or database backups.
Log collection does not create restorable snapshots or database backups.
Health checks observe reachability but do not create recovery points.
Health checks observe reachability but do not create recovery points.
Check official documentation
Compare the following points with the official documentation.
AWS Backup backup plans and tag-based resource assignmentsの公式説明を確認する。
What to confirm
バックアッププラン、タグ選択、保持設定の関係を説明できる。
Key points
- AWS Backup
- Backup plan
- Tag-based assignment
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Policy consistency
A single plan keeps schedule and retention consistent across resource types.
Automatic enrollment
Tags let newly added matching resources enter the protection scope without hand-editing scripts.