A company stores data on-premises on a Windows file server and generates 5 GB of new data daily. Part of its Windows workload has migrated to AWS and that data must be available on a cloud file system. The company already has an AWS Direct Connect link between on-premises and AWS. Which migration approach should the company use?

The correct approach is to use AWS DataSync to schedule a daily task to replicate data from the on-premises Windows file server to Amazon FSx. DataSync is specifically designed for online data transfer between on-premises storage and AWS storage services, making it ideal for this scenario. It can efficiently handle the 5 GB of daily new data. Amazon FSx for Windows File Server provides fully managed, highly reliable, and scalable file storage that is natively compatible with Windows workloads, ensuring seamless integration with the migrated cloud applications. Using the file gateway option in AWS Storage Gateway would replace the existing Windows file server, which is not the primary goal; the goal is to replicate data to a cloud file system. AWS Data Pipeline is a data orchestration service, not a data transfer service like DataSync, and is not suitable for direct file replication. Replicating to Amazon EFS is incorrect because EFS is a Linux-native file system and is not compatible with Windows workloads without additional layers, whereas the company has a Windows file server and Windows workloads.