Study guide
4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning
Key Takeaways Explain This Topic AI
Blob access tiers optimize cost based on access frequency and retrieval expectations, not just storage size.
Lifecycle management policies automate transitions, deletion, and cleanup based on age, modification time, version age, and other filters.
Soft delete, versioning, container soft delete, and point-in-time restore solve different recovery problems.
Archive tier minimizes storage cost but requires rehydration before reads and is unsuitable for immediate access.
Exam scenarios often combine accidental deletion, ransomware recovery, compliance retention, and cost optimization.
Last updated: May 2026
Cost and recovery are designed together
Azure Blob Storage access tiers are not labels for importance. They are cost and access behavior choices. Hot is optimized for frequently accessed data with higher storage cost and lower access cost. Cool is for infrequently accessed data that still needs online access. Cold, where available, fits less frequent access than cool while keeping data online. Archive is offline and has the lowest storage cost, but data must be rehydrated before it can be read. The correct tier depends on how quickly data must be accessed, how often it is read, and how long it will be retained.
- Tier Access behavior Typical use Exam warning
- Hot Online, frequent reads Active documents, app content Higher capacity cost than cooler tiers
- Cool Online, infrequent reads Monthly reports, short-term backups Early deletion and access costs may apply
Cold Online, rare reads Long-retention data needing online metadata and access Check regional and account support
Archive Offline until rehydrated Compliance archives, old exports Cannot read immediately; rehydration takes time
Tiering can happen at the account default access tier for new blobs or at the blob level for block blobs. Lifecycle management policies automate tier changes and deletions. A policy can move blobs to cool after 30 days, archive after 180 days, and delete after 2555 days. Policies can filter by prefix, blob type, tags, and other conditions. They can also act on previous versions and snapshots, which is important when versioning is enabled and old versions start consuming unexpected capacity.
Portal path example: Storage account > Data management > Lifecycle management > Add a rule. Choose a rule name, scope, blob type, prefix match, optional blob index match, and actions for base blobs, snapshots, or versions. For one-off tier changes, use Storage account > Containers > select blob > Change tier. At account level, use Configuration to set the default access tier for new blobs where supported.
- CLI examples: az storage blob set-tier \
- -account-name staz104prod01 \
- -container-name reports \
- -name 2025/q4/export.csv \
- -tier Cool \
- -auth-mode login
- az storage account blob-service-properties update \
- -account-name staz104prod01 \
- -resource-group rg-storage-prod \
- -enable-delete-retention true \
- -delete-retention-days 14 \
- -enable-container-delete-retention true \
- -container-delete-retention-days 14
Soft delete protects deleted blobs for a retention period. During that period, an administrator can restore the deleted blob. Container soft delete protects deleted containers. Blob versioning keeps previous versions when a blob is overwritten or deleted, giving a stronger recovery story for accidental overwrite. Snapshots are point-in-time copies created explicitly, while versions are created automatically when versioning is enabled. Point-in-time restore can restore block blobs to an earlier state within the configured retention window when prerequisites are met.
- Problem Best-fit feature Why
- User deletes a blob Blob soft delete Restore deleted blob within retention period
- User deletes a container Container soft delete Recover the container and its blobs
- App overwrites a blob with bad content Blob versioning Restore a previous version
- Need explicit point-in-time copy before change Blob snapshot Manual restore point for a blob
- Need broad rollback after corruption Point-in-time restore Restores block blob state within a time window
- Need automated cost optimization Lifecycle management Moves or deletes data by policy
Archive tier troubleshooting is a common case. If a user tries to read an archived blob, the operation fails because the blob is offline. Rehydrate it to hot or cool, choose a rehydration priority where supported, and wait until the archive status clears. Do not promise instant access. Also remember that changing tiers can have cost implications. Moving data too early from cool or archive can trigger early deletion charges depending on the tier rules.
Lifecycle troubleshooting starts with filters and dates. If a rule did not move a blob, check whether the blob type is supported, whether the prefix matches exactly, whether the rule is enabled, whether the action applies to base blobs or versions, and whether the age condition is based on last modification or creation behavior. If costs continue rising after enabling versioning, inspect old versions and snapshots. Data protection features preserve data, which means they can also preserve billable data.
Compliance scenarios need careful wording. Soft delete and versioning help recovery, but they are not the same as immutable storage or legal hold. If the requirement says users must not be able to modify or delete data for a retention period, look for immutability policies rather than only soft delete. If the requirement says recover from accidental deletion by an administrator, soft delete may be enough. If the requirement says recover from overwrite, use versioning.
Case scenario: a media company stores raw video uploads for active editing for 14 days, rarely reads them after 90 days, and must retain them for seven years. Editors also accidentally overwrite metadata files. A practical design is hot tier for new data, lifecycle rules to cool or cold after the active window, archive after the rare-access period if retrieval delay is acceptable, delete only after the retention requirement, blob versioning for overwrite recovery, soft delete for accidental deletes, and monitoring for retained versions.
If a legal retention requirement forbids deletion, add immutable storage policy rather than relying only on lifecycle rules.