Describe considerations for working with non-relational data on Azure →mediumMultiple ChoiceObjective-mapped
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
A company stores large video files in Azure Blob Storage. The files are accessed frequently for the first 30 days after upload, then rarely for the next 180 days, and after that they are only needed for compliance but never accessed. The company wants to minimize storage costs while ensuring the files remain durable and accessible. Which strategy should they implement?
⚠ Common exam trap
Candidates often assume the Cool tier is the cheapest option for long-term storage, overlooking the Archive tier's significantly lower cost for compliance data that is never accessed, and they may also forget that lifecycle management can automate multiple tier transitions over time.
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
✓
Store files initially in the Hot tier, then use lifecycle management to move files to Cool after 30 days and to Archive after 210 days.
It aligns the access patterns with the appropriate Azure Blob Storage access tiers: Hot for frequent initial access, Cool for reduced-cost infrequent access after 30 days, and Archive for the lowest-cost long-term retention after 210 days. Azure lifecycle management policies automate these transitions, ensuring durability and accessibility while minimizing costs.
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 Cool access tier and apply lifecycle management to move files to the Archive tier after 30 days.
Why it's wrong here
The Cool tier is not optimal for the first 30 days of frequent access because it has higher read costs and lower availability than Hot. Moving to Archive after 30 days is too early for the 180-day period of rare access.
- ✓
Store files initially in the Hot tier, then use lifecycle management to move files to Cool after 30 days and to Archive after 210 days.
Why this is correct
The Hot tier optimizes the initial 30 days when end users actively upload and retrieve video files; its storage cost is higher but it has no retrieval penalty, making frequent data movement inexpensive. A lifecycle management policy then automatically transitions each blob to Cool after 30 days because Cool reduces storage charges for the 180-day period of rare access, despite a small per-GB retrieval cost. After 210 days, the policy moves the blob to Archive, which provides the lowest storage cost for the compliance period when files are never accessed but must be retained. This staged approach exactly aligns costs with the actual access pattern while avoiding manual intervention and the risk of premature transitions.
- ✗
Store files in the Archive tier from the beginning to maximize cost savings.
Why it's wrong here
Placing files directly in the Archive tier appears to minimize storage charges, but Archive is designed for data that is rarely accessed and requires explicit rehydration to Hot or Cool before a blob can be read. During the first 30 days, frequent reads would trigger repeated rehydration operations, incurring substantial read, data retrieval, and egress costs, plus a latency of hours or up to 15 hours, which is unacceptable for active video access. The storage savings per GB do not offset these retrieval penalties when access density is high, so the total cost of ownership is actually greater than using Hot initially. Thus, Archive-from-the-start fails the business requirement for immediate availability during the launch window.
- ✗
Store files in the Premium tier for fast access, then manually delete files after 30 days.
Why it's wrong here
The Premium blob tier is a block blob offering backed by SSDs, intended for high-transaction-rate workloads such as virtual machine disks or telemetry ingestion, and its per-GB price is far above Hot or Cool, making it uneconomical for storing large video files. Relying on the Premium tier for the first 30 days consumes SSD capacity and incurs high storage costs without any offsetting functional benefit because videos do not require the low-millisecond latency Premium guarantees. Additionally, manually deleting files after 30 days completely forfeits the 210-day compliance retention requirement, and manual deletion is error-prone, potentially deleting data before retention expires or leaving data that should be archived. An automated lifecycle policy would correctly downgrade to Cool and then Archive while maintaining durability and compliance.
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
One of 820 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-900 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 DP-900 exam.