AWS Storage Gateway for On-Premises SMB File Copy

SAA-C03 By islever Editorial Last updated

Determine appropriate data security controls.

Short answer

D AWS Storage Gateway allows on-premises applications to store files using standard SMB interfaces while automatically uploading data to Amazon S3 in the background.

Question

A company has an on-premises business application that generates hundreds of files each day. These files are stored on an SMB file share and require a low-latency connection to the application servers. A new company policy states all application-generated files must be copied to AWS. There is already a VPN connection to AWS. The application development team does not have time to make the necessary code modifications to move the application to AWS. Which service should a solutions architect recommend to allow the application to copy files to AWS?
  1. Amazon Elastic File System (Amazon EFS)
  2. Amazon FSx for Windows File Server
  3. AWS Snowball
  4. AWS Storage Gateway Correct Answer

Key Takeaways

The question tests the ability to select a hybrid storage service that bridges on-premises SMB shares to AWS cloud storage while maintaining low latency and requiring zero application modifications.

AWS Storage Gateway provides a seamless hybrid cloud storage solution that allows on-premises applications to store files in AWS via standard protocols like SMB without code changes. This page explains why Storage Gateway is the correct choice over Amazon FSx for Windows File Server.

Common mistake: Candidates often choose Amazon FSx for Windows File Server because it supports SMB, but they overlook that FSx is primarily designed for native cloud workloads rather than extending local file servers to the cloud with automatic background copying.

Expert Analysis

Why the Answer Is Correct

AWS Storage Gateway, specifically in its File Gateway configuration, is designed exactly for this scenario. It presents an SMB interface to on-premises clients, allowing them to write files as if to a local drive, while automatically and asynchronously uploading those files to Amazon S3 in the background. This meets the requirement to copy files to AWS without modifying the existing application code.

Why the Other Options Are Wrong

Amazon FSx for Windows File Server (Option B) is a managed Microsoft Windows file system, but it is optimized for running within AWS or connecting via Direct Connect/VPN for cloud-native workloads. While it supports SMB, it does not provide the same "hybrid" caching and automatic background upload-to-S3 mechanism as Storage Gateway for extending an existing on-premises file server. Amazon EFS (Option A) uses the NFS protocol, which is incompatible with SMB clients. AWS Snowball (Option C) is a physical data transport service used for large-scale offline data migration, not for continuous, low-latency file copying from an active application.

Community Comment Notes

Community consensus strongly favors Storage Gateway. As FlyingHawk noted, only B and D support SMB, but Storage Gateway handles the automatic copying requirement. Users like jcck202020 highlighted that Storage Gateway offers seamless integration between on-premises environments and AWS, fitting the need for copying rather than moving the entire filesystem infrastructure.

Official Reference

https://docs.aws.amazon.com/storagegateway/latest/userguide/StorageGatewayConcepts.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

When you see 'on-premises application', 'SMB/NFS', 'no code changes', and 'copy to AWS', think immediately of AWS Storage Gateway. Differentiate between FSx (cloud-native file server) and Storage Gateway (hybrid bridge to object storage).

Frequently Asked Questions

Why can't I use Amazon FSx for Windows File Server?

FSx is designed for cloud workloads. Storage Gateway is specifically built as a hybrid appliance to extend on-premises file servers to AWS object storage seamlessly.

Does Storage Gateway require changing the application code?

No. The application continues to interact with the local gateway instance via standard SMB protocols, unaware that the backend storage is in AWS S3.

More SAA-C03 FAQ →

Community Votes

D
76%
B
24%

76% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 10 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 10

  1. jcck202020 👍 3
    AWS Storage Gateway provides a set of hybrid cloud storage services that offer on-premises access to virtually unlimited cloud storage. The File Gateway configuration of AWS Storage Gateway supports the SMB protocol (and NFS), enabling on-premises applications to seamlessly store and retrieve files in Amazon S3 using existing file system protocols. It fits perfectly for applications that need to continue operating without modification, while also adhering to the new policy of copying files to AWS. Given these descriptions, Option D (AWS Storage Gateway) is the recommended service. It allows for a smooth integration by maintaining the existing SMB file-sharing capabilities and connects seamlessly to AWS through the VPN, enabling daily file transfers without significant changes to application code or infrastructure.
  2. LeonSauveterre 👍 3 Answered D
    D is good to go. AWS Storage Gateway provides seamless integration between on-premises environments and AWS, and specifically, File Gateway can be used to expose an SMB interface that on-premises applications can use. For B: While FSx does support SMB, it's optimized for AWS cloud workloads, not necessarily for on-premises systems. If you want an on-premises system to directly interact with an SMB share in AWS, you would typically need a service that integrates with the on-premises network seamlessly.
  3. FlyingHawk 👍 3 Answered D
    Only B and D support smb share, so A and C are out, the requirement is to copy the files at smb shares to AWS automatically. Storage Gateway automatically copies files to AWS (e.g., Amazon S3) in the background, meeting the requirement to copy all application-generated files to AWS.
  4. ckhemani 👍 3 Answered D
    Amazon FSx for Windows File Server is not used of transfer data. if it was Amazon Fsx Gateway, then it would have been been correct. They are looking solution for copying not moving to which filesystem.
  5. EdricHoang 👍 3 Answered B
    Amazon FSx for Windows File Server also support SMB and hybrid solution. And, no modification is needed.
Show 5 more comments
  1. Scheldon 👍 3 Answered D
    AnswerD StorageGateway https://docs.aws.amazon.com/storagegateway/
  2. Nm55569 👍 3 Answered B
    Why not "Amazon FSx for Windows File Server"?
  3. Kaula 👍 3 Answered D
    https://docs.aws.amazon.com/storagegateway/
  4. Awsbeginner87 👍 2 Answered D
    AWS Storage Gateway service enables hybrid storage between on-premises environments and the AWS Cloud. It provides low-latency performance by caching frequently accessed data on premises, while storing data securely and durably in Amazon cloud storage services.
  5. dhewa 👍 2 Answered D
    B is incorrect in this case because the development team doesn’t have time to modify the application.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide