Quick Answer
The answer is a block blob staged block upload with commit. This approach is correct because it breaks large thumbnail metadata into smaller, independent blocks that can be individually retried if a network failure occurs, using the Put Block and Put Block List REST APIs to commit only the successfully uploaded blocks. On the Microsoft Azure Developer Associate AZ-204 exam, this scenario tests your understanding of reliable uploads to Blob Storage over unstable networks, often appearing in questions about handling large files with intermittent connectivity. A common trap is choosing a simple synchronous upload, which fails entirely on a single interruption, whereas staged block uploads provide fine-grained error recovery. Remember the memory tip: “Block by block, commit the lot” — each block is a retryable unit, and only the complete list gets committed.
This AZ-204 practice question tests your understanding of develop for azure storage. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
An application needs to upload large thumbnail metadata to Blob Storage reliably over unstable networks. Which upload approach should be used?
Block blob staged block upload with commit
Staging blocks supports resumable, parallel uploads for large block blobs.
Page blob only
Why wrong: Page blobs are designed for random read/write scenarios such as disks.
Append blob only
Why wrong: Append blobs are optimized for append operations such as logs, not general large file block upload.
Table Storage batch operation
Why wrong: Table batches apply to entity operations, not blob upload.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Block blob staged block upload with commit
Block blob staged block upload with commit is the correct approach because it allows uploading large thumbnails in smaller, independent blocks that can be retried individually if a network failure occurs. This method uses the Put Block and Put Block List REST APIs, enabling reliable uploads over unstable networks by committing only successfully uploaded blocks. It is specifically designed for large files and provides fine-grained control over upload progress and error recovery.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Block blob staged block upload with commit
Why this is correct
Staging blocks supports resumable, parallel uploads for large block blobs.
Related concept
Read the scenario before looking for a memorised answer.
Page blob only
Why it's wrong here
Page blobs are designed for random read/write scenarios such as disks.
Append blob only
Why it's wrong here
Append blobs are optimized for append operations such as logs, not general large file block upload.
Table Storage batch operation
Why it's wrong here
Table batches apply to entity operations, not blob upload.
Common exam traps
The trap here is that candidates may confuse blob types (block, page, append) and choose page blobs due to their 'reliability' reputation for VHDs, but fail to recognize that block blobs are the correct choice for large file uploads with retry logic over unstable networks.
Trap categories for this question
Scenario analysis trap
Page blobs are designed for random read/write scenarios such as disks.
Detailed technical explanation
Under the hood, the staged block upload approach uses the Put Block REST API to upload blocks (each up to 100 MB) with a unique block ID, and then the Put Block List API commits the blocks in order by specifying their IDs. This allows the client to retry only failed blocks without re-uploading the entire blob, leveraging the block blob's support for up to 50,000 blocks and a maximum blob size of ~4.75 TB. In real-world scenarios, this is critical for mobile apps uploading large thumbnails over cellular networks where packet loss is common.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Develop for Azure storage — study guide chapter
Learn the concepts, then practise the questions
Develop for Azure storage practice questions
Targeted practice on this topic area only
All AZ-204 questions
997 questions across all exam domains
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-204 questions linked to Develop Azure compute solutions.
Practise AZ-204 questions linked to Develop for Azure storage.
Practise AZ-204 questions linked to Implement Azure security.
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
Practise AZ-204 questions linked to AZ-204 fundamentals.
Practise AZ-204 questions linked to AZ-204 scenario.
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Develop for Azure storage — This question tests Develop for Azure storage — Read the scenario before looking for a memorised answer..
The correct answer is: Block blob staged block upload with commit — Block blob staged block upload with commit is the correct approach because it allows uploading large thumbnails in smaller, independent blocks that can be retried individually if a network failure occurs. This method uses the Put Block and Put Block List REST APIs, enabling reliable uploads over unstable networks by committing only successfully uploaded blocks. It is specifically designed for large files and provides fine-grained control over upload progress and error recovery.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 11, 2026
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.