Match each Azure service tier to its description.
Drag a concept onto its matching description — or click a concept then click the description.
Hierarchical namespace for Azure Data Lake Storage
Optimized for frequent data access
Optimized for infrequent access with lower cost
Lowest cost for rarely accessed data
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Hot: Optimized for data that is accessed frequently and has low latency requirements.
In Azure Blob Storage and Data Lake Storage, access tiers are optimized for different access patterns. Hot is for frequent access, Cool for infrequent access (30 days), Cold for less frequent access (90 days), and Archive for rarely accessed data (180 days). Common confusions include swapping Cool and Cold descriptions or misattributing Archive characteristics.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Hot: Optimized for data that is accessed frequently and has low latency requirements.
Why this is correct
The Hot tier is designed for frequent access with low latency, and has the highest storage cost but lowest access cost.
Cool: Optimized for infrequently accessed data stored for at least 30 days.
Why this is correct
The Cool tier is for data accessed infrequently, stored at least 30 days, with lower storage cost and higher access cost.
Cold: Optimized for infrequently accessed data stored for at least 90 days.
Why this is correct
The Cold tier is for data accessed infrequently but stored for at least 90 days, with even lower storage cost.
Archive: Optimized for rarely accessed data stored for at least 180 days.
Why this is correct
The Archive tier is for rarely accessed data, stored for at least 180 days, with the lowest storage cost and highest access cost.
Cool: Optimized for rarely accessed data stored for at least 180 days.
Why it's wrong here
Incorrect — this description matches the Archive tier, not Cool.
Hot: Optimized for infrequently accessed data stored for at least 30 days.
Why it's wrong here
Incorrect — this description matches the Cool tier, not Hot.
Quick reference
| 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
About these practice questions
One of 760 original DP-203 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 →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-203 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-203 exam.