AWS Certified Solutions Architect – Associate (SAA-C02) — Question 373

A company has an on-premises application that collects data and stores it to an on-premises NFS server. The company recently set up a 10 Gbps AWS Direct
Connect connection. The company is running out of storage capacity on premises. The company needs to migrate the application data from on premises to the
AWS Cloud while maintaining low-latency access to the data from the on-premises application.
What should a solutions architect do to meet these requirements?

Answer options

• A. Deploy AWS Storage Gateway for the application data, and use the file gateway to store the data in Amazon S3. Connect the on-premises application servers to the file gateway using NFS.
• B. Attach an Amazon Elastic File System (Amazon EFS) file system to the NFS server, and copy the application data to the EFS file system. Then connect the on-premises application to Amazon EFS.
• C. Configure AWS Storage Gateway as a volume gateway. Make the application data available to the on-premises application from the NFS server and with Amazon Elastic Block Store (Amazon EBS) snapshots.
• D. Create an AWS DataSync agent with the NFS server as the source location and an Amazon Elastic File System (Amazon EFS) file system as the destination for application data transfer. Connect the on-premises application to the EFS file system.

Correct answer: A

Explanation

AWS Storage Gateway's file gateway configuration caches frequently accessed data locally, ensuring low-latency access for the on-premises application while seamlessly storing the bulk of the data in Amazon S3. Connecting directly to Amazon EFS over Direct Connect does not provide a local caching mechanism, resulting in higher latency for file operations compared to a local gateway. Volume gateway is incorrect because it presents block storage interfaces (iSCSI) rather than the required NFS file interface.