AWS SMB Storage Solution Least Overhead

SAA-C03 By islever Editorial Last updated

Design secure access to AWS resources.

Short answer

D Create an Amazon FSx for Windows File Server file system to provide native SMB support with minimal management.

Question

A company is implementing a shared storage solution for a media application that the company hosts on AWS. The company needs the ability to use SMB clients to access stored data. Which solution will meet these requirements with the LEAST administrative overhead?
  1. Create an AWS Storage Gateway Volume Gateway. Create a file share that uses the required client protocol. Connect the application server to the file share.
  2. Create an AWS Storage Gateway Tape Gateway. Configure tapes to use Amazon S3. Connect the application server to the Tape Gateway.
  3. Create an Amazon EC2 Windows instance. Install and configure a Windows file share role on the instance. Connect the application server to the file share.
  4. Create an Amazon FSx for Windows File Server file system. Connect the application server to the file system. Correct Answer

Key Takeaways

The core concept is matching the SMB protocol requirement with a managed service that natively supports it, avoiding the management burden of EC2 instances.

This question identifies Amazon FSx for Windows File Server as the optimal solution for SMB-based shared storage on AWS, minimizing administrative overhead compared to self-managed alternatives.

Common mistake: Candidates often choose Option A (Storage Gateway Volume Gateway) or Option C (EC2), mistakenly believing Volume Gateway supports SMB directly or underestimating the maintenance costs of managing an EC2 instance.

Expert Analysis

Why the Answer Is Correct

Amazon FSx for Windows File Server is a fully managed file system built on Windows Server. It provides native support for the Server Message Block (SMB) protocol, allowing clients to mount the file share using standard Windows networking tools. Because it is a managed service, AWS handles patching, backups, and high availability, resulting in the least administrative overhead.

Why the Other Options Are Wrong

Option A (Storage Gateway Volume Gateway) converts data into iSCSI volumes for block-level access, not SMB file shares; only the File Gateway option supports SMB. Option B (Tape Gateway) is designed for virtual tape library (VTL) backup scenarios and does not provide file sharing capabilities. Option C (EC2 Windows Instance) requires manual installation of roles, configuration, security patching, and scaling, which contradicts the 'least administrative overhead' requirement.

Community Comment Notes

Community consensus strongly favors Option D, noting that SMB protocol directly maps to FSx for Windows. One commenter clarified that Volume Gateway uses iSCSI, not SMB, while another emphasized that EC2 involves significant manual maintenance like patches and backups, reinforcing why FSx is superior for low overhead.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When asked for 'least administrative overhead', prioritize Managed Services (like FSx, RDS, EKS) over Infrastructure-as-a-Service (like EC2). Always verify protocol compatibility: SMB maps to FSx for Windows or File Gateway; iSCSI maps to Volume Gateway.

Frequently Asked Questions

Does Storage Gateway Volume Gateway support SMB?

No. Volume Gateway provides iSCSI block storage. Only Storage Gateway File Gateway supports SMB/CIFS.

Why not use an EC2 Windows instance for file sharing?

While possible, EC2 requires manual OS patching, role installation, and HA configuration, creating higher administrative overhead than FSx.

More SAA-C03 FAQ →

Community Votes

D
100%

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

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

  1. Scheldon 👍 4 Answered D
    Answer D https://aws.amazon.com/fsx/windows/
  2. muhammadahmer36 👍 2 Answered D
    D. Create an Amazon FSx for Windows File Server file system. Connect the application server to the file system.
  3. LeonSauveterre 👍 1 Answered D
    FSx for Windows File Server for sure. About other options: A - Volume Gateway doesn't directly support SMB. SMB is more commonly supported in File Gateway or FSx for Windows. B - Tape Gateway is for backup, not for file sharing via SMB. C - This is actually a valid alternative if you're looking for more control, but it involves manual setup, maintenance, patches, backups and of course scaling, which increases administrative overhead in a big way.
  4. trinh_le 👍 3 Answered D
    SMB protocol -> FSx windows

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