Which solutions will meet these requirements?
(Choose two.)
Deploy AWS DataSync agents on premises. Schedule DataSync tasks to transfer the data to the FSx for Windows File Server file system.
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.
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.
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.
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.
Explanations:
AWS DataSync supports preserving file permissions during migration, and the solution allows the transfer of data to the FSx for Windows File Server.
Copying data into S3 via the AWS CLI does not preserve file permissions. DataSync is required to maintain permissions during migration.
Importing data through physical devices (such as drives) does not preserve file permissions. AWS DataSync is needed to transfer data with permissions intact.
AWS Snowcone with DataSync supports migrating data to FSx for Windows File Server and preserves file permissions, fulfilling the requirement.
While Snowball Edge can be used for large data transfers, using the AWS CLI does not preserve file permissions. DataSync must be used instead.
I arrange that the answer is:
Deploy AWS DataSync agents on premises. Schedule DataSync tasks to transfer the data to the FSx for Windows File Server file system.