Which solution will meet these requirements?
Take EBS snapshots of the production EBS volumes. Restore the snapshots onto EC2 instance store volumes in the test environment.
Configure the production EBS volumes to use the EBS Multi-Attach feature. Take EBS snapshots of the production EBS volumes. Attach the production EBS volumes to the EC2 instances in the test environment.
Take EBS snapshots of the production EBS volumes. Create and initialize new EBS volumes. Attach the new EBS volumes to EC2 instances in the test environment before restoring the volumes from the production EBS snapshots.
Take EBS snapshots of the production EBS volumes. Turn on the EBS fast snapshot restore feature on the EBS snapshots. Restore the snapshots into new EBS volumes. Attach the new EBS volumes to EC2 instances in the test environment.
Explanations:
Restoring EBS snapshots to instance store volumes is not feasible, as instance store volumes cannot be restored from snapshots.
EBS Multi-Attach allows multiple EC2 instances to attach to the same EBS volume, but it does not support cloning data for a test environment without affecting production. This option also does not address the requirement of isolating modifications from the production environment.
While this option involves taking EBS snapshots and creating new EBS volumes, it does not mention the use of fast snapshot restores, which is crucial for minimizing time when cloning large amounts of data.
This option takes EBS snapshots and uses the fast snapshot restore feature to minimize the time required to clone data, while ensuring modifications do not affect the production environment by creating new EBS volumes for the t
If I had to guess, I’d say the answer is:
Take EBS snapshots of the production EBS volumes. Turn on the EBS fast snapshot restore feature on the EBS snapshots. Restore the snapshots into new EBS volumes. Attach the new EBS volumes to EC2 instances in the test environment.