Which configuration will meet these requirements?
Enable EBS fast snapshot restore (FSR) on the snapshots for the second Availability Zone. Create new EBS volumes in the second Availability Zone from the snapshots. Attach the new EBS volumes to a new EC2 instance.
Enable EBS fast snapshot restore (FSR) on the snapshots for the current Availability Zone. Create new EBS volumes in the second Availability Zone from the snapshots, Attach the new EBS volumes to a new EC2 instance.
Specify Provisioned IOPS on the snapshots, Create new EBS volumes in the second Availability Zone from the snapshots. Attach the new EBS volumes to a new EC2 instance.
Specify Provisioned IOPS on the existing EBS volumes. Create the snapshots. After the snapshots are completed, create new EBS volumes in the second Availability Zone from the snapshots. Attach the new EBS volumes to a new EC2 instance.
Explanations:
Enabling EBS fast snapshot restore (FSR) in the target Availability Zone ensures that the restored volumes can deliver their full provisioned performance immediately upon creation. This is the most efficient method for quick validation tests since the new EC2 instance can access the volumes with optimal performance.
Enabling FSR in the current Availability Zone does not affect the performance of volumes created in the second Availability Zone. Therefore, the volumes created from snapshots without FSR in the target zone will not deliver their provisioned performance immediately, delaying validation tests.
Specifying Provisioned IOPS on the snapshots does not affect the performance of the restored volumes since EBS snapshots themselves do not have performance settings. The performance is determined by the settings of the volumes created from those snapshots, and without enabling FSR in the target zone, the volumes will not have immediate provisioned performance.
While specifying Provisioned IOPS on existing EBS volumes ensures that the snapshots retain the IOPS capability, this option does not provide any immediate performance benefits when the new volumes are created in the second Availability Zone without enabling FSR. As such, the new volumes would still not deliver their full provisioned performance immediately, delaying validation tests.
As far as I can tell, the answer is:
Enable EBS fast snapshot restore (FSR) on the snapshots for the second Availability Zone. Create new EBS volumes in the second Availability Zone from the snapshots. Attach the new EBS volumes to a new EC2 instance.