SAP-C02 · Question #690
A company is planning to migrate an application from on premises to the AWS Cloud. The company will begin the migration by moving the application's underlying data storage to AWS. The application…
The correct answer is D. Create an S3 bucket for the application. Deploy a new AWS Storage Gateway file gateway on an. Option D is correct because AWS Storage Gateway's file gateway mode deploys as an on-premises virtual appliance that exposes an SMB share to local application servers, while transparently storing all data in a backend S3 bucket - satisfying both the SMB access requirement and…
Question
A company is planning to migrate an application from on premises to the AWS Cloud. The company will begin the migration by moving the application's underlying data storage to AWS. The application data is stored on a shared file system on premises, and the application servers connect to the shared file system through SMB. A solutions architect must implement a solution that uses an Amazon S3 bucket for shared storage. Until the application is fully migrated and code is rewritten to use native Amazon S3 APIs, the application must continue to have access to the data through SMB. The solutions architect must migrate the application data to AWS to its new location while still allowing the on- premises application to access the data. Which solution will meet these requirements?
Options
- ACreate a new Amazon FSx for Windows File Server file system. Configure AWS DataSync with
- BCreate an S3 bucket for the application. Copy the data from the on-premises storage to the S3
- CDeploy an AWS Server Migration Service (AWS SMS) VM to the on-premises environment. Use
- DCreate an S3 bucket for the application. Deploy a new AWS Storage Gateway file gateway on an
How the community answered
(60 responses)- A30% (18)
- B7% (4)
- C13% (8)
- D50% (30)
Explanation
Option D is correct because AWS Storage Gateway's file gateway mode deploys as an on-premises virtual appliance that exposes an SMB share to local application servers, while transparently storing all data in a backend S3 bucket - satisfying both the SMB access requirement and the S3-as-storage requirement simultaneously during the transition period.
Option A is wrong because FSx for Windows File Server, while SMB-compatible, is a dedicated managed file system - not S3-backed storage. It doesn't fulfill the requirement that data reside in S3.
Option B is wrong because simply copying data to S3 leaves the on-premises application with no SMB access path - raw S3 only exposes data via its own HTTP-based API, not SMB.
Option C is wrong because AWS Server Migration Service migrates virtual machines, not file data or storage systems - it's the wrong tool category entirely.
Memory tip: Think of Storage Gateway as a protocol translator - whenever an exam question asks "keep using on-premises protocols (SMB/NFS) but store data in AWS (S3)," Storage Gateway file gateway is almost always the answer. The pattern is: legacy protocol in → S3 out.
Topics
Community Discussion
No community discussion yet for this question.