AZ-305 Practice Question 99: Storage Mover File Share Migration
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 10 · question 9 of 10
A manufacturer runs three on-premises Windows file servers totaling 60 TB of SMB shares that it wants to migrate to Azure file shares. The migration must minimize downtime with an initial bulk transfer followed by a delta sync of only the changes right before cutover, preserve file and folder metadata, and be managed centrally from Azure rather than by running ad hoc copy commands on each server. The company does not want to build or operate a continuous, ongoing file synchronization service afterward.
What should you include in the design?
Show answer and explanation
Answer:
Azure Storage Mover is a fully managed migration service, orchestrated centrally from Azure, that deploys an agent close to the source shares and performs an initial bulk transfer followed by optional delta syncs of only the changes, using the FileREST API so file and folder metadata is preserved with full fidelity. It is a one-directional migration tool, not a continuous synchronization service, which matches the requirement not to operate ongoing sync.
Option A is wrong because Azure File Sync is designed for continuous, ongoing synchronization between on-premises servers and Azure file shares with cloud tiering, which is the standing service the company explicitly does not want to build. Option B is wrong because Robocopy over a VPN is a manual, per-server process with no central orchestration or built-in delta sync design, and it does not preserve metadata as reliably as a native Azure Files API-based mover. Option D is wrong because scheduled AzCopy scripts are also a manual, per-server approach with no central management console and require custom scripting to achieve a bulk-then-delta migration pattern.
Reference: Use Azure Storage Mover to migrate to Azure file shares