Exam AWS DevOps Engineer Professional topic 1 question 64 discussion

I'll go with C Reference: https://aws.amazon.com/blogs/mt/controlling-your-aws-costs-by-deleting-unused-amazon-ebs-volumes/

D: https://github.com/aws/Trusted-Advisor-Tools/tree/master/UnderutilzedEBSVolumes This is a serverless (Lambda) application that reacts to Trusted Advisor warnings via CloudWatch rules to detect and delete Underutilized EBS volumes - volumes that have been unattached or had low I/O for a number of days. The app will only delete idle, unattached volumes after successfully taking a snapshot. It sends an email with information on how to recover the volume from the snapshot.

I will go with C: Here are tolls that can be used to automate this: https://catalog.workshops.aws/msft-costopt/en-US/storage/ebs/unattached-ebs-volumes https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/delete-unused-amazon-elastic-block-store-amazon-ebs-volumes-by-using-aws-config-and-aws-systems-manager.html B is not correct because Amazon Data Lifecycle Manager manages EBS snapshots not volumes and EBS backed AMIs https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/snapshot-lifecycle.html

A - only checks if volume or related instance is marked for termination/deletion. Nope. B. DLM cannot detect unattached volumes. Go actually try & configure it. You filter on tag & say delete volume after 14 days but you cannot specify if its attach or not - just tag filtering. D. Does not work. C. Only viable option.

Force to choose C A. will not work correctly. B. DLM can work only with snapshots C. Correct D. Trusted advisor cannot check for unattached EBS for 14 days - it can only check for underutilized volumes - those volumes can also be attached and the check is for 7 days. "Yellow: A volume is unattached or had less than 1 IOPS per day for the past 7 days."

Data Lifecycle Manager is the most straightforward solution https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/snapshot-lifecycle.html

Correct answer is C. D is incorrect because Trusted Advisor detects only under provisioned and over provisioned EBS volume meaning utilization. If the EBS volume is already deattached and not utilized by any EC2 instance, then I don't think Trusted Advisor would detect that. I am not very sure about it but that's my guess. C seems logically correct. Some folks didn't select C because they thought Lambda will tag the unattached EBS volume each day ( again and again). But thats not true. Lambda will do so only once per EBS volume and therefore will be able to detect if a specifc volume was unused for 14 days and then delete it.

It should be C not B. Data Lifecycle Manager is for EBS snapshots not the volume. https://aws.amazon.com/blogs/storage/automating-amazon-ebs-snapshot-and-ami-management-using-amazon-dlm/

I'll go with C

https://aws.amazon.com/blogs/mt/controlling-your-aws-costs-by-deleting-unused-amazon-ebs-volumes/

Amazon Data Lifecycle Manager cannot discover unattached disks and AWS Trusted Advisor can only discover currently unattached disks This question has a complicated request, so I have no choice but to rely on the Lambda function

I will go with C A. AWS Config Checks if EBS volumes are attached to EC2 instances. If the volume is 'available state', then you configure CloudWatch Event to invoke a Lambda function. Lambda function will take care of deletion. Note that Config does not only trigger unused EBS volumes for 14 days, but every unused EBS volume(irrespective of the number of days its been unused). Though it can be made work, its not the most efficient solution B. Data Lifecycle Manager only looks at EBS snapshot lifecycle. Not the EBS volumes itself C. Lambda function triggered periodically and tagging the new volumes and checking if already tagged volumes are >= 14 days old. If it finds any >= 14 days old, Lambda will delete them 4. Trusted advisor does not check for unused volumes, it checks for under utilised EBS volumes So C is the best answer in this context.

At first I thought Ans D seems the best option - but this answers creates a snapshot. creating a snapshot is not a requirement. So, A seems to be the best option.

Though few of the the answers are poorly worded, D seems to be best of the lot. With A it is not clear how config will identify it is 14 days since volume was unattached, B works with lifecycle of snapshots, not directly with lifecycle of volume, C has a logic flaw if date is updated D. That leaves D(though it is not clear how D will be automated and why it is creating snapshots before delete when not asked in Qs.)

honestly there is no correct ans here. the closest is C, it would hv been logically doable if the tagging of current date is mentioned AFTER the function/logic that detects & delete 14 days old EBS. I choose B still. Though tt "Use Amazon EC2 and Amazon Data Lifecycle Manager to configure a volume lifecycle policy" line sounds so wrong.

D makes more sense. Trusted Advisor is designed to give you information about underutilized ebs volumes.

D maybe is valid, but i don't see any way to create a automatic way to detect, the C option at least is performing a daily task to validate the volumes