A company runs a transactional workload on an EC2 instance backed by a 400 GiB General Purpose SSD (gp2) volume. Monitoring shows the application needs a sustained 9,000 IOPS and 350 MiB/s of throughput, but the gp2 volume delivers only its size-derived baseline and the team does not want to grow the volume just to gain performance. A solutions architect must raise IOPS and throughput at the lowest cost without changing the volume size. Which action meets the requirement?
- AIncrease the gp2 volume size to 3,000 GiB so the size-derived baseline reaches the required IOPS, then enable an instance burst balance to cover throughput peaks.
- BMigrate the volume to Provisioned IOPS SSD (io2) and provision 9,000 IOPS, accepting the higher per-IOPS price for the guaranteed performance the workload needs.
- CAttach a second gp2 volume of the same size and stripe the two in a RAID 0 array so the combined baseline meets the IOPS and throughput target.
- DMigrate the volume to General Purpose SSD (gp3) and provision the 9,000 IOPS and 350 MiB/s throughput independently of the 400 GiB capacity. Correct
Why A is wrong: Growing a gp2 volume to lift baseline IOPS forces the team to pay for unused capacity, which directly contradicts the requirement to avoid increasing the volume size.
Why B is wrong: io2 can supply the IOPS but it costs more per provisioned IOPS than gp3, so it fails the lowest-cost requirement when gp3 already meets the target.
Why C is wrong: RAID 0 striping doubles cost and adds management effort while keeping the size-tied gp2 model, making it more expensive and complex than provisioning gp3 directly.
Why D is correct: gp3 decouples IOPS and throughput from capacity, so the team can provision exactly 9,000 IOPS and 350 MiB/s on the existing 400 GiB at lower cost than gp2.