AZ-305 Design data storage solutions Practice Question
Which THREE of the following are valid methods to securely transfer data to Azure Blob Storage? (Select three.)
⚠ Common exam trap
It's easy for candidates to confuse Azure File Sync with a general-purpose data transfer tool, but it is strictly for file shares (SMB) and cannot target Blob Storage, while Azure Migrate is mistaken for a data transfer service when it is actually a migration orchestration tool for servers and applications.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Data Box
Azure Data Box is a physical data transfer solution that allows you to securely transfer large volumes of data to Azure Blob Storage when network transfer is impractical. It uses AES-256 encryption for data at rest and TLS for data in transit, and after the device is shipped back, data is automatically uploaded to your designated storage account.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Azure Data Box
Why this is correct
Azure Data Box is a physical, ruggedized storage appliance supplied by Microsoft to accelerate offline transfers of large volumes of data to Azure Blob Storage. You order the device through the portal, copy data to its local SMB/NFS shares, ship it back, and Microsoft uploads the contents to blob storage. The device encrypts data at rest with BitLocker and is irreversibly erased after upload, making it ideal when network transfer would take days or weeks.
- ✗
Azure File Sync
Why it's wrong here
Azure File Sync is a service that synchronizes files between an on-premises Windows Server file server and Azure Files, the managed SMB file share service, not Azure Blob Storage. It is not a method for uploading arbitrary datasets into blob containers; instead, it enables cloud tiering and centralized file management for file shares. Because its destination is Azure Files rather than blob storage, it cannot be used for the data transfer scenario implied by this question.
- ✓
AzCopy
Why this is correct
AzCopy is a standalone command-line utility that provides high-performance, scriptable copying of data to and from Azure Blob Storage using a network connection. It supports resumable transfers, incremental synchronization, wildcard patterns, and authentication via SAS tokens or Microsoft Entra ID. AzCopy is the appropriate online tool when the data size and available bandwidth permit transfer over internet or ExpressRoute, and it is often used for smaller or incremental uploads.
- ✗
Azure Migrate
Why it's wrong here
Azure Migrate is a discovery, assessment, and migration hub for moving on-premises workloads—such as VMware VMs, Hyper-V VMs, physical servers, and SQL Server databases—to Azure. It relies on the Azure Migrate appliance and specialized migration tools to orchestrate compute and database migrations, not to copy raw file data into blob storage. Therefore, it is not a valid method for a blob storage data transfer, which is a storage-level operation rather than a workload migration.
- ✓
Azure Import/Export service
Why this is correct
The Azure Import/Export service lets you transfer large amounts of data to or from Azure Blob Storage by shipping your own physical SATA hard drives or SSDs to an Azure datacenter. You prepare the drives with the WAImportExport tool, which encrypts them with BitLocker and generates manifest files, and then Microsoft imports the data into blob storage. Unlike Data Box, you supply the disks rather than using a Microsoft-provided appliance, so it is suitable when you need to leverage existing hardware for offline transfer, still targeting blob storage.
Quick reference
Symmetric Encryption Algorithm Comparison
| Algorithm | Key Size | Block Size | Status | Notes |
|---|---|---|---|---|
| AES-128 | 128-bit | 128-bit | Current standard | NIST approved; WPA3, TLS |
| AES-256 | 256-bit | 128-bit | Current standard | Preferred for sensitive / govt data |
| 3DES | 112-bit effective | 64-bit | Deprecated (2023) | Replaced by AES |
| DES | 56-bit | 64-bit | Broken | Cracked in < 24 h; never deploy |
| ChaCha20 | 256-bit | Stream cipher | Current | TLS 1.3, WireGuard |
Go deeper
Related to this question
About these practice questions
One of 795 original AZ-305 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-305 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-305 exam.