Extending SMB Storage with S3 File Gateway Lifecycle

SAA-C03 By islever Editorial Last updated

Design cost-optimized storage solutions. Determine high-performing and/or scalable storage solutions.

Short answer

B Create an Amazon S3 File Gateway for SMB access with local caching and an S3 Lifecycle policy moving files older than 7 days to S3 Glacier Deep Archive.

Question

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?
  1. Use AWS DataSync to copy data that is older than 7 days from the SMB file server to AWS.
  2. Create an Amazon S3 File Gateway to extend the company's storage space. Create an S3 Lifecycle policy to transition the data to S3 Glacier Deep Archive after 7 days. Correct Answer
  3. Create an Amazon FSx for Windows File Server file system to extend the company's storage space.
  4. Install a utility on each user's computer to access Amazon S3. Create an S3 Lifecycle policy to transition the data to S3 Glacier Flexible Retrieval after 7 days.

Key Takeaways

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.

Common mistake: 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.

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

https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-management.html

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

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.

More SAA-C03 FAQ →

Discussion 134 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 30 of 134

  1. Sinaneos 👍 56
    Answer directly points towards file gateway with lifecycles, D is wrong because utility function is vague and there is no need for flexible storage.
  2. javitech83 👍 41 Answered B
    B answwer is correct. low latency is only needed for newer files. Additionally, File GW provides low latency access by caching frequently accessed files locally so answer is B
  3. PhucVuu 👍 13 Answered B
    Keywords: - After 7 days the files are rarely accessed. -The total data size is increasing and is close to the company's total storage capacity. - Increase the company's available storage space without losing low-latency access to the most recently accessed files. -> (for rarely accessed files we can access it with high-latency) - Must also provide file lifecycle management to avoid future storage issues. A: Incorrect - Don't mention how to increase company's available storage space. B: Correct - extend storage space and fast access with S3 File Gateway (cache recent access file), reduce cost and storage by move to S3 Glacier Deep Archive after 7 days. C: Incorrect - Didn't handle file lifecycle management. D: Incorrect - Don't mention about increase the company's available storage space.
  4. nathanss 👍 13 Answered B
    B is the correct answer again here. Why dont the moderator give some reasoning for the community's Most Voted answer a proper review and correct themselves or provide better reasoning ? Whoever agrees please upvote this.Thanks
  5. shirleyson123 👍 8
    I AM QUITE SUSPICIOUS WHY a public community thread ARE FIELDING OUT WRONG ANSWERS!???
