Migrating SMB File Storage to AWS with Least Overhead
Short answer
C Use AWS DataSync to migrate the data to Amazon FSx for Windows File Server.
Question
Key Takeaways
The question tests the ability to match on-premises SMB file storage protocols with the correct AWS managed file service (FSx for Windows) while utilizing an automated transfer tool (DataSync) to minimize manual effort.
This page explains how to migrate large volumes of unstructured SMB data to AWS using AWS DataSync and Amazon FSx for Windows File Server, ensuring protocol compatibility and minimal operational overhead.
Common mistake: Candidates often choose Amazon S3 because it is a popular storage service, but S3 does not natively support the SMB protocol required by existing applications without additional gateways or proxy solutions, which increases complexity.
Expert Analysis
Why the Answer Is Correct
The correct answer is C because the scenario specifies that the company uses SMB-based storage and does not want to change its applications. Amazon FSx for Windows File Server provides fully managed Microsoft Windows-native file systems that are accessible via SMB. AWS DataSync is the ideal tool for this migration as it automates the transfer of file data and metadata (permissions, timestamps) from on-premises sources to FSx for Windows, significantly reducing operational overhead compared to manual copying or custom scripts.
Why the Other Options Are Wrong
Option A is incorrect because Amazon S3 is an object storage service that does not support the SMB protocol; accessing it would require application changes or a gateway layer, violating the requirement to avoid changing applications. Option B is incorrect because Amazon FSx for Lustre is designed for high-performance Linux workloads and uses POSIX-compliant interfaces, not SMB. Option D involves AWS Storage Gateway Volume Gateway, which presents iSCSI volumes rather than native SMB file shares in the same seamless way FSx does, and typically requires more configuration and management overhead for large-scale file migrations compared to DataSync's automated approach.
Community Comment Notes
The community overwhelmingly supports option C, citing the necessity of SMB compatibility for existing applications. As one user noted, "Option C since its SMB (windows), and low operational effort so DataSync over Direct Connect," highlighting the balance between protocol needs and ease of use. Another commenter emphasized that "Only FSx for NetApp ONTAP and FSx for Windows File Server support SMB Protocol," effectively ruling out other file services like Lustre or S3 for this specific constraint.
Official Reference
- https://docs.aws.amazon.com/datasync/latest/userguide/create-fsx-location.html
- https://aws.amazon.com/fsx/windows/
These links open the official vendor documentation in a new tab.
Exam Strategy
Always identify the access protocol specified in the question (e.g., SMB, NFS, iSCSI) first. Then, select the AWS storage service that natively supports that protocol. Finally, choose the migration tool that minimizes operational overhead (usually DataSync for files).
Frequently Asked Questions
Why can't I use Amazon S3 for SMB data?
Is AWS DataSync faster than Direct Connect alone?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 7 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 7
-
Sivaeas 👍 6 Answered CAWS DataSync is a data transfer service that simplifies, automates, and accelerates moving and replicating data between on-premises storage systems and AWS storage services over the internet or AWS Direct Connect. DataSync can transfer your file data, and also file system metadata such as ownership, time stamps, and access permissions. In DataSync, a location for Amazon FSx for Windows is an endpoint for an FSx for Windows File Server. You can transfer files between a location for Amazon FSx for Windows and a location for other file systems. For information, see Working with Locations in the AWS DataSync User Guide. DataSync accesses your FSx for Windows File Server using the Server Message Block (SMB) protocol.
-
ogerber 👍 4 Answered COption C since its SMB (windows) , and low operational effort so DataSync over Direct Connect
-
Naveena_Devanga 👍 3Correct Anwer is C As most of the data is unstructured, and the company’s file storage consists of SMB-based storage types from multiple vendors which is commonly a Windows-Linux file-sharing type so FSx for Windows File Server file systems completely meets the solution.
-
osmk 👍 3 Answered Chttps://docs.aws.amazon.com/datasync/latest/userguide/create-fsx-location.html
-
Linuslin 👍 2 Answered CAWS Storage Gateway provides a standard set of storage protocols such as iSCSI, SMB, and NFS, which allow you to use AWS storage without rewriting your existing applications.--->A is not complete describe, so A is out. https://aws.amazon.com/storagegateway/faqs/?nc=sn&loc=6 Only FSx for NetApp ONTAP and FSx for Windows File Server support SMB Protocol. --->B is out. https://aws.amazon.com/tw/fsx/when-to-choose-fsx/ AWS Direct Connect is more expensive than AWS DataSync.--->D is out C is the correct answer.
Show 2 more comments
-
Andy_09 👍 6Option C
-
Scheldon 👍 2 Answered CAnswerC
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →