A solutions architect works for a government agency that has strict disaster recovery requirements. All Amazon Elastic Block Store (Amazon EBS) snapshots are required to be saved in at least two additional AWS Regions. The agency also is required to maintain the lowest possible operational overhead.
Which solution meets these requirements?
Configuring a policy in Amazon Data Lifecycle Manager (Amazon DLM) is the most appropriate solution. DLM automates the process of copying EBS snapshots to additional regions, ensuring compliance with the disaster recovery requirements while minimizing operational overhead. It provides a straightforward, automated way to manage snapshots without requiring additional setup or management, aligning perfectly with the need for low operational overhead.
The best answer is A: configuring Amazon Data Lifecycle Manager to automate the copying of EBS snapshots to additional regions, is the most suitable solution. It meets the requirement of minimal operational overhead while ensuring that snapshots are stored in multiple regions for disaster recovery. This approach is straightforward and leverages AWS's native capabilities for snapshot management. Can't be C...EBS snapshots are not stored in S3 in a direct manner that would allow the use of S3 Cross-Region Replication. This option seems to misunderstand the nature of EBS snapshots and S3 integration.
EBS snapshot are stored in S3.
Indeed, you can do a cross-Region snapshot copy with AWS Backup, but ans “C” states to do a local-Region copy, then from the S3 console to run a S3 cross-Region replication, which is NOT possible. See the text and link below. “EBS snapshots are stored in Amazon S3, in S3 buckets that you CAN’T access directly. You can create and manage your snapshots using the Amazon EC2 console or the Amazon EC2 API. You can't access your snapshots using the Amazon S3 console or the Amazon S3 API.” https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html So, correct ans is “A”.
"You can now copy snapshots across regions using Data Lifecycle Manager (DLM). You can enable policies which, along with create, can now also copy snapshots to one or more AWS region(s). Copies can be scheduled for up to three regions from a single policy and retention periods are set for each region separately." https://aws.amazon.com/about-aws/whats-new/2019/12/amazon-data-lifecycle-manager-enables-automation-snapshot-copy-via-policies/
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/snapshot-lifecycle.html It help's - Create disaster recovery backup policies that back up data to isolated Regions or accounts.
https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-data-lifecycle-manager-now-automates-copying-ebs-snapshots-across-accounts/ fully automated and no overhead. Answer A
Answer is C. Therefore, option C is the most efficient and cost-effective solution that aligns with the agency's strict disaster recovery requirements while minimizing operational complexity.
How AWS Backup create Snaphot?
yes. i'm researching and saw that: https://docs.aws.amazon.com/prescriptive-guidance/latest/backup-recovery/new-ebs-volume-backups.html#amazon-dlm
CRR is a feature in AWS S3 that automatically replicates data from one S3 bucket in one AWS region to another S3 bucket in a different region. the requirements here to send backup to two regions
AWS Backup does not store snapshots in Amazon S3: AWS Backup stores the EBS snapshots in the same AWS Region where the EBS volumes reside. It does not store the snapshots in Amazon S3 buckets.
"A" - correct.
A (Amazon Data Lifecycle Manager) could work, but it's more suitable for lifecycle management tasks such as creating, retaining, and deleting EBS snapshots based on defined policies. It doesn't inherently handle cross-region replication.
Option A. EBS Data Lifecycle manager supports automated cross region snapshot. https://aws.amazon.com/about-aws/whats-new/2019/12/amazon-data-lifecycle-manager-enables-automation-snapshot-copy-via-policies/
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/snapshot-ami-policy.html
C ans a IS not correct Snapshots must be archived in the same Region in which they were created. If you enabled cross-Region copy and snapshot archiving, Amazon Data Lifecycle Manager does not archive the snapshot copy.
C Amazon data lifecycle manager can't copy snapshots. AWS backup has cross-Region copy feature https://aws.amazon.com/getting-started/hands-on/amazon-ebs-backup-and-restore-using-aws-backup/#:~:text=same%20AWS%20Region%20(-,however%2C%20see%20step%203.2%20for%20information%20on%20cross%2DRegion%20copy,-).%20This%20tutorial%20uses
Since 2019, DLM can copy to other regions. See https://aws.amazon.com/about-aws/whats-new/2019/12/amazon-data-lifecycle-manager-enables-automation-snapshot-copy-via-policies/ I'm pretty sure the answer is A
For me A would be the solution. C will imply copying the ebs snapshots to s3, why not using directly the AWS Backup cross-region backup copy feature?
Answer is C
should be C