Storage Accounts in Azure
A Storage Account is the fundamental building block of Azure Storage. It provides a unique namespace for your data in Azure and acts like the “container” that holds all storage services (blobs, files, queues, tables, disks).
Key Concepts
- Each storage account gets a unique name and endpoint (e.g., mystorage.blob.core.windows.net).
- Data in a storage account is always replicated based on redundancy settings (LRS, ZRS, GRS, RA-GRS).
- Supports different performance tiers: Standard (HDD, cost-optimized) vs Premium (SSD, low latency).
Types of Storage Accounts
- General-purpose v2: Most common, supports blobs, files, queues, and tables. Default choice in almost all scenarios.
- BlockBlobStorage: Optimized for block blobs (media, backup, big data).
- FileStorage: High-performance file shares.
- Premium performance tiers: For workloads needing very low latency (databases, transaction-heavy apps).
Confusion Buster 🚨
Storage Account ≠ Container
– Storage Account = the top-level container for all your data services.
– Container (inside Blob Storage) = just for blobs.
Exam trick: Many questions use “container” loosely — make sure you know whether they mean a Blob container or the Storage Account itself.
Simple Example
Think of a Storage Account like a warehouse. Inside it, you can have different sections: one for pallets (blobs), one for cupboards (files), one for message boards (queues), and one for spreadsheets (tables). But the entire warehouse is the Storage Account.
Exam Tip
Always choose General-purpose v2 unless the question specifically asks for premium scenarios. If you see keywords like “low latency” or “high-performance database workloads,” go with Premium FileStorage or BlockBlobStorage.
What to Expect in the Exam
- Direct Q: “Which storage account type supports all services?” → General-purpose v2.
- Scenario: “Company needs SSD-backed storage for database logs.” → Premium Storage Account.
- Trick Q: “A Blob container is the same as a Storage Account.” (False).