Q61 — AWS SAA-C03 Ch.16

Question 61 of 100 | ← Chapter 16

Q1261. A company hosts a production database on an Amazon Elastic Block Store (Amazon EBS) backed Amazon EC2 instance. As part of an annual disaster recovery exercise,the company needs to restore recent EBS snapshots to a new EC2 instance in a second Availability Zone.After the snapshots are restored to EBS volumes,the resulting volumes must deliver all of their provisioned performance.The company must perform validation tests on the restored data as quickly as possible.Which configuration will meet these requirements?

• A. 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. ✓
• B. 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.
• C. Specify Provisioned lOPS 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.
• D. Specify Provisioned lOPS 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

Correct Answer: A. 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.

Explanation

The correct answer is A. 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.Explanation:The company needs to restore EBS snapshots to a new EC2 instance in a second Availability Zone (AZ) while ensuring:Full provisioned performance (no initialization lag).Fast validation testing (minimal delay after restoration). EBS Fast Snapshot Restore (FSR) is the AWS service designed to eliminate the performance impact of snapshot restoration by fully initializing snapshots in advance.Why Option A is Correct:EBS Fast Snapshot Restore (FSR):Pre-initializes snapshots to ensure full IOPS/throughput performance immediately after restoration. Must be enabled per AZ where the restored volumes will be used. Reduces validation time (no need to wait for background initialization).Restoration Process:Enable FSR on the snapshots for the target AZ (second AZ). Create new EBS volumes from the snapshots in the second AZ.Attach to a new EC2 instance for testing.Why the Other Options Are Incorrect:B. Enable FSR on the current AZ (not the target AZ)FSR must be enabled in the AZ where volumes are created, not the original AZ. Restored volumes in the second AZ will not benefit from FSR.C. Specify Provisioned IOPS on the snapshotsSnapshots do not have IOPS settings--IOPS are assigned to volumes, not snapshots. Even if volumes are created with Provisioned IOPS, they still need FSR for full performance immediately. D. Specify Provisioned IOPS on existing volumes, then snapshot This only affects the original volumes, not the restored ones. Restored volumes will still require initialization, delaying validation.Key Considerations:FSR Cost:FSR incurs additional costs (per snapshot, per AZ, per hour). Only enable it when needed (e.g., during disaster recovery drills).Alternative (Without FSR):If FSR is unavailable, restored Provisioned IOPS (io1/io2) volumes will gradually reach full performance (background initialization).Validation would be delayed until initialization completes.Conclusion:Option A is the best choice because:FSR ensures immediate full performance in the target AZ.Minimizes validation time (no initialization delay).Follows AWS best practices for disaster recovery testing.