Answer-first summary for fast verification
Answer: Deploy and configure Amazon FSx for Windows File Server on AWS. Deploy and configure an Amazon FSx File Gateway on premises. Move the on-premises file data to the FSx File Gateway. Configure the cloud workloads to use FSx for Windows File Server on AWS. Configure the on-premises workloads to use the FSx File Gateway.
## Explanation **Correct Answer: D** This solution best meets all the requirements: ### Key Requirements Analysis: 1. **5+ TB of Windows file data** - Requires Windows-compatible file storage 2. **Hybrid access** - Need access from both AWS and on-premises during migration 3. **Minimum latency** - Local caching for on-premises access 4. **Minimal operational overhead** - Managed services preferred 5. **No significant changes to existing file access patterns** - Must maintain SMB protocol compatibility 6. **AWS Site-to-Site VPN connectivity** - Already established network connection ### Why Option D is Correct: 1. **Amazon FSx for Windows File Server** provides fully managed Windows-native file shares with SMB protocol support, perfect for Windows workloads migrating to AWS. 2. **Amazon FSx File Gateway** deployed on-premises: - Caches frequently accessed files locally for low-latency access - Maintains SMB protocol compatibility (no changes to file access patterns) - Automatically syncs with FSx for Windows File Server in AWS - Provides seamless hybrid access during migration 3. **Hybrid Architecture**: - On-premises workloads use FSx File Gateway (local cache) - AWS workloads use FSx for Windows File Server directly - Data is synchronized between both locations ### Why Other Options Are Incorrect: **A**: Only addresses AWS workloads, doesn't provide low-latency on-premises access during migration. **B & C**: S3 File Gateway converts SMB to S3 object storage, which would require significant changes to file access patterns and isn't Windows-native. S3 isn't suitable for Windows file server workloads that need SMB protocol support. ### Additional Benefits: - **Managed Service**: Both FSx and FSx File Gateway are managed services, minimizing operational overhead - **Seamless Migration**: Allows gradual migration of workloads while maintaining access - **Data Consistency**: Automatic synchronization ensures data consistency across locations - **Performance**: Local caching provides low-latency access for on-premises users This solution provides a true hybrid file storage solution that maintains Windows compatibility while enabling a smooth migration to AWS.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company has more than 5 TB of file data on Windows file servers that run on premises. Users and applications interact with the data each day. The company is moving its Windows workloads to AWS. As the company continues this process, the company requires access to AWS and on-premises file storage with minimum latency. The company needs a solution that minimizes operational overhead and requires no significant changes to the existing file access patterns. The company uses an AWS Site-to-Site VPN connection for connectivity to AWS.
What should a solutions architect do to meet these requirements?
A
Deploy and configure Amazon FSx for Windows File Server on AWS. Move the on-premises file data to FSx for Windows File Server. Reconfigure the workloads to use FSx for Windows File Server on AWS.
B
Deploy and configure an Amazon S3 File Gateway on premises. Move the on-premises file data to the S3 File Gateway. Reconfigure the on-premises workloads and the cloud workloads to use the S3 File Gateway.
C
Deploy and configure an Amazon S3 File Gateway on premises. Move the on-premises file data to Amazon S3. Reconfigure the workloads to use either Amazon S3 directly or the S3 File Gateway, depending on each workload’s location.
D
Deploy and configure Amazon FSx for Windows File Server on AWS. Deploy and configure an Amazon FSx File Gateway on premises. Move the on-premises file data to the FSx File Gateway. Configure the cloud workloads to use FSx for Windows File Server on AWS. Configure the on-premises workloads to use the FSx File Gateway.