Modifying EBS General Purpose SSD Volumes
Question
An AWS Solution architect who uses EBS General Purpose SSD (gp2) volume type for his EBS volumes now wants to modify some of these volumes.
What options would you suggest? (Select TWO)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct AnswerA, D.
The EBS volume types can be modified in flight without the volume being detached or the instance being restarted.
However, some limitations need to be noticed.
The details are in https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html.
Option A is CORRECT: Because the root volume can be changed to io1 such as:
Option B is incorrect: Because a gp2 volume that is attached to an instance as a root volume cannot be modified to an st1 or sc1 volume.
Check https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html.
Option C is incorrect: Because there is no gp4 type of volume available.
Option D is CORRECT: Because the volume size 1TB is suitable for Throughput Optimized HDD (st1):
Sure, I'd be happy to explain the options available for modifying EBS volumes from the General Purpose SSD (gp2) volume type.
Option A: A 50GB gp2 root volume can be modified to an EBS Provisioned IOPS SSD (io1) after stopping the instance. Explanation: This option is correct because when you stop an instance, you can modify the EBS root volume type. In this case, the current gp2 volume can be modified to an EBS Provisioned IOPS SSD (io1) volume type, which provides higher performance and consistent IOPS for latency-sensitive workloads.
Option B: A gp2 volume attached to an instance as a root volume can be modified to a Throughput Optimized HDD (st1) volume. Explanation: This option is incorrect because you cannot modify the volume type of a root volume. Root volumes are created from Amazon Machine Images (AMIs) and cannot be modified after the instance is launched.
Option C: A 1GB gp2 volume attached to an instance as a non-root volume can be modified to a gp3 volume. Explanation: This option is partially correct because you can modify a gp2 volume to a gp3 volume, which provides better performance at a lower cost. However, the minimum size for gp3 volumes is 1 GiB, not 1 GB. GiB stands for gibibyte, which is a binary multiple of a byte and is equal to 2^30 bytes. On the other hand, GB stands for gigabyte, which is a decimal multiple of a byte and is equal to 10^9 bytes. Therefore, the correct size for a gp3 volume would be 1 GiB, not 1 GB.
Option D: A 1TB gp2 volume attached to an instance as a non-root volume can be modified to a Throughput Optimized HDD (st1) volume without stopping the instance or detaching the volume. Explanation: This option is incorrect because you cannot modify the volume type of an EBS volume without creating a new volume and copying the data over. Therefore, to modify a gp2 volume to a Throughput Optimized HDD (st1) volume, you would need to create a new st1 volume, copy the data from the gp2 volume to the st1 volume, and then detach the gp2 volume and attach the st1 volume to the instance.
