CLF-C02 Cloud Technology and Services Practice Question
A company runs a legacy on-premises file server that stores 10 TB of shared documents used by a team of 50 employees. The company wants to migrate this data to Amazon S3 to benefit from durable, scalable storage. However, the team requires low-latency access to frequently used files (less than 5 milliseconds latency) because the application reads and writes files multiple times per second. The company also wants to maintain a local cache of recently accessed files on premises to reduce latency and minimize egress costs. The entire solution should be managed through the AWS Management Console and support standard file-sharing protocols like SMB. Which AWS service should the company use to meet these requirements?
⚠ Common exam trap
Many candidates confuse AWS Storage Gateway File Gateway with Amazon FSx for Windows File Server, assuming both provide on-premises caching, but FSx is a cloud-only service without a local cache, making it unsuitable for sub-5 ms latency requirements from on-premises clients.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
AWS Storage Gateway File Gateway
AWS Storage Gateway File Gateway is the correct choice because it provides a hybrid cloud storage service that enables low-latency, on-premises access to frequently used files by maintaining a local cache of recently accessed data. It supports the SMB protocol for standard file sharing, integrates with Amazon S3 for durable, scalable storage, and can be managed through the AWS Management Console. The local cache reduces both latency (targeting sub-5 ms for cached data) and egress costs by serving reads from the on-premises cache instead of fetching from S3.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
AWS Storage Gateway File Gateway
Why this is correct
This service is designed exactly for this use case: it provides a local VM that caches frequently accessed files on premises, presents SMB/NFS shares to applications, and stores the primary data in Amazon S3. It offers low-latency access through the cache and is managed from the AWS Management Console.
- ✗
Amazon FSx for Windows File Server
Why it's wrong here
FSx for Windows File Server is a fully managed native Windows file server running in AWS. While it supports SMB protocol, it does not include an on-premises caching component. Access from on-premises requires a network connection (VPN or Direct Connect) with no local cache, which would introduce latency and recurring egress costs for every file operation.
When this WOULD be correct
A company needs a fully managed, native Windows file server in the cloud with support for SMB protocol, Active Directory integration, and low-latency access from AWS, but does not require an on-premises cache or hybrid deployment.
- ✗
AWS DataSync
Why it's wrong here
AWS DataSync is designed for large-scale data transfers from on-premises to AWS (or vice versa) over the internet or Direct Connect. It can copy the initial 10 TB to S3 efficiently, but it does not provide ongoing low-latency file access with local caching. After the transfer is complete, DataSync is not used for daily read/write operations.
When this WOULD be correct
A company needs to migrate 50 TB of data from an on-premises NFS server to Amazon EFS, and the migration must be automated, incremental, and track changes. AWS DataSync would be the correct choice for the one-time or recurring data transfer, not for ongoing file access.
- ✗
Amazon S3 with AWS Direct Connect
Why it's wrong here
While Direct Connect provides a dedicated, high-bandwidth network connection from on-premises to AWS, there is no local cache. Each file read/write would require a round trip over the Direct Connect link to S3, resulting in latencies that typically exceed 5 milliseconds for small I/O operations. Additionally, all data movements incur egress charges, and the solution does not provide a standard SMB file share interface.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.
✓AWS Storage Gateway File GatewayCorrect answer▾
Why this is correct
This service is designed exactly for this use case: it provides a local VM that caches frequently accessed files on premises, presents SMB/NFS shares to applications, and stores the primary data in Amazon S3. It offers low-latency access through the cache and is managed from the AWS Management Console.
✗Amazon FSx for Windows File ServerWrong answer — click to see why▾
Why this is wrong here
Amazon FSx for Windows File Server does not provide a local on-premises cache to reduce latency and egress costs; it is a fully managed Windows file server in the cloud, not a hybrid caching solution.
★ When this WOULD be the correct answer
A company needs a fully managed, native Windows file server in the cloud with support for SMB protocol, Active Directory integration, and low-latency access from AWS, but does not require an on-premises cache or hybrid deployment.
Why candidates choose this
Candidates may confuse FSx for Windows File Server's SMB support and low-latency access with the requirement for a local cache, overlooking that FSx does not offer a local caching tier on premises.
✗AWS DataSyncWrong answer — click to see why▾
Why this is wrong here
AWS DataSync is a data transfer service for moving large datasets to or from AWS, but it does not provide low-latency file access (sub-5ms) or a local cache for frequently accessed files. It is not designed for ongoing, low-latency file sharing via SMB.
★ When this WOULD be the correct answer
A company needs to migrate 50 TB of data from an on-premises NFS server to Amazon EFS, and the migration must be automated, incremental, and track changes. AWS DataSync would be the correct choice for the one-time or recurring data transfer, not for ongoing file access.
Why candidates choose this
Candidates may confuse DataSync as a solution for both migration and ongoing access, or think its caching capabilities (which it does not have) could meet the low-latency requirement.
Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This CLF-C02 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CLF-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CLF-C02 exam.