This chapter covers Azure Storage Account types and the different storage services they can contain. AZ-900 tests this under objective 2.4, building on the Blob Storage chapter with a broader view of Azure's storage options.
Jump to a section
A simple way to picture Azure Storage Account Types
A self-storage facility doesn't offer just one type of unit — it might have small lockers for documents, larger units for furniture, and climate-controlled units for sensitive items, each suited to different needs. An Azure Storage Account works similarly: it's the overall account you set up with a provider, but within it, different storage services suit different kinds of data — unstructured files, structured tables, message queues, and traditional shared file systems — each optimized for its own purpose.
What a Storage Account is
An Azure Storage Account is the top-level container for several different storage services — Blob Storage (unstructured data, covered in its own chapter), Azure Files (shared file storage), Azure Queue Storage (simple messaging), and Azure Table Storage (structured NoSQL data). A single storage account can contain any combination of these, depending on what the workload needs.
Storage account performance tiers
Storage accounts generally offer performance tiers — a Standard tier suited to most general-purpose scenarios, and a Premium tier offering higher performance for workloads that need faster, more consistent response times, at a higher cost.
Replication options
Storage accounts also offer different replication options, determining how many copies of data are kept and where — ranging from keeping multiple copies within a single region (locally-redundant storage) to replicating across paired regions (geo-redundant storage, connecting back to the Region Pairs concept from an earlier chapter). More replication generally means more resilience against data loss, at a higher cost.
Choosing the right combination
The right storage account configuration depends on the workload: a media company storing rarely accessed video archives might prioritize cost over top-tier performance, while a financial application needing consistent fast access might prioritize the Premium tier and stronger replication.
Create a storage account
A storage account is created within a chosen region, serving as the container for whichever storage services the workload needs.
Choose a performance tier
Standard suits most general-purpose scenarios; Premium suits workloads needing higher, more consistent performance, at a higher cost.
Choose a replication option
Based on how critical the data is and its resilience requirements, a replication option is chosen — ranging from single-region redundancy to geo-redundant replication across paired regions.
Use the appropriate storage service within the account
Depending on the data type — unstructured files, shared file storage, message queues, or structured NoSQL data — the appropriate storage service within the account is used.
A company running a general business application uses a Standard-tier storage account with locally-redundant storage, since its data isn't mission-critical enough to justify the higher cost of geo-redundant replication or Premium performance.
A financial trading platform, by contrast, uses a Premium-tier storage account with geo-redundant replication, since it needs both fast, consistent performance and strong protection against regional data loss — illustrating how the right configuration depends heavily on the specific workload's requirements, not a one-size-fits-all default.
Objective 2.4 expects candidates to understand that a storage account can contain multiple types of storage services, and to recognize the general purpose of performance tiers and replication options.
A common wrong answer is assuming a storage account can only hold one type of data — it can contain Blob Storage, Azure Files, Queue Storage, and Table Storage together, depending on what's configured. Another common trap is assuming higher replication or performance tiers are always the "right" choice — they come with added cost, and the appropriate choice depends on the specific workload's actual requirements.
Stable terms: Storage Account, Standard/Premium tier, replication. Recognizing that a storage account is the umbrella container for multiple storage services, not a single storage type itself, is a frequently tested distinction.
Memory trick: a Storage Account is the container; Blob Storage, Files, Queues, and Tables are different services that can live inside it, each suited to a different kind of data.
An Azure Storage Account is the container for multiple storage services, including Blob Storage, Azure Files, Queue Storage, and Table Storage.
Storage accounts offer Standard and Premium performance tiers, suited to different performance needs.
Replication options range from single-region redundancy to geo-redundant replication across paired regions.
The right combination of tier and replication depends on the specific workload's performance and resilience requirements.
These come up on the exam all the time. Here's how to tell them apart.
Locally-Redundant Storage
Multiple copies within a single region
Lower cost
Protects against a localized failure within that region
Geo-Redundant Storage
Copies replicated to a paired region as well
Higher cost
Protects against loss of an entire region, not just a local failure
Mistake
A storage account can only be used for one type of data.
Correct
A single storage account can contain multiple storage services — Blob Storage, Azure Files, Queue Storage, and Table Storage — together, depending on what the workload needs.
Mistake
Premium tier and maximum replication are always the best choice.
Correct
Higher performance tiers and stronger replication options come with added cost — the right choice depends on the specific workload's actual performance and resilience requirements, not a universal default.
Mistake
Storage Account and Blob Storage mean the same thing.
Correct
A Storage Account is the broader container; Blob Storage is one of several specific storage services that can exist within it, alongside Azure Files, Queue Storage, and Table Storage.
It's the top-level container for Azure's storage services — including Blob Storage, Azure Files, Queue Storage, and Table Storage — letting an organization configure performance tier and replication settings that apply to the services within it.
Standard suits most general-purpose scenarios at a lower cost. Premium offers higher, more consistent performance for workloads that need faster response times, at a higher cost.
Geo-redundant storage replicates data to a paired region as well as locally, protecting against the loss of an entire region, not just a localized failure. It costs more than locally-redundant storage, so the choice depends on how critical that extra protection is for the specific data.
You've just covered Azure Storage Account Types — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?