Which is a recommended tip to control block storage costs?

• A. Attach volumes to multiple instances
• B. Get rid of orphaned volumes
• C. Disable volume autoscaling
• D. Increase the number of higher IOPS volumes

Answer: (B)

The main idea here is to stop paying for storage you don’t actually need. In block storage, you’re charged for the provisioned capacity of each volume even when it’s detached from any instance. Those detached, unused volumes—often called orphaned volumes—continue to incur costs until you delete them or move the data elsewhere. So the best practice to curb block storage expenses is to identify and remove orphaned volumes, freeing up the allocated storage and stopping ongoing charges.

To apply this, regularly audit your volumes, delete any that are no longer needed, and ensure you have backups or snapshots if you want to preserve data before deleting. The other options don’t help with cost control: attaching volumes to multiple instances isn’t a reliable or general cost-saving tactic, and increasing high-IOPS volumes or disabling autoscaling would typically raise costs rather than reduce them.