You have an on-premises server that runs Windows Server and contains a folder named Folder1. Folder1 contains 50 GB of files. You have an Azure subscription that contains an Azure Files share named…

Question

Explanation

This question tests your knowledge of the correct Azure tool to perform a one-time migration of on-premises file data to an Azure Files share. The key is distinguishing between tools designed for migration versus tools designed for ongoing hybrid sync.

Approach. The correct approach is to use AzCopy on the on-premises Windows Server to copy Folder1 directly to the Azure Files share. AzCopy is a command-line utility optimized for high-performance data transfer to and from Azure Storage, including Azure Files. You would generate a SAS (Shared Access Signature) token for the Azure Files share, then run a command such as: azcopy copy 'C:\Folder1' 'https://<storageaccount>.file.core.windows.net/share<SAS>' --recursive. This handles 50 GB efficiently in a single operation without requiring ongoing infrastructure. Azure File Sync would be incorrect here because it is designed for continuous hybrid sync (keeping on-premises and cloud in sync long-term), not a one-time migration, and requires deploying a Storage Sync Service and server endpoint - unnecessary overhead for a simple lift-and-shift.

Concept tested. Selecting the appropriate Azure data transfer tool (AzCopy vs. Azure File Sync vs. Storage Explorer) for a one-time on-premises-to-Azure Files migration scenario, and understanding when each tool is appropriate based on the use case (migration vs. hybrid sync vs. interactive browsing).

Reference. https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files

No community discussion yet for this question.