Show 25 more comments
  1. Ander927 👍 7
    file gateway comes with a cache volume on-premise wich ensures the low latency for the most recently accessed files
  2. Buruguduystunstugudunstuy 👍 6
    Option A, using AWS DataSync to copy data that is older than 7 days from the SMB file server to AWS, would not provide additional storage space for the company's data and would not allow for low-latency access to the most recently accessed files. Option C, creating an FSx for Windows File Server file system, would provide additional storage space but would not include file lifecycle management. Option D, installing a utility on each user's computer to access Amazon S3 and creating an S3 Lifecycle policy, would not provide additional storage space on the company's file server.
  3. Buruguduystunstugudunstuy 👍 6 Answered B
    Option B, creating an Amazon S3 File Gateway and an S3 Lifecycle policy to transition data to S3 Glacier Deep Archive, would meet the requirements specified in the prompt. The S3 File Gateway allows you to store and retrieve objects in Amazon S3 using standard file system protocols, such as SMB and NFS. This would provide additional storage space for the company's data and allow for low-latency access to the most recently accessed files, as the data would still be stored on the SMB file server.
  4. JayBee65 👍 6
    No, you misread the question, the requirement is "without losing low-latency access to the most recently accessed files". Since files accessed in the last 7 days will not be transitioned to Glacier Deep Archive, they will still be available "without losing low-latency access" if B is selected.
  5. MoMoCh4n 👍 6 Answered B
    D is Dead wrong "install a utility on each user's computer" doesn't seem logical...what if there are 99999999 users?
  6. Andreshere 👍 5
    A. DataSync is focused on transferring data when we need synchronization (for example, from an on-premises DB that updates daily to a DB in AWS). In this case, we don’t need to transfer data or synchronize data, we only need to increase the storage. So, this option is not correct. B. S3 File Gateway allows communication between a File System/Server and S3, and it supports SMB protocol. We can use S3 FGW to move files from the FS to the S3 bucket. Then, the question says that files older than seven days are rarely accessed, so we can transition to S3 Glacier for those files to archive, in a costly-efficient way. So, this option is correct. C. You have two different storages for saving the files, making the interoperability unnecessarily more complex (and you need constant data synchronization, regarding to option A). D. This is a mess. The solution is not scalable and It depends on the number of users, which is not a static number. Additionally, Flexible Retrieval is unnecessary.
  7. HayLLlHuK 👍 5
    The same question and answer explanation exists in a Udemy course. Correct answer is B. Amazon S3 File Gateway provides a seamless way to connect to the cloud to store application data files and backup images as durable objects in Amazon S3 cloud storage. Amazon S3 File Gateway offers SMB or NFS-based access to data in Amazon S3 with local caching. It can be used for on-premises data-intensive Amazon EC2-based applications that need file protocol access to S3 object storage. Lifecycle policies can then transition the data to S3 Glacier Deep Archive after 7 days. D is wrong because is involves too much extra configuration which is unnecessary.
  8. Udoyen 👍 5
    Yes it might be vague but how do we keep the low-latency access that only flexible can offer?
  9. pakut2 👍 4
    I was wrong. Turns out you are able to transition from standard to Glacier after just 7 days. I can't find it explicitly stated anywhere, but it works in the console. My confusion is from the minimum storage duration metric. 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
  10. Liam_W 👍 4 Answered D
    Initially when reading this question, i wanted to use S3 Inteligiant Tiering as the answer but it was not mention. I was then torn between B and D due to the life cycle policies that was required as stated by the question: I chose D because it covers the need to be accessed whenever, without reducing the latency. This answer is also the best choice as it would reduce any storage issues users could face.
  11. Nava702 👍 4
    It says low-latency is required for the most recently accessed files, not new ones. So if an older file is retrieved from deep archive, it should then readily be accessible, according to the question, which points toward Flexible retrieval. However the utility portion in the answer D is vague.
  12. topdog 👍 4
    D is definitely the correct answer for this question. Answer D is the only one that meet this requirement After 7 days the files are rarely accessed.
  13. hro 👍 4
    AWS would not have you install a utility do something a service can do. The answer is B.
  14. LuckyAro 👍 4
    I SUSPECT IT'S A LEGAL ISSUE, SOME SO OBVIOUSLY WRONG ! CONFUSES ONE.
  15. BoboChow 👍 4 Answered B
    Amazon S3 File Gateway supports either SMB or NFS protocol
  16. gx2222 👍 3 Answered B
    Explanation: Since the company needs to increase available storage space while maintaining low-latency access to recently accessed files and implement file lifecycle management to avoid future storage issues, the best solution is to use Amazon S3 with a File Gateway. Using an Amazon S3 File Gateway, the company can access its SMB file server through an S3 bucket. This provides low-latency access to recently accessed files by caching them on the gateway appliance. The solution also supports file lifecycle management by using S3 Lifecycle policies to transition files to lower cost storage classes after they haven't been accessed for a certain period of time. In this case, the company can create an S3 Lifecycle policy to transition files to S3 Glacier Deep Archive after 7 days of not being accessed. This would allow the company to store large amounts of data at a lower cost, while still having easy access to recently accessed files.
  17. McLobster 👍 3 Answered A
    according to documentation the minimum storage timeframe for an object inside S3 before being able to transition using lifecycle policy is 30 days , so those 7 days policies kinda seem wrong to me Transition actions – These actions define when objects transition to another storage class. For example, you might choose to transition objects to the S3 Standard-IA storage class 30 days after creating them, or archive objects to the S3 Glacier Flexible Retrieval storage class one year after creating them. For more information, see Using Amazon S3 storage classes. I was thinking of option A using DataSync as a scheduled task? am i wrong here?
  18. M0SHE 👍 3 Answered B
    ption B: Amazon S3 File Gateway provides a hybrid cloud storage solution, integrating on-premises environments with cloud storage. Files written to the file share are automatically saved as S3 objects. With S3 Lifecycle policies, you can transition objects between storage classes. Transitioning to Glacier Deep Archive is suitable for rarely accessed files. This solution addresses both the storage capacity and lifecycle management requirements.
  19. awsgeek75 👍 3 Answered B
    Problems: SMB + Out of space + require low latency access to recent file + 7 day old files can go in archive A: Can work but not a continuous process so storage problems not solved C: FSx needs to connect to something on other side to transfer data. This is not specified here D: There is not data on user computer. B File gateway is for extending on-prem to S3.
  20. BillyBlunts 👍 3
    Can anyone tell me what the test is going to use as the correct answer? I don't want to go into the test and just answer the ones that majority voted for but really they don't have it as the right answer. BTW the discussions are awesome and helps you learn a lot from other peoples intellect.
  21. mikey2000 👍 3 Answered D
    I think the answer is D because the question said without losing low-latency access.With glacier flexible retrieval, data can but access within 1-5 mins unlike glacier deep archival, it take 12 hours to access your data, 12 hours would defeat trying to get a low- latency access
  22. premnick 👍 3 Answered D
    The question says, after 7 days the file are "rarely accessed", which means there are still possibilities that these filed would be needed in short period of time. Glacier Flexible Retrieval would fit this requirement.
  23. AlaN652 👍 3
    The question says " without losing low-latency access to the most recently accessed files. " this can be achieved by cashing most frequently accessed files in the file GW.
  24. sanking 👍 3 Answered D
    Why B is not correct? Create an S3 Lifecycle policy to transition the data to S3 Glacier Deep Archive after 7 days. I think “ S3 Glacier Deep Archive” is not correct.
  25. Ptopics 👍 3
    Low latency access is for files less than 7 days old. File GW provides low latency access by caching frequently accessed files locally so answer is B.

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.

Scheduled scaling for a predictable morning EC2 traffic spike

S-grade

Improving RDS Performance with Provisioned IOPS SSD

S-grade

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

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