Extending SMB Storage with S3 File Gateway Lifecycle
A company is running an SMB file server in its data center. The file server stores large files that are accessed frequently for the first few days after the files are created. After 7 days the files are rarely accessed. The total data size is increasing and is close to the company's total storage capacity. A solutions architect must increase the company's available storage space without losing low-latency access to the most recently accessed files. The solutions architect must also provide file lifecycle management to avoid future storage issues. Which solution will meet these requirements?
Community Insight
The question tests whether you can combine on-premises file access, gateway caching for low latency, and S3 lifecycle rules; the trap is picking a solution that adds space but provides no lifecycle management (FSx) or one that destroys low latency for recent files.
This SAA-C03 scenario asks how to extend an on-premises SMB file server's capacity while keeping recently accessed files fast and adding lifecycle management. An Amazon S3 File Gateway plus an S3 Lifecycle policy transitioning data older than 7 days to S3 Glacier Deep Archive (option B) satisfies every stated requirement.
Option C (Amazon FSx for Windows File Server) is the most tempting wrong answer because it clearly extends SMB storage with low latency, but it offers no built-in lifecycle management, which the question explicitly requires; option A merely copies old data without freeing primary storage, and option D's per-user utility is impractical and uses the wrong retrieval class.
Community Discussion (142 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon S3 File Gateway presents an SMB/NFS interface on-premises while storing objects in Amazon S3, so the company gains effectively unlimited cloud-backed capacity without changing user workflows. The gateway's local disk cache keeps recently and frequently accessed files available at low latency, which directly satisfies the requirement for low-latency access to the most recently accessed files. Adding an S3 Lifecycle policy that transitions objects older than 7 days to S3 Glacier Deep Archive supplies the requested file lifecycle management and prevents future capacity exhaustion at the lowest cost. Because files are rarely touched after 7 days, the long retrieval time of Deep Archive does not violate the stated requirements. This combination addresses all three constraints: added space, retained low latency for new files, and automated lifecycle control.Why the Other Options Are Wrong
Option A, AWS DataSync copying data older than 7 days, only moves cold copies to AWS while the on-premises file server remains full, so available local capacity is not actually increased and no lifecycle policy is created. Option C, Amazon FSx for Windows File Server, extends storage and preserves SMB low latency, but it provides no lifecycle management, so it fails the explicit requirement to avoid future storage issues. Option D requires installing a utility on every user's workstation—impractical at scale and a poor replacement for SMB access—and S3 Glacier Flexible Retrieval is designed for data that may be needed within hours, making it a costlier mismatch for rarely accessed archives compared with Deep Archive. As Buruguduystunstugudunstu noted about option C, it "would provide additional storage space but would not include file lifecycle management."Community Comment Notes
Several commenters converge on B, with javitech83 explaining that "low latency is only needed for newer files" and that the File Gateway "provides low latency access by caching frequently accessed files locally." Ander927 likewise pointed out that the file gateway "comes with a cache volume on-premise wich ensures the low latency for the most recently accessed files," and JayBee65 clarified that files in the last 7 days are never transitioned, so low latency is preserved. Sinaneos argued the answer "directly points towards file gateway with lifecycles," dismissing D because installing a utility is vague, a view echoed by MoMoCh4n: "D is Dead wrong." nathanss and shirleyson123 expressed frustration about the source key itself rather than the question, which does not change the technical verdict that B is correct.Official Reference
Exam Strategy
When a question pairs 'extend storage' with 'lifecycle management,' look for an option that names both a storage-extending service and an explicit lifecycle/transition policy; FSx-style answers usually fail this test. Also confirm where low latency is required—only recently accessed files need it here—so a cached gateway plus an archival tier is acceptable.
Frequently Asked Questions
Why is Amazon FSx for Windows File Server wrong if it extends SMB storage?
FSx adds capacity and low-latency SMB access but has no built-in lifecycle management, so it fails the requirement to prevent future storage issues.
Why does S3 Glacier Deep Archive work for files older than 7 days?
Those files are rarely accessed, so the long retrieval time of Deep Archive is acceptable and it minimizes archival storage cost.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →
minimum storage durationmetric. As I understand it now, you are able to delete/move objects before minimum storage duration is exceeded, but you pay for the entire period nonetheless. So it's doable, but not cost effective. Anyway, it does not apply here since S3 Standard storage class does not have a minimum storage duration constraint. So, I would go with B. Both B and D achieve the same thing, but B is way simpler to setup and maintain