How can an EBS volume that is currently attached to an EC2 instance be migrated from one Availability Zone to
another?
A.
Detach the volume and attach it to another EC2 instance in the other AZ.
B.
Simply create a new volume in the other AZ and specify the original volume as the source.
C.
Create a snapshot of the volume, and create a new volume from the snapshot in the other AZ.
D.
Detach the volume, then use the ec2-migrate-voiume command to move it to another AZ.
C
Agree on C
While EBS volumes are locked to the Availability Zone in which they reside, snapshots are available throughout their region of residence).
c
C.
A
C. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumes.html: These snapshots can be used to create multiple new EBS volumes, expand the size of a volume, or move volumes across Availability Zones.
C
C
Why is A not an acceptable answer?
The question here is too generic. It did not specify the type of EBS.
For suppose you have an EBS of type general purpose SSD and you want to migrate data from another type of EBS.
Will A be the option?
No, right?
This Question is tricky.
The safest option would be going with c
https://aws.amazon.com/ebs/faqs/
C
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumes.html
refer to Data availability session:
After you create a volume, you can attach it to any EC2 instance in the same Availability Zone.
An EBS volume can be attached to only one instance at a time within the same Availability Zone.
C is the right answer.
It is not A because see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumes.html#EBSFeatures
An EBS volume can be attached to only one instance at a time within the same Availability Zone.
The keyword is migrate, not copy.
A is the right answer, we are migrating an EBS from a volume in Oregon-Boardman Availability Zone, to Oregon-Prineville Availability Zone, this is not the same as attaching an EBS volume to another EC2 within the same availability zone. So we detach from Oregon-Boardman, and attach in Oregon-Prineville.
C
C
C is correct answer after all.
I chose C,
EBS only attached to EC2 on the same AZ.
A is not feasible , the EBS can be attached to the instance in same AZ, I tried this through console and hence C is the only feasible and correct option
Correct answer is C
A cannot be right answer – you cannot attach a volume to an instance which is different availability zone.
agree!
Answer: C
snapshots can be used to create multiple new EBS volumes, expand the size of a
volume, or move volumes across Availability Zones.
A doesn’t work. I do this day to day at work, when you create volumes you specify AZ and it belongs to that AZ, you cannot attach it to an Instance in a different AZ. So C is the right answer