Blob Storage Access Tiers and Lifecycle – Complete Guide for DP-900
Why Is This Topic Important?
Azure Blob Storage is one of the most widely used services in Azure, and understanding its access tiers and lifecycle management is critical for both real-world cost optimization and the DP-900 exam. Microsoft frequently tests candidates on their ability to choose the correct access tier for a given scenario and to understand how lifecycle policies automate data movement. Mastering this topic ensures you can:
• Reduce storage costs by placing data in the most cost-effective tier
• Automate data management without manual intervention
• Answer scenario-based exam questions with confidence
What Are Blob Storage Access Tiers?
Azure Blob Storage offers multiple access tiers that let you store data at different price points based on how frequently the data is accessed. The four tiers are:
1. Hot Tier
• Optimized for data that is accessed frequently
• Highest storage cost, but the lowest access (read/write) cost
• Example: Active web content, real-time analytics data, images served on a website
2. Cool Tier
• Optimized for data that is infrequently accessed and stored for at least 30 days
• Lower storage cost than Hot, but higher access cost
• Example: Short-term backups, older reports that are occasionally reviewed
3. Cold Tier
• Optimized for data that is rarely accessed and stored for at least 90 days
• Lower storage cost than Cool, but higher access cost than Cool
• Example: Compliance data that must be retained but is seldom read
4. Archive Tier
• Optimized for data that is rarely or never accessed and stored for at least 180 days
• Lowest storage cost, but the highest access cost
• Data is stored offline — it is not immediately available; you must rehydrate (move it to Hot or Cool) before reading it
• Rehydration can take hours (up to 15 hours for standard priority)
• Example: Long-term archival data, regulatory records, historical datasets
Key Comparison Table
| Tier | Storage Cost | Access Cost | Min Retention | Availability |
| Hot | Highest | Lowest | None | Immediate |
| Cool | Lower | Higher | 30 days | Immediate |
| Cold | Even Lower | Even Higher | 90 days | Immediate |
| Archive | Lowest | Highest | 180 days | Requires Rehydration |
How Do Access Tiers Work?
• Access tiers can be set at the account level (Hot or Cool as default) or at the individual blob level (Hot, Cool, Cold, or Archive).
• The Archive tier can only be set at the blob level, not at the account level.
• You can change a blob's tier at any time, but moving data out of Cool, Cold, or Archive before the minimum retention period incurs an early deletion penalty.
• When you move a blob from Archive to Hot or Cool, this process is called rehydration. There are two rehydration priorities: Standard (up to 15 hours) and High (under 1 hour for blobs under 10 GB, but more expensive).
What Is Blob Lifecycle Management?
Lifecycle management is a rule-based policy that automatically transitions blobs between access tiers or deletes them based on conditions you define. This eliminates the need for manual data management and helps optimize costs continuously.
How Lifecycle Management Works:
1. You define rules in a lifecycle management policy attached to a storage account.
2. Each rule contains:
• Filters – specify which blobs the rule applies to (e.g., by blob name prefix or blob type)
• Actions – specify what happens when the condition is met
3. Actions can include:
• tierToCool – Move blob to Cool tier after X days since last modification
• tierToCold – Move blob to Cold tier
• tierToArchive – Move blob to Archive tier
• delete – Delete the blob entirely
4. Rules are evaluated once per day by Azure automatically.
Example Lifecycle Policy Scenario:
• Move blobs to Cool tier if not modified for 30 days
• Move blobs to Archive tier if not modified for 90 days
• Delete blobs if not modified for 365 days
This is extremely powerful for organizations that generate large volumes of data and want to manage costs without manual intervention.
Real-World Use Cases
• Media company: Hot tier for recently uploaded videos; Cool tier after 30 days; Archive after 1 year
• Healthcare: Patient records in Cool tier; moved to Archive for long-term regulatory compliance
• Financial services: Transaction logs in Hot; moved to Cold after 90 days; archived after 1 year; deleted after 7 years
Important Details for the Exam
• Only block blobs and append blobs support tiering. Page blobs do not support access tiers.
• The Archive tier is offline — you cannot read or modify a blob in the Archive tier without rehydrating it first.
• Lifecycle management policies work with General Purpose v2 (GPv2) and Blob Storage accounts.
• You can also apply lifecycle rules to blob versions and snapshots.
Exam Tips: Answering Questions on Blob Storage Access Tiers and Lifecycle
Tip 1: Focus on the Access Pattern
When a question describes how often data is accessed, match it to the correct tier:
• Frequently accessed → Hot
• Infrequently accessed (30+ days) → Cool
• Rarely accessed (90+ days) → Cold
• Almost never accessed, long-term retention (180+ days) → Archive
Tip 2: Remember the Cost Trade-off
Storage cost and access cost are inversely related. Lower storage cost = higher access cost. If a question asks about minimizing cost for rarely accessed data, the answer is usually Archive or Cold. If it asks about minimizing access cost for frequently read data, the answer is Hot.
Tip 3: Archive Is Offline
If a question mentions that data must be immediately readable, Archive is not the correct answer. Archive requires rehydration, which takes hours. This is a common trap in exam questions.
Tip 4: Know Lifecycle Management Triggers
Lifecycle rules trigger based on last modified date or creation date. If a question describes automating the movement of aging data between tiers, the answer is lifecycle management policy.
Tip 5: Early Deletion Penalties
If data is deleted or moved out of Cool (before 30 days), Cold (before 90 days), or Archive (before 180 days), there is a penalty. If a question mentions storing data for a short time in a lower tier, watch out for this detail.
Tip 6: Account-Level vs. Blob-Level Tiers
The default access tier (Hot or Cool) is set at the account level. Individual blobs can override this. The Archive tier can only be set at the blob level. If a question asks about setting the Archive tier for the entire account, the answer is that this is not possible.
Tip 7: Distinguish Lifecycle Management from Other Features
Do not confuse lifecycle management with:
• Soft delete (protects against accidental deletion)
• Versioning (maintains previous versions of blobs)
• Immutable storage (prevents modification or deletion for compliance)
Lifecycle management is specifically about automating tier transitions and deletion based on age.
Tip 8: Watch for Keywords in Exam Questions
• "minimize storage cost" → Think Archive or Cold
• "automate data movement" → Think lifecycle management
• "data must be available immediately" → Eliminate Archive
• "compliance retention for years" → Think Archive + lifecycle policy
• "occasionally accessed" → Think Cool
Summary
Azure Blob Storage access tiers (Hot, Cool, Cold, Archive) allow you to optimize costs based on data access frequency. Lifecycle management policies automate the process of transitioning blobs between tiers and deleting old data. For the DP-900 exam, focus on matching access patterns to the correct tier, understanding the cost trade-offs, remembering that Archive is offline and requires rehydration, and knowing that lifecycle management automates tier transitions based on blob age. These concepts are fundamental to Azure data storage and are commonly tested in scenario-based questions.
