AZ-305 Design data storage solutions Practice Question
A media company needs to store large video files that are frequently accessed for the first month, then infrequently after that. They want to minimize storage costs while ensuring files are instantly accessible when needed. Which storage strategy should they implement?
⚠ Common exam trap
Many candidates choose manual tiering (Option B) thinking it offers more control, but the exam tests the understanding that Azure's built-in lifecycle management is the automated, cost-optimized solution for predictable access patterns, and that archive tier (Option C) is not instantly accessible.
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 Azure Blob Storage lifecycle management to move files from hot to cool after 30 days
Azure Blob Storage lifecycle management allows you to define rules that automatically transition blobs from the hot tier (frequent access) to the cool tier (infrequent access) after a specified number of days. This meets the requirement of instant accessibility for the first month and cost minimization thereafter, as the cool tier offers lower storage costs with the same low-latency access as the hot tier.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store all files in the hot access tier
Why it's wrong here
Storing all files permanently in the hot access tier incurs higher per-gigabyte storage charges than cooler tiers, yet after the first month the access pattern drops sharply. This fails the requirement to minimise costs because the hot tier is designed for consistently frequent reads, not for a workload that becomes archival. The option is tempting because the hot tier guarantees instant retrieval with no latency penalty, making it the correct choice for data that requires consistently low-latency access throughout its lifecycle.
- ✗
Manually move files between tiers using AzCopy
Why it's wrong here
AzCopy is a CLI tool for copying blobs, not automating tier transitions. Relying on manual moves requires custom scheduling, age tracking, and error handling, which is inefficient and error-prone at scale. Each AzCopy copy operation consumes compute and network resources, and the copy may not preserve metadata or access tier semantics the same way that an in-place tier change does. Lifecycle management avoids these manual actions by using Azure-native, server-side policies that run automatically.
- ✗
Store all files in the archive access tier
Why it's wrong here
Storing every file in the archive access tier from the start ignores the recent files that are still being actively accessed and edited. Archive blobs must be rehydrated to an online tier before they can be read, incurring retrieval latency of up to 15 minutes or more and additional rehydration and read costs. The archive tier also enforces a 180-day minimum retention period, so deleting or moving files before that period accrues early deletion penalties. This approach trades low storage price for unacceptable access latency and can end up costing more when rehydration fees and operational delays are factored in.
- ✓
Use Azure Blob Storage lifecycle management to move files from hot to cool after 30 days
Why this is correct
Azure Blob Storage lifecycle management lets you define a policy that automatically transitions blobs from the hot tier to the cool tier after 30 days since last modification, matching the stated access pattern. This is the correct approach because it is server-side, transparent, and eliminates manual intervention while reducing storage costs as content ages. The cool tier still offers low-latency reads, so any occasional access to older videos remains convenient without paying hot-tier storage rates. Because lifecycle management manipulates tier metadata rather than copying data, it avoids the network and compute overhead associated with manual moves.
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
Courseiva writes every AZ-305 question from scratch — 795 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-305 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-305 exam.