AWS Certified Solutions Architect - Associate free question 7 / 10 · Domain 3: Design High-Performing Architectures
A gp2 data volume attached to a Nitro-based EC2 instance is running short of space as data grows. The team wants to increase the capacity and change the volume type to gp3 to improve performance as well. Which approach with little impact on the application is correct?
- Change with Elastic Volumes. Going from gp2 to gp3 without specifying IOPS and throughput drops to gp3's minimum performance, so specify the values when you change
- Change the capacity and type with Elastic Volumes without detaching the volume, and extend the file system on the operating system side before using the added capacity
- Change the capacity and type with Elastic Volumes, and when the data shrinks in the future, use the same operation to make the capacity smaller again
- Change with Elastic Volumes without detaching, and if it does not work out, cancel the change request and return to the original type
Show the answer and explanation
Answer: B
Why this is correct
With Amazon EBS Elastic Volumes, you can do three things: increase the volume capacity, change the volume type, and adjust performance. If the instance supports Elastic Volumes, you can make the change without detaching the volume or restarting the instance, and you can keep using the application while the change is in progress. A change can take from a few minutes to a few hours, but a capacity increase takes effect once the volume enters the optimizing state, which is usually a matter of seconds. After you increase the capacity, you extend the file system on the operating system side to use the added space.
Why the other options are wrong
"Change with Elastic Volumes. Going from gp2 to gp3 without specifying IOPS and throughput drops to gp3's minimum performance, so specify the values when you change" … The guide says that when you change from gp2 to gp3 without specifying IOPS or throughput, EBS automatically assigns the higher of the performance equivalent to the original gp2 and the gp3 baseline. Performance does not fall to the gp3 baseline just because you left the values out. You can change the capacity and type without detaching the volume.
"Change with Elastic Volumes without detaching, and if it does not work out, cancel the change request and return to the original type" … The guide says that you cannot cancel a modification request you have submitted. Until one modification completes, you cannot submit another for the same volume, and there is a limit on the number of modifications within a period, so you cannot proceed on the assumption that you will cancel if it does not work out.
"Change the capacity and type with Elastic Volumes, and when the data shrinks in the future, use the same operation to make the capacity smaller again" … With Elastic Volumes you can increase capacity, but you cannot decrease it. To make a volume smaller, you create a new, smaller volume and move the data with an application tool such as rsync or robocopy. If you take a large volume expecting to return later, you keep paying for unused capacity.
Related settings
When errors occur, or with earlier-generation instances, you need steps such as detaching the volume or stopping the instance. The time a modification takes is not necessarily proportional to the size of the volume, and it is longer for a volume that has not been initialized. There is no charge for the modification itself, and you are billed at the new configuration from the time the modification starts.