AZ-104 Implement and Manage Storage Practice Question
You need to move infrequently accessed blob data automatically from the Hot tier to the Cool tier after 30 days to reduce cost. What should you configure?
⚠ Common exam trap
Test-takers frequently confuse blob soft delete (which only handles recovery) with lifecycle management (which handles automated tiering and deletion), leading them to choose soft delete when the question asks about cost optimization through tier transitions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Lifecycle management rules
Azure Blob Storage lifecycle management rules allow you to automatically transition blobs from the Hot tier to the Cool tier based on age or other conditions. By configuring a rule that moves blobs to the Cool tier after 30 days from creation or last modification, you reduce storage costs for infrequently accessed data without manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Blob soft delete
Why it's wrong here
Blob soft delete preserves deleted blobs and snapshots for a configurable retention period so you can recover them after accidental deletion. While a soft-deleted blob is marked as deleted and inaccessible to normal read/write operations, it remains in its current access tier and is never migrated downward. Soft delete is a data-integrity and disaster-recovery mechanism, not a cost-management tool, so it cannot move infrequently accessed blobs from Hot to Cool based on usage patterns.
When this WOULD be correct
You need to recover blobs that were accidentally deleted or overwritten within a specified retention period. Configure blob soft delete to enable data recovery after deletion.
- ✓
Lifecycle management rules
Why this is correct
Lifecycle management rules are the native Azure Blob Storage feature that automates tier transitions. You define a JSON policy on the storage account that evaluates blobs after a specified number of days (based on last modification) and moves them from Hot to Cool, Cool to Archive, or deletes them. This directly addresses the requirement to automatically shift infrequently accessed data to a lower-cost tier without manual intervention. Rules can filter by blob prefix or type, giving precise control.
- ✗
A private endpoint
Why it's wrong here
A private endpoint is a network-security construct from Azure Private Link that gives a storage account a private IP address inside a virtual network, routing all traffic privately and bypassing the public internet. It changes the network path and authentication context but leaves the blob's physical tier unchanged. Since the endpoint only controls connectivity and not storage behavior, it cannot observe access frequency or schedule a transition to the Cool tier, so it is irrelevant to automated tier moves.
When this WOULD be correct
A question that asks: 'You need to ensure that storage account access is restricted to a virtual network and no public internet access is allowed. What should you configure?' In that case, a private endpoint would be correct.
- ✗
A CanNotDelete lock
Why it's wrong here
A CanNotDelete lock is a resource governance control that prevents the storage account, container, or blob from being deleted, either accidentally or by unauthorized users. It does not alter the blob's access tier, metadata, or storage location, and it has no temporal logic to detect infrequent access. Because tier transitions and access monitoring are entirely separate operations, applying this lock merely safeguards the data from deletion and cannot automate a Hot-to-Cool move.
When this WOULD be correct
You need to prevent accidental deletion of a critical storage account while still allowing data modifications. A CanNotDelete lock would be the correct answer for a question about protecting a resource from deletion.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓Lifecycle management rulesCorrect answer▾
Why this is correct
Lifecycle management rules are the native Azure Blob Storage feature that automates tier transitions. You define a JSON policy on the storage account that evaluates blobs after a specified number of days (based on last modification) and moves them from Hot to Cool, Cool to Archive, or deletes them. This directly addresses the requirement to automatically shift infrequently accessed data to a lower-cost tier without manual intervention. Rules can filter by blob prefix or type, giving precise control.
✗Blob soft deleteWrong answer — click to see why▾
Why this is wrong here
Blob soft delete is used to protect data from accidental deletion or overwrite, not to automate tier transitions based on age. It does not move blobs between access tiers.
★ When this WOULD be the correct answer
You need to recover blobs that were accidentally deleted or overwritten within a specified retention period. Configure blob soft delete to enable data recovery after deletion.
Why candidates choose this
Candidates may confuse 'soft delete' with 'lifecycle management' because both involve time-based actions on blobs, but soft delete focuses on recovery, not cost optimization via tier changes.
✗A private endpointWrong answer — click to see why▾
Why this is wrong here
A private endpoint is used to securely connect to Azure services over a private IP address, not to manage data tier transitions. It does not automate moving blobs between Hot and Cool tiers.
★ When this WOULD be the correct answer
A question that asks: 'You need to ensure that storage account access is restricted to a virtual network and no public internet access is allowed. What should you configure?' In that case, a private endpoint would be correct.
Why candidates choose this
Candidates might confuse 'private endpoint' with 'access tier' or think it controls data movement, but it is a networking feature unrelated to lifecycle management.
✗A CanNotDelete lockWrong answer — click to see why▾
Why this is wrong here
A CanNotDelete lock prevents deletion of the storage account or container but does not manage data tier transitions. It cannot move blobs from Hot to Cool tier based on age.
★ When this WOULD be the correct answer
You need to prevent accidental deletion of a critical storage account while still allowing data modifications. A CanNotDelete lock would be the correct answer for a question about protecting a resource from deletion.
Why candidates choose this
Candidates may confuse resource locks with lifecycle management, thinking a lock can control data movement or retention, or they may misapply the concept of 'locking' data to a specific tier.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
Learn chapter
Privileged Identity Management (PIM)
Key term
Blob
A blob is a large piece of unstructured data, like a photo or video, stored in the cloud with a unique identifier.
Key term
Cool tier
Cool tier is a low-cost, online-only storage access tier in Microsoft Azure Blob Storage designed for data that is infrequently accessed and stored for at least 30 days.
About these practice questions
Courseiva writes every AZ-104 question from scratch — 1,049 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.