Block blobs are the correct choice for storing large binary objects up to 4.7 TB in Azure Blob Storage when you need the lowest read latency and object-level tiering support. This is because block blobs are optimized for streaming and random read access over HTTP/HTTPS, providing faster direct access compared to append or page blobs, and they natively support granular tiering between Hot, Cool, Cold, and Archive tiers without requiring a storage account move. On the Microsoft Azure Developer Associate AZ-204 exam, this question tests your understanding of blob type trade-offs—a common trap is confusing page blobs (designed for VHDs and frequent writes) with block blobs, or assuming append blobs are suitable for large binary data. Remember that block blobs handle up to ~4.74 TB, while page blobs max out at 8 TB but lack object-level tiering. A helpful memory tip: think of block blobs as “big, blocky, and tierable”—they break large files into manageable blocks for fast reads and cost-efficient lifecycle management.
AZ-204 Develop for Azure storage Practice Question
This AZ-204 practice question tests your understanding of develop for azure storage. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are developing a .NET application that needs to store and retrieve large binary objects (up to 4.7 TB) in Azure Blob Storage. The application requires the lowest possible latency for reads and must support object-level tiering. Which blob type should you use?
Block blobs support large objects (up to ~4.7 TB) and offer object-level tiering, making them suitable for this scenario.
B
Archive storage account
Why wrong: Archive storage is a tier, not a blob type. It is for infrequently accessed data and does not provide low-latency reads.
C
Page blob
Why wrong: Page blobs are designed for random read/write operations (like VHDs) and do not support tiering. They are limited to 8 TB but are not ideal for object-level tiering.
D
Append blob
Why wrong: Append blobs are optimized for append operations, not for large binary objects with low-latency reads and tiering.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Block blob
Block blobs are designed for storing large binary objects up to approximately 4.74 TB and support object-level tiering (Hot, Cool, Cold, Archive). They offer the lowest read latency among Azure blob types because they can be accessed directly via HTTP/HTTPS and are optimized for streaming and random read access. Object-level tiering allows you to change the access tier of individual blobs without moving the storage account, which meets the requirement for granular cost optimization.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Block blob
Why this is correct
Block blobs support large objects (up to ~4.7 TB) and offer object-level tiering, making them suitable for this scenario.
Related concept
Read the scenario before looking for a memorised answer.
✗
Archive storage account
Why it's wrong here
Archive storage is a tier, not a blob type. It is for infrequently accessed data and does not provide low-latency reads.
✗
Page blob
Why it's wrong here
Page blobs are designed for random read/write operations (like VHDs) and do not support tiering. They are limited to 8 TB but are not ideal for object-level tiering.
✗
Append blob
Why it's wrong here
Append blobs are optimized for append operations, not for large binary objects with low-latency reads and tiering.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse storage account tiers (Hot, Cool, Archive) with blob types, or assume Page blobs are suitable for large binary objects because of their high maximum size, overlooking that Page blobs lack object-level tiering and are designed for VHDs, not general binary storage.
Detailed technical explanation
How to think about this question
Block blobs store data as a collection of individually manageable blocks (up to 100 MB each), allowing parallel uploads and efficient reads. The Put Block and Put Block List REST API operations enable atomic updates and tiering at the blob level via the Set Blob Tier operation. In real-world scenarios, this is ideal for media files, backups, or large datasets where you need to optimize costs by moving infrequently accessed blobs to cooler tiers without affecting the storage account configuration.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop for Azure storage — This question tests Develop for Azure storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Block blob — Block blobs are designed for storing large binary objects up to approximately 4.74 TB and support object-level tiering (Hot, Cool, Cold, Archive). They offer the lowest read latency among Azure blob types because they can be accessed directly via HTTP/HTTPS and are optimized for streaming and random read access. Object-level tiering allows you to change the access tier of individual blobs without moving the storage account, which meets the requirement for granular cost optimization.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.