Blob Lifecycle Management
You are developing a .NET Core application that stores user profile images in Azure Blob Storage. The images are accessed frequently in the first week after upload, then rarely afterwards. You need to minimize storage costs while maintaining immediate access for the first week. What should you do?
Quick Answer
The correct answer is to implement a lifecycle management policy to move blobs to the Cool tier 7 days after creation. This solution directly addresses the access pattern by using blob lifecycle management tier transition to automatically shift data from Hot to Cool storage after the first week, minimizing costs while preserving immediate access during the high-frequency period. On the Microsoft Azure Developer Associate AZ-204 exam, this scenario tests your understanding of automated cost optimization strategies versus manual tier changes or default tier adjustments, which are common traps—changing the default tier to Cool would introduce latency for new uploads, while Archive would break the immediate access requirement. A key memory tip is to think of lifecycle policies as a “set-and-forget” schedule: you define the rule based on age, and Azure handles the tier transition, ensuring you never pay Hot prices for cold data.
⚠ Common exam trap
Many exam-takers confuse 'default access tier' (which applies to all new blobs immediately) with 'lifecycle management' (which applies rules after creation), leading them to incorrectly choose Option B or A, while overlooking the automated, policy-driven approach in Option D.
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
✓
Implement a lifecycle management policy to move blobs to Cool tier 7 days after creation.
Azure Blob Storage lifecycle management policies allow you to automatically transition blobs to a cooler tier (Cool) after a specified number of days, minimizing storage costs while maintaining immediate access for the first week. This policy is applied at the storage account level and requires no manual intervention or scheduled jobs, ensuring that blobs remain in the Hot tier for the first 7 days (frequent access) and then move to Cool tier (lower cost, still immediate access).
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manually change the blob tier to Cool after 7 days using a scheduled job.
Why it's wrong here
Manual process is error-prone and not cost-effective; lifecycle management is preferred.
- ✗
Set the default access tier of the storage account to Cool.
Why it's wrong here
Cool tier has higher retrieval latency and is not optimal for frequent access in the first week.
- ✗
Store blobs in Archive tier and use rehydration when needed.
Why it's wrong here
Archive tier has high retrieval latency and cost, unsuitable for immediate access within a week.
- ✓
Implement a lifecycle management policy to move blobs to Cool tier 7 days after creation.
Why this is correct
Automates tier transition after the frequent access period, balancing cost and performance.
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
About these practice questions
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-204
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are developing an application that stores user-uploaded profile pictures in Azure Blob Storage. Users frequently access these pictures for the first 7 days after upload, then rarely. To minimize costs, you need to automatically delete pictures that are older than 30 days. Which Azure Storage feature should you use to achieve this?
easy- ✓ A.Lifecycle management policy
- B.Blob snapshots
- C.Change feed
- D.Soft delete
Why A: Azure Blob Storage lifecycle management policies allow you to automatically tier or expire blobs based on age. By defining a rule that deletes blobs after 30 days from creation, you can remove old profile pictures without manual intervention, directly minimizing storage costs.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 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-204 exam.