Back up EC2, a separate EBS volume, and RDS for MySQL daily in one account and Region, retaining recovery points for 30 days. Service support and the required IAM role permissions have been checked.
Manage a common schedule, retention, and destination while protecting only the selected resources. No cold-storage transition is required.
Which configuration is most appropriate?
Connect an AWS Backup plan, vault, and resource assignment with an IAM role to centrally manage daily backups and retention.
Detailed explanation
This connects policy, destination, and protected resources. Creating a plan alone does not complete resource assignment.
This connects policy, destination, and protected resources. Creating a plan alone does not complete resource assignment.
A vault is a destination, not a standalone schedule or resource selection.
A vault is a destination, not a standalone schedule or resource selection.
The name does not implement frequency, retention, or resource selection.
The name does not implement frequency, retention, or resource selection.
RDS settings do not centrally schedule and retain EC2 and separate EBS backups.
RDS settings do not centrally schedule and retain EC2 and separate EBS backups.
Check official documentation
Compare the following points with the official documentation.
Review rule schedules, retention, vaults, resource selection and IAM roles, and service-specific feature support.
Official references
What to confirm
Explain why a vault alone does not initiate backups and why jobs and recovery points must be checked.
Key points
- Backup plan
- Resource assignment
- Backup vault
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-04.
Foundation review
Connect policy, resources, and permissions
A plan rule sets frequency, start window, retention, and destination; a resource assignment selects resources and an execution role. Check feature availability and IAM/KMS access for the services and Region. A start window is not a guarantee of simultaneous snapshots across services.
Separate configuration from recoverability
A plan's existence is not proof of successful backups. Check failed jobs, omitted resources, and recovery-point timestamps and retention. If EC2 protection overlaps with separate volume backups, review coverage and duplicate cost. Test restored data and application behavior as part of operational validation.