Migrating file data to S3 while keeping SMB access via Storage Gateway
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?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
A Storage Gateway file gateway bridges SMB/NFS on premises to an S3-backed file share, so the application retains SMB access during the transition while the data actually resides in S3.
An on-prem app using SMB must move its shared data to S3 but keep SMB access until code is rewritten. A Storage Gateway file gateway deployed on-prem presents an SMB file share backed by S3, letting the existing app keep SMB access while the data lands in the S3 bucket.
Choosing FSx for Windows (Option A) stores data in FSx rather than the required S3 bucket, and AWS SMS (Option C) migrates servers rather than providing a continued SMB-to-S3 bridge.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D creates the S3 bucket as the ultimate store and deploys a Storage Gateway file gateway on an on-prem VM with an SMB file share that stores data in that bucket. The existing application keeps S3-compatible SMB access through the gateway while the underlying data is already in S3, exactly meeting the transitional requirement.Why the Other Options Are Wrong
Option A uses FSx for Windows, which stores data in FSx rather than the mandated S3 bucket. Option B copies data to S3 but provides no SMB access for the still-on-prem application. Option C (AWS SMS) migrates a file server to EC2 and does not maintain the SMB-to-S3 bridge during the transition.Community Comment Notes
The community vote is overwhelmingly D (95). TonytheTiger links the AWS Architecture Blog on connecting S3 via File Gateway. A removed comment argued for A, but A does not place data in the required S3 bucket during the transition.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →