Courseiva

Storing Large Binary Files in Azure Blob Storage for Read-Heavy Workloads

You are designing a solution to store large binary files (up to 100 GB each) that are frequently read but rarely updated. The data must be accessible via HTTPS and support concurrent reads. Which Azure data store should you use?

Quick Answer

The answer is Azure Blob Storage, as it is the only Azure data store designed to handle large binary files up to 100 GB each while supporting frequent reads, concurrent HTTPS access, and rare updates. Azure Blob Storage can accommodate individual blobs up to 190.7 TiB and is optimized for read-heavy workloads through its block blob architecture, which allows parallel chunking and retrieval. On the DP-900 exam, this question tests your ability to match workload patterns—specifically large binary files with high read concurrency—to the correct storage service, often contrasting Blob Storage with Azure Files (limited to 4 TiB per file and better for shared drives) or Cosmos DB (built for transactional NoSQL data). A common trap is choosing Azure Files for its familiarity, but remember that blob storage is purpose-built for unstructured binary data at scale. Memory tip: think “BLOB = Big Large Object Binary,” and if it’s a massive file that’s read often but rarely changed, Blob Storage is your go-to.

⚠ Common exam trap

DP-900 often tests the storage-service selection trap: candidates confuse Azure Files (SMB/NFS shares) with Blob Storage (HTTP object store) because both 'store files', but only Blob is designed for massive unstructured objects accessed over HTTPS.

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

✓

Azure Blob Storage

Azure Blob Storage is the object store designed for massive unstructured/binary objects (block blobs up to ~190.7 TiB, single PUT up to 5 GiB, with 100 GB well within range), exposes HTTPS/REST endpoints via the blob service, and supports concurrent reads with high throughput and multiple access tiers. Its Hot tier fits the 'frequently read, rarely updated' pattern, and features like snapshots, soft delete, and RA-GRS cover durability.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Azure Files

    Why it's wrong here

    Azure Files exposes SMB and NFS shares; HTTPS access requires a REST or mounted path rather than native object retrieval, and 100 GB single-file streaming at scale is not its design target. It is tempting as a managed file share, and would suit lift-and-shift SMB workloads, not HTTPS blob delivery.

  • ✗

    Azure Cosmos DB

    Why it's wrong here

    Cosmos DB stores JSON documents and key-value items with size limits far below 100 GB per item, so it cannot hold such binary objects. It is tempting as a globally distributed, low-latency store, and would be correct for semi-structured records needing multi-region replication, not large file blobs.

  • ✗

    Azure NetApp Files

    Why it's wrong here

    Azure NetApp Files serves NFS and SMB volumes over a delegated subnet for high-performance enterprise file workloads, not HTTPS object access. It is tempting for its low-latency throughput, and would be correct for latency-sensitive databases or SAP file shares, not internet-facing blob storage.

  • ✓

    Azure Blob Storage

    Why this is correct

    Azure Blob Storage handles objects up to roughly 190.7 TiB, serves them over HTTPS, and supports many concurrent readers, meeting the 100 GB file size and access requirements. It is optimised for large unstructured binaries, unlike Azure Files or Azure Queue Storage.

Quick reference

Azure Blob Storage Tier Comparison

TierStorage CostRetrieval CostLatencyUse Case
HotHighestLowestImmediateActive data, frequent reads
CoolLowerHigherImmediateData accessed < once / month
ColdLower stillHigherImmediateData accessed < once / quarter
ArchiveLowestHighest + rehydration delayHoursLong-term compliance retention

About these practice questions

This DP-900 question is part of Courseiva's 851-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on DP-900

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You are designing a solution to store large binary files (videos) for a media company. The solution must support tiered storage to optimize costs based on access frequency. Which Azure storage option should you use?

medium
  • A.Azure Cosmos DB
  • B.Azure Files
  • ✓ C.Azure Blob Storage
  • D.Azure Disk Storage

Why C: Azure Blob Storage is the correct choice because it is designed for storing large unstructured binary data (videos, images, documents) and supports tiered storage — Hot, Cool, Cold, and Archive access tiers — to optimize costs based on access frequency. Cosmos DB is a NoSQL database, Azure Files is a managed SMB/NFS file share, and Azure Disk Storage provides block-level disks for VMs, none of which offer blob-specific tiering for large media files.

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Microsoft exam blueprint

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.