Q: 7
A company that runs many workloads on AWS has an Amazon EBS spend that has increased over
time. The DevOps team notices there are many unattached
EBS volumes. Although there are workloads where volumes are detached, volumes over 14 days old
are stale and no longer needed. A DevOps engineer has been tasked with creating automation that
deletes unattached EBS volumes that have been unattached for 14 days.
Which solution will accomplish this?
Options
Discussion
C . CloudWatch + Lambda lets you actually target unattached volumes, while B is a common trap since Data Lifecycle Manager doesn't work for unattached EBS. Easy to miss that detail, but I've seen similar in exam prep.
Its C no question
Gotta agree with C here. Lambda plus CloudWatch Events can automate both tagging and cleanup, which is exactly what's needed if you want volumes gone after being unattached for 14 days. Data Lifecycle Manager (B) can't do this for unattached EBS volumes-I've checked docs before. If I'm missing something, let me know!
Pretty sure I ran into a similar one in exam mentioned in recent exam reports, most picks went with C for the Lambda tagging and delete approach.
Probably C. Data Lifecycle Manager (B) doesn't support deleting unattached EBS volumes, that's a common trap option. The Lambda with tagging logic in C is the way most real-world automation handles this, pretty sure. Happy to be corrected though.
C tbh. Lambda triggered by CloudWatch Events is the standard way to automate this kind of cleanup for unattached EBS volumes.
B for me since Data Lifecycle Manager deals with EBS lifecycle, so seems logical to use it for scheduling deletions. Not 100% sure if it supports unattached volumes directly, but that's the closest fit I see.
C . Data Lifecycle Manager (B) can’t handle unattached EBS volumes, which trips up a lot of people. The Lambda tagging method in C fits the automation need. Not 100% sure if there’s a new AWS feature for this yet, correct me if so.
Not sure B works here, Data Lifecycle Manager won't delete unattached EBS volumes. C is the safer pick in this scenario.
B or C? Data Lifecycle Manager in B seems like it should handle this, but maybe I'm missing something in the docs. Easy to pick B by mistake if you don't remember its limitations.
Be respectful. No spam.
