Most Cost-Effective Low-Latency On-Premises Access to Amazon S3?
Short answer
B Configure an Amazon S3 File Gateway to provide low-latency, cached file access to S3 data for the on-premises rendering application.
Question
Key Takeaways
This question tests which hybrid storage service gives on-premises applications low-latency file access to S3; the trap is choosing Mountpoint for Amazon S3, which targets Linux clients running inside AWS and does not cache data on premises.
An on-premises media rendering application needs low-latency access to data that now lives in Amazon S3, at the lowest possible cost. Amazon S3 File Gateway (B) satisfies this by caching hot data locally while keeping the full dataset durably stored in S3.
Common mistake: Candidates often pick Mountpoint for Amazon S3 (A) because it reads S3 directly with no data copy, but Mountpoint is not an on-premises gateway and provides no local cache, so it cannot deliver the required low-latency access.
Expert Analysis
Why the Answer Is Correct
Amazon S3 File Gateway presents S3 objects to on-premises servers as files over NFS or SMB and keeps a local cache of the most frequently accessed data, so the rendering application gets the same low-latency reads it had with local storage. Because the authoritative copy of every object stays in Amazon S3, you keep S3's low per-GB storage pricing instead of paying for a second copy on faster, more expensive storage. Cache sizing lets you hold only the hot rendering assets on the gateway while the full library remains in S3, which is exactly what the "maintain the desired application performance" plus "MOST cost-effective" wording requires. No application rewrite is needed either, since the gateway exposes a standard file interface.
Why the Other Options Are Wrong
Option A, Mountpoint for Amazon S3, is a Linux FUSE client intended for compute running inside AWS such as EC2, containers, and EKS; it has no on-premises cache, so reads from a rendering farm would incur S3 request latency on every access. Option C duplicates the entire dataset into Amazon FSx for Windows File Server and adds an FSx File Gateway on top, which is far more expensive than S3 and is unnecessary when a file interface with caching is all that is required. Option D builds a self-managed on-premises file server that calls the S3 API, which still requires local storage capacity, patching, and application changes without providing a native cached file presentation, so it is neither low-latency nor cost-effective. Only S3 File Gateway meets the latency requirement while leaving the data in the cheapest durable storage tier.
Community Comment Notes
LeonSauveterre captured the key distinction by noting that "Mountpoint is not designed for on-premises environments or low-latency access" and that the File Gateway reduces latency through local caching. Bwhizzy made the same point, explaining that the gateway "caches frequently accessed data locally," which is what preserves rendering throughput. Americanman reinforced this by quoting AWS's own positioning that existing file-based applications can use Amazon S3 "without modification." The unanimous support for B in the votes matches how AWS describes S3 File Gateway, and none of the comments raise a scenario in which Mountpoint or FSx would be cheaper here.
Official Reference
- https://aws.amazon.com/storagegateway/file/s3/
- https://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html
These links open the official vendor documentation in a new tab.
Exam Strategy
When a stem pairs an on-premises application with data already in Amazon S3 and asks for low latency at the lowest cost, think hybrid file gateway with local caching rather than a FUSE client or a copy into FSx. Eliminate any option that duplicates the dataset into more expensive storage, because the cost keyword in the stem usually decides the answer.
Frequently Asked Questions
Why is Mountpoint for Amazon S3 not suitable for the on-premises rendering application?
Does Amazon S3 File Gateway keep the data in Amazon S3 rather than copying it?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 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 3
-
LeonSauveterre 👍 4 Answered BA - Mountpoint is not designed for on-premises environments or low-latency access; it works well for cloud-based applications. B - Amazon S3 File Gateway provides low-latency, on-premises access to data stored in Amazon S3 through a file-based interface. It caches frequently accessed data locally to reduce latency. C - Copying data to FSx increases costs, as FSx storage is more expensive than S3. Let alone unnecessary complexity. D - Direct interaction with S3 introduces higher latency for on-premises applications and lacks local caching.
-
Bwhizzy 👍 3 Answered BB. Configure an Amazon S3 File Gateway to provide storage for the on-premises application. Explanation: Amazon S3 File Gateway provides a way for on-premises applications to access objects stored in Amazon S3 as files. It caches frequently accessed data locally, which ensures low-latency access to the data. This is crucial for maintaining the performance of the rendering application. By keeping the data in Amazon S3, the company benefits from lower storage costs compared to using other storage services like Amazon FSx, while still providing the necessary performance for the on-premises application through the local caching capabilities of the File Gateway. The File Gateway seamlessly integrates with Amazon S3, allowing the application to access data using standard file protocols like NFS or SMB, which simplifies the setup.
-
Americanman 👍 2Amazon S3 File Gateway enables your existing file-based applications, devices, and workflows to use Amazon S3, without modification. Amazon S3 File Gateway securely and durably stores both file contents and metadata as objects, while providing your on-premises applications low-latency access to cached data.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →