A company uses Amazon EC2 instances and Amazon Elastic Block Store (Amazon EBS) volumes to run an application. The company creates one snapshot of each EBS volume every day to meet compliance requirements. The company wants to implement an architecture that prevents the accidental deletion of EBS volume snapshots. The solution must not change the administrative rights of the storage administrator user.
Which solution will meet these requirements with the LEAST administrative effort?
To prevent the accidental deletion of EBS volume snapshots without changing the administrative rights of the storage administrator user, locking the EBS snapshots is the most effective solution. Locking a snapshot ensures that it cannot be deleted, thus fulfilling the requirement of preventing accidental deletions with minimal administrative effort.
Locking EBS Snapshots (Option D): The "lock" feature in AWS allows you to prevent accidental deletion of resources, including EBS snapshots. This can be set at the snapshot level, providing a straightforward and effective way to meet the requirements without changing the administrative rights of the storage administrator user.
Typical use case for object lock aka D
D: Exactly what a locked EBS snapshot is used for https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-snapshot-lock.html
I will go for D
correct option D