Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Data Box with Storage Mover Synchronization
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An enterprise plans to migrate hundreds of terabytes of on-premises file share data to Azure Storage. The organization has limited WAN bandwidth, and users must continue modifying files on-premises during the migration process.
The migration strategy must achieve the following:
- Move the bulk of existing data without overloading the limited network connection
- Synchronize incremental changes and modified metadata before the final cutover with minimal downtime
Which migration strategy should the enterprise implement?
Explanations
Use Azure Data Box for the initial bulk data transfer, followed by Azure Storage Mover for online delta catch-up
Use Azure Data Box for the initial bulk data transfer, followed by Azure Storage Mover for online delta catch-up
What the Solution Is
Azure Data Box is a physical appliance service provided by Microsoft designed to move massive volumes of data into Azure offline, bypassing bandwidth-constrained wide area networks. Azure Storage Mover is a fully managed cloud migration service that automates and orchestrates the migration of unstructured files and folders from on-premises storage to Azure Storage.
How It Meets the Requirements
- Conserving Network Bandwidth: Azure Data Box allows the enterprise to copy hundreds of terabytes locally to an encrypted physical device and ship it to an Azure datacenter, eliminating the need to transfer large baselines over a slow internet connection.
- Synchronizing Active Delta Changes: While the physical device is in transit, users continue to modify local files. Azure Storage Mover performs an online catch-up phase, scanning the source storage, detecting differences, and transferring only the delta (new files, modified files, and permission/ACL updates) over the network before the final workload cutover.
Key Advantages and Capabilities
- Reduced Network Saturation: Offloads large bulk payloads to physical media while reserving WAN capacity for daily business operations.
- Minimal Cutover Downtime: The catch-up phase transfers only small incremental modifications, making the final transition window predictable and brief.
- High File Fidelity: Preserves file metadata, timestamps, and access control lists (ACLs) across shares.
- Centralized Orchestration: Enables tracking migration progress, managing agent endpoints, and monitoring logs from the Azure portal.
Why This Is Optimal
Combining an offline physical transport mechanism (Azure Data Box) with an intelligent cloud-managed synchronization tool (Azure Storage Mover) provides the ideal hybrid migration workflow for large datasets where WAN bandwidth is constrained and data remains continuously active.
Use Azure Data Box Heavy for both the initial baseline transfer and continuous delta replication
Use Azure Data Box Heavy for both the initial baseline transfer and continuous delta replication
What the Option Is
Azure Data Box Heavy is a ruggedized, high-capacity physical appliance capable of storing several hundred terabytes of raw data. It is ordered through the Azure portal, delivered to a local datacenter, loaded with data over a local network, and shipped back to Microsoft for offline ingestion.
Why It Doesn't Meet the Requirement
- Inability to Perform Live Sync: Azure Data Box Heavy is purely an offline, point-in-time data transport solution. It cannot maintain an active synchronization link with on-premises storage once it is disconnected and shipped.
- Accumulated Drift: Any modifications, newly created files, or metadata updates generated during the shipping and ingestion window cannot be captured by the physical device alone without an accompanying online synchronization tool.
Key Characteristics and Limitations
- Massive Ingestion Capacity: Designed specifically for multi-hundred terabyte datasets where online WAN transfer is unfeasible.
- Point-in-Time Snapshot: Captures only the data copied prior to device disconnection.
- Shipping Turnaround: Entails physical transit times that make real-time delta replication impossible.
This Answer Would Be Correct If
The file shares were completely static or read-only during the migration period, meaning no user modifications or delta updates would occur during the shipping process.
Use Azure File Sync exclusively over the public Internet to execute both the initial baseline copy and ongoing file tiering
Use Azure File Sync exclusively over the public Internet to execute both the initial baseline copy and ongoing file tiering
What the Option Is
Azure File Sync is a service that allows organizations to centralize file shares in Azure Files while maintaining the flexibility, performance, and compatibility of an on-premises Windows file server with local cloud tiering and caching.
Why It Doesn't Meet the Requirement
- Network Bottleneck: Relying exclusively on Azure File Sync over the public internet to migrate hundreds of terabytes of initial baseline data would severely saturate the enterprise's limited WAN bandwidth and could take months to complete.
- Missing Bulk Offline Step: Without an initial offline seeding mechanism like Azure Data Box, baseline sync over low-bandwidth links is impractical for multi-hundred terabyte environments.
Key Characteristics and Limitations
- Bi-directional Caching: Keeps frequently accessed files locally on Windows Server while tiering older files to Azure Files.
- Network Dependent: Relies entirely on available WAN bandwidth for baseline initialization unless seeded offline first.
- Target Constraints: Requires a Windows Server host to run the Azure File Sync agent.
This Answer Would Be Correct If
The dataset were relatively small, high-speed network bandwidth were readily available, and the primary goal was to establish continuous bi-directional caching between on-premises Windows Servers and Azure Files.
Use an Azure Migrate appliance for the initial data transfer, followed by Azure Data Box for ongoing delta synchronization
Use an Azure Migrate appliance for the initial data transfer, followed by Azure Data Box for ongoing delta synchronization
What the Option Is
Azure Migrate provides a centralized hub to discover, assess, and migrate on-premises servers, infrastructure, applications, and databases to Azure. It utilizes an on-premises virtual appliance to collect performance metrics and orchestrate workload migrations.
Why It Doesn't Meet the Requirement
- Improper Tool Pairing: Azure Migrate primarily focuses on server discovery, VM replication, and workload assessment rather than serving as an offline data transport mechanism for terabytes of raw file shares over slow links.
- Misunderstanding of Data Box Capabilities: Azure Data Box is a physical device shipped via courier for bulk transfers. It cannot be used for continuous or automated delta synchronization because physical shipping incurs days of transit latency and cannot perform live catch-up operations.
Key Characteristics and Limitations
- Azure Migrate Appliance: Deployed on Hyper-V or VMware environments to run discovery scripts and assess migration readiness.
- Offline Latency: Physical media cannot accommodate rapid, incremental file change replication.
- Network Dependency: Live migration through Azure Migrate relies heavily on network connectivity, which conflicts with the constraint of limited WAN bandwidth.
This Answer Would Be Correct If
The organization needed to discover on-premises virtual machines, evaluate their readiness for Azure IaaS, and replicate complete server operating systems over a dedicated network connection.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Data Box Heavy vs Data Box
Describe migration options, including Azure Migrate and Azure Data Box
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Migrate
Describe migration options, including Azure Migrate and Azure Data Box
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Data Box Disk BitLocker Encryption
Describe migration options, including Azure Migrate and Azure Data Box
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Data Box Offline Data Transfer
Describe migration options, including Azure Migrate and Azure Data Box
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Infrastructure as a Service
Describe infrastructure as a service (IaaS)
IntermediateAZ-800 Administering Windows Server Hybrid Core Infrastructure Exam
Azure File Sync Event Logs and Azure Monitor
Configure and manage Azure File Sync
Last updated Validated