AIncorrect
Keep them all just in case.
Keeping unused resources means charges keep accruing even though they are not used.
From a cost optimization perspective this is wasteful, so it is incorrect.
From a cost optimization perspective, what is the MOST appropriate action for EBS volumes that are no longer used and Elastic IPs that remain even though nothing is running?
1 / 1
Select an answer
CorrectD
Explanation
A question asking the cost optimization action for unused resources.
- 1「no longer used」Unused, possibly incurring wasted charges
- 2「cost optimization」Eliminate wasted cost
- 3「remain」Left-over resources need to be inventoried
BIncorrect
Replace them with larger volumes.
Making unused resources larger only increases wasted cost.
It runs counter to cost optimization, so it is incorrect.
CIncorrect
Back up everything and then delete it without checking usage.
The idea of taking a backup (snapshot) before deleting is on the safe side, but deleting everything in bulk without checking usage risks erasing resources that are still needed.
Moreover, backing up everything unconditionally adds new snapshot storage charges, and some items, such as Elastic IPs, cannot be backed up. The appropriate approach is to first confirm that something is unused and delete only what is unneeded, so this is incorrect.
DCorrect
After confirming they are unused, delete the unneeded resources.
This is correct. Unused EBS volumes and unassociated Elastic IPs can incur charges just by being left in place. By confirming they are unneeded and then deleting (or releasing) them, you eliminate wasted cost. Taking inventory of and deleting unused resources is a basic of cost optimization.
Key Takeaway
"Unused resources" and "cost optimization" mean confirm and delete (take inventory). Unassociated Elastic IPs and unattached EBS can also be billable. Keeping or enlarging them increases waste.