AZ-204 Develop for Azure storage Practice Question
Your application uses Azure Blob Storage to store images. You need to automatically move blobs older than 30 days to the Cool tier and delete blobs older than 365 days. What should you implement?
⚠ Common exam trap
The trap here is that candidates often over-engineer the solution by choosing Azure Automation or Logic Apps for scheduled tasks, not realizing that Azure Blob Storage has a built-in, serverless lifecycle management feature that directly handles age-based tiering and deletion without any external compute or orchestration.
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
✓
Azure Blob Storage lifecycle management policy
Azure Blob Storage lifecycle management policies allow you to define rules that automatically transition blobs to cooler tiers (e.g., Cool) after a specified number of days and delete them after a different number of days. This is the native, cost-effective, and fully managed solution for automating tier transitions and deletions based on blob age, without requiring external compute or orchestration services.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure Automation runbook on a schedule
Why it's wrong here
An Azure Automation runbook could be scheduled to execute PowerShell or Python scripts that iterate through blob containers, check blob properties like last modified time, and then programmatically change tiers or delete blobs. While technically feasible, this approach introduces significant operational overhead for script development, maintenance, and error handling. It is not the native, declarative solution designed for efficient blob lifecycle management within Azure Storage, making it less efficient and more complex than built-in features.
- ✗
Azure Logic Apps with recurrence trigger
Why it's wrong here
Azure Logic Apps would necessitate custom actions to iterate through all blobs, determine their age, and then programmatically initiate tier changes or deletions. This approach is inefficient and overly complex for managing blob lifecycle, which Azure Blob Storage offers as a native, declarative policy feature. Logic Apps are tempting as they are excellent for orchestrating serverless workflows and integrating diverse services based on recurrence or events, making them ideal for custom processing tasks, such as resizing an image upon upload, rather than automated storage tier management.
- ✓
Azure Blob Storage lifecycle management policy
Why this is correct
Azure Blob Storage lifecycle management policies provide a native, declarative, and cost-effective way to automatically transition blobs to cooler access tiers (e.g., Hot to Cool, Cool to Archive) or delete them after a specified period. These policies are configured directly on the storage account and apply rules based on blob age, last modified time, or other conditions, eliminating the need for custom code or external services. This ensures optimal storage costs by moving less frequently accessed data to cheaper tiers.
- ✗
Azure Event Grid subscription with blob created event
Why it's wrong here
An Azure Event Grid subscription triggered by a "blob created" event would react immediately when a new blob is uploaded, but it is not suitable for managing the lifecycle of *existing* blobs based on their age or for periodic cleanup. Event Grid is designed for real-time event-driven processing, such as triggering an image resize upon upload, rather than implementing scheduled tiering or deletion policies for data that has resided in storage for a specific duration.
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 →
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.