AZ-204 Develop for Azure storage Practice Question
You are designing a cost-effective solution to store log files that are accessed infrequently after 30 days. The logs must be retained for 7 years for compliance. Data must be available within 1 hour of a request. Which Azure Blob Storage access tier and lifecycle management rule should you use?
⚠ Common exam trap
The trap here is that candidates often overlook the 1-hour availability requirement and choose Archive tier immediately (Option B) or skip the Cool tier (Option A), not realizing that Archive rehydration can take up to 15 hours unless High Priority is explicitly used, and that Hot tier is more cost-effective for the initial high-write period.
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
✓
Use Hot tier for 30 days, then Cool tier until 90 days, then Archive tier until deletion after 7 years.
It balances cost and compliance: the Hot tier handles initial frequent writes, Cool tier reduces cost for infrequent access after 30 days, and Archive tier provides the lowest-cost storage for long-term retention while still allowing rehydration within 1 hour (via High Priority rehydration). The lifecycle rule deletes the blobs after 7 years to meet compliance requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Hot tier initially, then move to Archive after 30 days, and delete after 7 years.
Why it's wrong here
This option is not cost-effective for typical log file access patterns. While the Hot tier is appropriate initially, moving directly to the Archive tier after only 30 days is problematic because log files often require access for troubleshooting or analysis beyond the first month. The Archive tier incurs high retrieval costs and significant latency (hours for rehydration), which would lead to substantial expenses if logs needed to be accessed between 30 days and the typical 90-day 'cool' period.
- ✗
Use Archive tier immediately and set a lifecycle rule to delete after 7 years.
Why it's wrong here
Storing log files immediately in the Archive tier is highly impractical and inefficient for any scenario where recent logs might need to be accessed. The Archive tier is specifically designed for rarely accessed, long-term retention, incurring the highest data retrieval costs and requiring several hours for rehydration before data becomes usable. This approach completely disregards the common operational need for immediate or near-immediate access to recent log data for monitoring and troubleshooting, making it unsuitable for active log storage.
- ✗
Use Cool tier initially, then move to Archive after 30 days, and delete after 7 years.
Why it's wrong here
While the Cool tier offers lower storage costs than the Hot tier, it incurs higher transaction costs per access. For log files, especially recent ones, frequent access for monitoring, debugging, or analytics is common within the initial period. Starting directly in the Cool tier would lead to increased transaction costs if logs are accessed frequently, potentially negating any storage cost savings compared to the Hot tier, which is optimized for frequent access with lower transaction fees.
- ✓
Use Hot tier for 30 days, then Cool tier until 90 days, then Archive tier until deletion after 7 years.
Why this is correct
This strategy provides an optimal balance between cost-effectiveness and data accessibility requirements for log files. The Hot tier ensures immediate, low-cost access for frequently used recent logs (e.g., first 30 days). Transitioning to the Cool tier for the next period (e.g., 30-90 days) reduces storage costs for data that is less frequently accessed but still potentially needed. Finally, moving to the Archive tier for long-term retention (up to 7 years) minimizes costs for rarely accessed historical data, aligning perfectly with typical log data lifecycle patterns.
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.