A company needs to implement a managed file system to host Windows file shares for users on premises. Resources in the AWS Cloud also need access to the data on these file shares. A SysOps…

Question

Options

• ASet up an Amazon S3 File Gateway.
• BSet up an AWS Direct Connect connection.
• CUse AWS DataSync to automate data transfers between the existing file servers and AWS.
• DSet up an Amazon FSx File Gateway.

• A
  10% (4)
• B
  3% (1)
• C
  8% (3)
• D
  80% (32)

Explanation

Amazon FSx File Gateway is correct because it is specifically designed to provide on-premises access to fully managed Amazon FSx for Windows File Server shares using the SMB protocol, while simultaneously making those same shares available to AWS resources - all with low-latency local caching for on-premises users.

Option A (S3 File Gateway) is wrong because S3 File Gateway presents object storage (S3 buckets) via NFS/SMB, not a native Windows file share backed by a managed Windows file system. It lacks the Windows-native features (Active Directory integration, DFS namespaces, etc.) that the question implies.

Option B (Direct Connect) is wrong because it is a network connectivity solution, not a file system or storage gateway - it provides a dedicated private link to AWS but does nothing on its own to present or manage file shares.

Option C (DataSync) is wrong because DataSync is a one-time or scheduled data migration/replication service; it does not present a live, accessible file share to on-premises users with local caching.

Memory tip: Think "FSx File Gateway = Windows file shares, both sides of the fence." Whenever you see Windows file shares + on-premises access + AWS access + low latency, FSx File Gateway is the answer - it is the only AWS Storage Gateway type purpose-built for Windows (SMB/NTFS) workloads backed by Amazon FSx.

No community discussion yet for this question.