A company is decommissioning an on-premises Windows file server whose SMB shares hold several terabytes of files that depend on Windows ACLs. The data must land in an Amazon FSx for Windows File Server file system, the transfer must run as a managed scheduled task that verifies integrity, and the existing file permissions must be preserved on arrival. Which approach meets all of these needs with the least custom scripting?
- AMount the FSx file system from a jump host and run robocopy with the copy-all flag on a Windows scheduled task to mirror the shares and their security descriptors.
- BOrder an AWS Snowball Edge device, copy the shares onto it offline, and ship it so the data is imported directly into the FSx for Windows file system on return.
- CEnable cross-Region replication from the on-premises SMB shares to FSx so that changed files and their permissions are continuously copied during the migration.
- DDeploy an AWS DataSync agent on premises and configure a scheduled task from the SMB source to the FSx location that verifies data and preserves SMB metadata. Correct
Why A is wrong: Robocopy can copy ACLs but is a hand-rolled script on a self-managed host with no built-in transfer verification, which is exactly the manual approach the requirement rules out.
Why B is wrong: Snowball suits one-off offline bulk movement but does not import directly into FSx or provide the scheduled, repeatable, integrity-verified sync the cutover requires.
Why C is wrong: Cross-Region replication is an S3 feature between buckets and cannot connect an on-premises SMB share to FSx, so it cannot perform this Windows file migration at all.
Why D is correct: DataSync supports SMB sources and FSx for Windows destinations, runs scheduled incremental tasks, verifies transferred data and carries the SMB metadata including ACLs, meeting every part of the requirement.