Answer-first summary for fast verification
Answer: Provision an AWS Storage Gateway Volume Gateway stored volume with the same amount of disk space as the existing file storage volume. Mount the Volume Gateway stored volume to the existing file server by using iSCSI, and copy all files to the storage volume. Configure scheduled snapshots of the storage volume. To recover from a disaster, restore a snapshot to an Amazon Elastic Block Store (Amazon EBS) volume and attach the EBS volume to an Amazon EC2 instance.
## Explanation **Correct Answer: D** **Why Option D is correct:** 1. **Least amount of change to existing infrastructure**: The Volume Gateway stored volume uses the same iSCSI protocol that the company already uses, so no changes to applications or access methods are required. 2. **Immediate access without latency**: Stored volumes keep the entire dataset locally on-premises while asynchronously backing up to AWS. This ensures low-latency access to all files. 3. **Handles hundreds of TB**: Stored volumes can accommodate large datasets by providing the same amount of disk space as the existing storage. 4. **Disaster recovery capability**: Scheduled snapshots provide point-in-time recovery, and EBS volumes can be restored from these snapshots in AWS. **Why other options are incorrect:** **Option A (S3 File Gateway):** - Requires modifying applications to use NFS protocol instead of iSCSI - Only caches 10TB locally, which is insufficient for "hundreds of TB" of data - Users would experience latency when accessing non-cached files **Option B (Tape Gateway):** - Designed for backup/archival, not for immediate file access - Nightly backups mean data loss up to 24 hours - Restore process is slow and doesn't provide immediate access **Option C (Volume Gateway cached volume):** - Only caches 10TB locally, insufficient for the dataset size - Would require frequently accessed data to be fetched from AWS, causing latency - Not suitable for "immediate access to all file types" requirement **Key AWS Services:** - **AWS Storage Gateway Volume Gateway (stored volume)**: Maintains entire dataset locally with async backup to AWS - **Amazon EBS**: Provides block storage for EC2 instances in AWS - **iSCSI**: Standard protocol for block-level storage access that the company already uses This solution provides seamless integration with existing infrastructure while meeting both the immediate access requirements and disaster recovery needs.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company wants to implement a disaster recovery plan for its primary on-premises file storage volume. The file storage volume is mounted from an Internet Small Computer Systems Interface (iSCSI) device on a local storage server. The file storage volume holds hundreds of terabytes (TB) of data.
The company wants to ensure that end users retain immediate access to all file types from the on-premises systems without experiencing latency.
Which solution will meet these requirements with the LEAST amount of change to the company's existing infrastructure?
A
Provision an Amazon S3 File Gateway as a virtual machine (VM) that is hosted on premises. Set the local cache to 10 TB. Modify existing applications to access the files through the NFS protocol. To recover from a disaster, provision an Amazon EC2 instance and mount the S3 bucket that contains the files.
B
Provision an AWS Storage Gateway tape gateway. Use a data backup solution to back up all existing data to a virtual tape library. Configure the data backup solution to run nightly after the initial backup is complete. To recover from a disaster, provision an Amazon EC2 instance and restore the data to an Amazon Elastic Block Store (Amazon EBS) volume from the volumes in the virtual tape library.
C
Provision an AWS Storage Gateway Volume Gateway cached volume. Set the local cache to 10 TB. Mount the Volume Gateway cached volume to the existing file server by using iSCSI, and copy all files to the storage volume. Configure scheduled snapshots of the storage volume. To recover from a disaster, restore a snapshot to an Amazon Elastic Block Store (Amazon EBS) volume and attach the EBS volume to an Amazon EC2 instance.
D
Provision an AWS Storage Gateway Volume Gateway stored volume with the same amount of disk space as the existing file storage volume. Mount the Volume Gateway stored volume to the existing file server by using iSCSI, and copy all files to the storage volume. Configure scheduled snapshots of the storage volume. To recover from a disaster, restore a snapshot to an Amazon Elastic Block Store (Amazon EBS) volume and attach the EBS volume to an Amazon EC2 instance.