DEA-C01 · Question #72
A company is planning to upgrade its Amazon Elastic Block Store (Amazon EBS) General Purpose SSD storage from gp2 to gp3. The company wants to prevent any interruptions in its Amazon EC2 instances tha
The correct answer is C. Change the volume type of the existing gp2 volumes to gp3. Enter new values for volume size,. The most operationally efficient way to upgrade EBS gp2 to gp3 without interruption or data loss is to modify the existing volume's type in place.
Question
A company is planning to upgrade its Amazon Elastic Block Store (Amazon EBS) General Purpose SSD storage from gp2 to gp3. The company wants to prevent any interruptions in its Amazon EC2 instances that will cause data loss during the migration to the upgraded storage. Which solution will meet these requirements with the LEAST operational overhead?
Options
- ACreate snapshots of the gp2 volumes. Create new gp3 volumes from the snapshots. Attach the
- BCreate new gp3 volumes. Gradually transfer the data to the new gp3 volumes. When the transfer
- CChange the volume type of the existing gp2 volumes to gp3. Enter new values for volume size,
- DUse AWS DataSync to create new gp3 volumes. Transfer the data from the original gp2 volumes
How the community answered
(30 responses)- A7% (2)
- C90% (27)
- D3% (1)
Why each option
The most operationally efficient way to upgrade EBS gp2 to gp3 without interruption or data loss is to modify the existing volume's type in place.
Creating snapshots and new volumes requires detaching the old volume and attaching a new one, which causes downtime for the EC2 instance.
Gradually transferring data to new volumes is a complex and time-consuming process that requires application-level coordination and introduces significant operational overhead.
Modifying an existing EBS volume's type from gp2 to gp3 is an in-place operation that allows you to change volume size, IOPS, and throughput while the volume remains attached and available to the EC2 instance, thus preventing interruptions and data loss. This method minimizes operational overhead compared to creating new volumes and migrating data.
AWS DataSync is designed for large-scale data transfer between storage services or on-premises to AWS, not for in-place EBS volume type modifications for an attached volume, and would incur higher operational overhead.
Concept tested: In-place EBS volume modification
Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modify-volume.html
Topics
Community Discussion
No community discussion yet for this question.