Azure Storage Services
AZ-900 AZ-900 · Describe Azure architecture and services
The storage account and its services
Almost all data in Azure lives in a storage account: a container that holds storage services and provides a unique namespace (a web address) for them. One account can hold several services, and the account's settings — region, performance tier, redundancy — apply to everything inside it. The exam names five storage services, and you need to match each to its data type:
| Service | Stores | Typical use |
|---|---|---|
| Azure Blob Storage | Unstructured object data — text, images, video, backups | Website media, data lakes, backups, archives |
| Azure Files | Files in SMB/NFS shares, accessible like a network drive | Shared file storage for applications and users, replacing on-premises file servers |
| Azure Queues | Messages between application components | Decoupling services: one part of an app drops a message, another picks it up later |
| Azure Tables | Structured NoSQL key-attribute data | Simple, large-scale structured data without a relational database |
| Azure Disks | Managed disks attached to virtual machines | OS and data disks for VMs (page blobs behind the scenes) |
Blob Storage is the biggest and most tested. Blobs come in three types — block blobs (the standard, for most files), append blobs (for adding data such as logs), and page blobs (the basis of VM disks) — but the exam focuses on what blobs are for (unstructured object data) rather than the sub-types. Azure Files is the other heavily tested service: it offers fully managed file shares using the standard SMB and NFS protocols, so applications can use it exactly like a traditional file server, including from on-premises through File Sync.
Storage tiers: paying for how often you read
Blob Storage charges differently depending on how often data is accessed, through access tiers. The Hot tier is for data accessed frequently — highest storage cost, lowest access cost. The Cool tier is for data accessed infrequently and stored for at least 30 days — lower storage cost, higher access cost. The Cold tier is for data rarely accessed and stored for at least 90 days — cheaper still to store. The Archive tier is for data almost never accessed and stored for at least 180 days — the cheapest storage, but retrieval takes hours and costs the most per retrieval. The rule is a trade-off: the less often you read it, the cheaper it is to store and the more expensive (and slower) it is to get back. Exam questions describe an access pattern — "backups kept for years and almost never read" — and expect the tier that matches: Archive.
Redundancy: how many copies, and where
Azure Storage always keeps multiple copies of your data; the redundancy option decides how many and where. The options, from least to most durable:
- LRS (locally redundant storage): 3 copies in one datacenter in the primary region. Protects against a disk or server failure. Cheapest.
- ZRS (zone-redundant storage): 3 copies across availability zones in the primary region. Protects against a datacenter failure.
- GRS (geo-redundant storage): 6 copies — 3 in the primary region and 3 in the paired secondary region. Protects against a regional failure.
- GZRS (geo-zone-redundant storage): 6 copies — 3 across zones in the primary region and 3 in the secondary region. Protects against both datacenter and regional failure. Most durable, most expensive.
RA-GRS and RA-GZRS add read access to the secondary region, so applications can read the replicated copy even when the primary region is unavailable. The exam tests the copy counts (3 vs 6) and the failure each option survives: LRS survives a drive failure, ZRS survives a datacenter failure, GRS/GZRS survive a region failure.
Storage account options
When creating a storage account you choose a performance tier (Standard, on hard-disk drives, or Premium, on solid-state drives, for low-latency workloads such as VM disks) and an account kind: Standard general-purpose v2 is the default and supports all services; Premium block blobs, Premium file shares, and Premium page blobs are specialised for performance-sensitive workloads. The exam only requires the broad picture: Standard vs Premium performance, and that the account kind determines which services and features are available.
Moving files and migrating data
Three tools move files into Azure Storage. AzCopy is a command-line tool for copying blobs and files to and from storage accounts — fast, scriptable, and the right answer for bulk transfers and automation. Azure Storage Explorer is a graphical application for managing storage accounts: upload, download, and browse blobs and files with a mouse. Azure File Sync synchronises an on-premises Windows file server with Azure Files, keeping the files in both places in sync and optionally tiering rarely used files to the cloud to free local disk (cloud tiering). The exam distinguishes them by interface and purpose: command-line bulk copy is AzCopy, a graphical browser is Storage Explorer, ongoing sync with an on-premises file server is File Sync.
For whole migrations, two services apply. Azure Migrate is the hub for assessing and migrating on-premises servers, applications, and data to Azure — it discovers what you have, estimates costs, and moves workloads. Azure Data Box is a physical device Microsoft ships to you: load up to around 100 TB of data onto it, ship it back, and Microsoft uploads it to Azure. Data Box is the answer when the data is too large to move over the network in reasonable time — the exam's classic scenario is terabytes of data on a slow connection, where shipping a device beats months of uploading. (Data Box Heavy handled around a petabyte for the largest transfers, but has since been retired.)
Worked example: a media company's storage
A media company stores raw video footage, finished videos served to viewers, and office documents. The design: finished videos in Blob Storage on the Hot tier (frequently read, low access cost); raw footage in Blob Storage on the Cool or Archive tier (rarely read, cheap to keep); office documents in Azure Files so staff can map it like a network drive; and the whole account on GRS so a regional failure does not lose the archive. When the company first moved its 80 TB archive from an on-premises server over a slow link, it used a Data Box rather than uploading for weeks. Four services, two tiers, one redundancy choice — each matched to how the data is used.
Exam traps to watch for
- Putting frequently accessed data in Archive. Archive is cheapest to store but retrieval takes hours and costs the most — it is for data almost never read.
- Confusing ZRS with GRS. ZRS copies across zones in ONE region (datacenter failure); GRS copies to a SECOND region (regional failure). Both are 3 copies vs 6 copies.
- Choosing AzCopy for ongoing sync. AzCopy copies files on demand; Azure File Sync keeps an on-premises file server continuously synchronised with Azure Files.
- Recommending network upload for a huge one-off migration. Terabytes over a slow link is a Data Box scenario — shipping the device is faster than uploading.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company stores large video files that viewers stream every day, plus backups it almost never reads. Which storage tier should the backups use?
Explanation: Archive is for data almost never accessed and kept long-term: cheapest storage, with retrieval taking hours — the right trade-off for backups. Hot is for frequently accessed data, which describes the videos, not the backups. Premium is a performance tier for disks, not a blob access tier. Reversing the tiers (Cool for videos, Hot for backups) would pay the most to store the data read least.
Exam objective: AZ-900 Describe Azure storage services: describe storage tiers
Q2.A company needs its stored data to survive the failure of an entire Azure region. Which redundancy option should it choose?
Explanation: GRS keeps 6 copies: 3 in the primary region and 3 in the paired secondary region, so the data survives a regional failure. LRS keeps 3 copies in one datacenter. ZRS keeps 3 copies across zones in one region — it survives a datacenter failure, not a regional one. A local disk backup is not an Azure Storage redundancy option.
Exam objective: AZ-900 Describe Azure storage services: describe redundancy options
Q3.A company wants to replace its on-premises file server with cloud storage that applications can access using the standard SMB protocol, like a network drive. Which Azure service should it use?
Explanation: Azure Files provides managed file shares using SMB/NFS, accessible like a traditional network drive — the file-server replacement. Blob Storage is object storage for unstructured data, not a file share. Queues pass messages between application components. Tables store NoSQL key-attribute data.
Exam objective: AZ-900 Describe Azure storage services: compare Azure Storage services
Q4.An application is split into two parts: one part creates work items and the other processes them later, at its own pace. Which storage service should pass the work items between the two parts?
Explanation: Azure Queues store messages between application components, letting one part produce work and another consume it asynchronously. Disks are storage attached to VMs. Files are shared file storage. Blob Storage holds unstructured object data, not a message queue.
Exam objective: AZ-900 Describe Azure storage services: compare Azure Storage services
Q5.A company has 80 TB of data on an on-premises server and a slow internet connection. It needs the data in Azure within two weeks. What is the most practical way to move it?
Explanation: Azure Data Box is a physical device shipped to the customer: load around 100 TB, ship it back, Microsoft uploads it — far faster than weeks of uploading over a slow link. AzCopy over a slow connection would take too long for 80 TB. Email is not a data-migration method. File Sync synchronises file servers continuously; it does not solve the bandwidth problem for a one-off bulk move.
Exam objective: AZ-900 Describe Azure storage services: describe migration options, including Azure Migrate and Azure Data Box
Q6.A company wants to assess its on-premises servers, estimate what they would cost in Azure, and then migrate them. Which service provides this end-to-end migration hub?
Explanation: Azure Migrate discovers on-premises servers, assesses them, estimates Azure costs, and migrates workloads. Storage Explorer is a graphical tool for managing storage accounts. AzCopy copies files to and from storage. File Sync synchronises a file server with Azure Files — none of them assesses and migrates servers.
Exam objective: AZ-900 Describe Azure storage services: describe migration options, including Azure Migrate and Azure Data Box
Q7.An administrator needs to copy thousands of files from a local folder into Blob Storage as part of an automated nightly script. Which tool is designed for this?
Explanation: AzCopy is the command-line copy tool for blobs and files — fast, scriptable, and built for bulk transfers in automation. Storage Explorer is a graphical application for interactive use, not scripting. File Sync keeps a file server synchronised continuously. Azure Migrate moves servers and applications, not files in a script.
Exam objective: AZ-900 Describe Azure storage services: identify options for moving files, including AzCopy, Azure Storage Explorer, and Azure File Sync
Q8.How many copies of data does zone-redundant storage (ZRS) keep, and where?
Explanation: ZRS keeps 3 copies spread across availability zones within the primary region, surviving a datacenter failure. 3 copies in one datacenter describes LRS. 6 copies across two regions describes GRS or GZRS. No option keeps only 2 copies.
Exam objective: AZ-900 Describe Azure storage services: describe redundancy options