Explanation:
EBS snapshot lifecycle policies (via Data Lifecycle Manager) automate creation and retention. Snapshots are incremental by default, saving only changed blocks to minimize storage. Snapshots are not S3 objects for S3 Lifecycle. Multi-Attach is for access, not backup. Copying increases cost.
Ultimate access to all questions.
A regional logistics firm operates Amazon EC2 workloads backed by Amazon EBS volumes. The team needs a cost-efficient backup approach that maintains durability and automates daily and weekly retention for about 45 days while keeping storage usage minimal. Which actions should they take? (Choose 2)
A
Configure EBS snapshot lifecycle policies for automated creation and time based retention
B
Use S3 Lifecycle rules to transition EBS snapshots to S3 Glacier Deep Archive
C
Enable EBS Multi-Attach on volumes to improve durability
D
Rely on incremental EBS snapshots so only changed blocks are saved
E
Copy snapshots to a separate AWS account to enhance resilience
No comments yet.