Blob Storage
Object storage in containers, with lifecycle tiering, versioning, snapshots, immutability and lease-based concurrency.
Readiness
0%
2h 30m baseline
Exam memorization points
- Hierarchy is account > container > blob. Container names must be lowercase and are part of the URL.
- Blob types: block blobs (files and streaming), append blobs (logs), and page blobs (VHD backing for unmanaged disks).
- Data protection features are separate switches: blob soft delete, container soft delete, blob versioning, change feed, snapshots and immutable storage.
- Lifecycle management rules can transition tiers or delete blobs, and can be filtered by prefix or by blob index tags.
- Anonymous access levels are private, blob and container - and the account-level AllowBlobPublicAccess switch gates all of them.
- A blob lease lets a client lock a blob for write, read or delete with a lease ID; leases protect against concurrent writers.
Traps & distractors
- Reading from the Archive tier. Objects must be rehydrated (standard priority takes hours, high priority is faster) before any read works.
- Turning on blob versioning but not soft delete, which leaves deletions unprotected.
- Expecting container-level public access to work when AllowBlobPublicAccess is disabled on the account - the effective setting is the intersection.
- Confusing immutable storage time-based retention (objects cannot be modified or deleted until the period ends, and a locked policy cannot be shortened) with legal hold (no end date).
- Assuming lifecycle rules run immediately. Rules are evaluated once per day and tier transitions may take time.
Suggested lab
Tier, protect and share blobs
Configure the blob data protection stack and observe lifecycle behaviour.
- 1Create a container and upload a mix of small and large files.
- 2Enable blob soft delete, container soft delete, versioning and change feed on the account.
- 3Add a lifecycle rule with prefix filtering that cools at 30 days, archives at 180 days and deletes at 365 days.
- 4Upload a new version of a file, delete it, then restore the previous version.
- 5Generate a read-only SAS for a single blob with a short expiry and verify it cannot list the container.
Microsoft Learn
- Introduction to Azure Blob Storagedoc
- Search Microsoft Learn: blob lifecycle management soft delete versioning immutability leasesearch
Live Microsoft Learn ingestion is a Sprint 2 item; until then links are curated and the search fallback always resolves.
Status
No time invested yet. Baseline assumptions only.
Self-assessed mastery
0%
Critical priority
High-yield and still weak. Study this next.
- Exam importance100% × 30% = 30.0
Learner-agnostic frequency on the real exam (5/5).
- Blueprint weight78% × 25% = 19.4
This topic's domain carries 17.5% of the exam objectives.
- Dependency leverage20% × 20% = 4.1
1 later topic depend on it.
- Current gap100% × 25% = 25.0
Readiness is 0%, so 100% of the topic is still uncovered.
Exam Priority Score = 30% importance + 25% blueprint + 20% dependency + 25% gap. Importance is exam frequency, blueprint is the domain's official exam weight, dependency is how many later topics this one unlocks, and gap is how far you currently are from ready.
Unlocks next
Baseline study time
2h 30m
Complexity
3 / 5
Remaining to target
2h 8m
Status weight
0%
Topics: container, block blob, append blob, page blob, soft delete, versioning, immutable, lifecycle, lease
Weak neighbours in Storage