A computer-aided dispatch (CAD) database on Amazon EC2 uses Amazon EBS. Metrics show moderate IOPS needs well within gp3 capabilities, but the volume was provisioned as io2 for “future proofing.” What cost-aware storage change should the architect recommend?
Select an answer to reveal the explanation.
Short Explanation
Paying io2 prices for gp3-level IOPS is like leasing a race car to drive to the grocery store. Right-size to gp3 when metrics say you don’t need extreme provisioned IOPS. Extra idle io2 disks, Glacier for CAD queries, or blind HDD swaps miss the cost/performance match.
Full Explanation
Cost-optimized block storage means selecting the EBS volume type that meets measured performance without over-provisioning. gp3 generally offers a strong price/performance default for many transactional workloads; io2 is appropriate when higher provisioned IOPS/reliability characteristics are required. Unused extra io2 volumes increase cost. Glacier classes and magnetic HDD choices are mismatched to low-latency CAD database needs. Prefer gp3 when extreme io2-level IOPS are not required.