Answer: Deploy AWS DataSync agents on premises. Schedule DataSync tasks to transfer the data to the FSx for Windows File Server file system., Order an AWS Snowcone device. Connect the device to the on-premises network. Launch AWS DataSync agents on the device. Schedule DataSync tasks to transfer the data to the FSx for Windows File Server file system.

## Explanation **Correct Answers: A and D** **A. Deploy AWS DataSync agents on premises. Schedule DataSync tasks to transfer the data to the FSx for Windows File Server file system.** - **Correct**: AWS DataSync is specifically designed for migrating data while preserving metadata including file permissions, timestamps, and access control lists (ACLs). - DataSync agents can be deployed on-premises and directly transfer data to Amazon FSx for Windows File Server while maintaining Windows NTFS permissions. - This is the most straightforward and efficient solution for this scenario. **D. Order an AWS Snowcone device. Connect the device to the on-premises network. Launch AWS DataSync agents on the device. Schedule DataSync tasks to transfer the data to the FSx for Windows File Server file system.** - **Correct**: Snowcone can run AWS DataSync agents locally, allowing you to transfer data while preserving metadata. - Snowcone is a small, portable device that can be connected to the on-premises network and used as a data transfer appliance. - This is useful when network bandwidth is limited or when you need a physical transfer option. **Why other options are incorrect:** **B. Copy the shares on each file server into Amazon S3 buckets by using the AWS CLI. Schedule AWS DataSync tasks to transfer the data to the FSx for Windows File Server file system.** - **Incorrect**: Copying files to S3 using AWS CLI will not preserve Windows NTFS permissions. S3 is an object storage service that doesn't support Windows file system metadata. - Even if DataSync is used later, the permissions would already be lost during the initial S3 upload. **C. Remove the drives from each file server. Ship the drives to AWS for import into Amazon S3. Schedule AWS DataSync tasks to transfer the data to the FSx for Windows File Server file system.** - **Incorrect**: Similar to option B, importing data into S3 first will cause loss of Windows file permissions. - The AWS Snowball import service into S3 doesn't preserve Windows NTFS permissions. - This approach adds unnecessary complexity and cost. **E. Order an AWS Snowball Edge Storage Optimized device. Connect the device to the on-premises network. Copy data to the device by using the AWS CLI. Ship the device back to AWS for import into Amazon S3. Schedule AWS DataSync tasks to transfer the data to the FSx for Windows File Server file system.** - **Incorrect**: Using AWS CLI to copy data to Snowball Edge doesn't preserve Windows permissions. - The data would be imported into S3 first, losing metadata, before being transferred to FSx. - Snowball Edge supports running DataSync agents (like Snowcone), but this option specifically mentions using AWS CLI which doesn't preserve permissions. **Key Points:** - AWS DataSync is the recommended service for migrating data to Amazon FSx for Windows File Server while preserving Windows NTFS permissions. - DataSync can run on-premises agents or on AWS Snow Family devices (Snowcone, Snowball Edge) to facilitate data transfer. - Direct transfer to FSx (not through S3) is essential for preserving Windows file permissions. - The requirement to "preserve file permissions" eliminates any solution that involves S3 as an intermediate storage, as S3 doesn't support Windows file system metadata.