AZ-204 Develop for Azure storage Practice Question
You are developing a solution that needs to store and retrieve JSON documents with a flexible schema. The data is accessed via REST API and requires low-latency reads. Which Azure Storage service should you use?
⚠ Common exam trap
It's easy for candidates to confuse Azure Blob Storage's ability to store JSON files (as blobs) with the ability to efficiently query and retrieve individual documents with low latency, overlooking the fact that Blob Storage lacks native indexing and querying capabilities for JSON content.
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 Cosmos DB
Azure Cosmos DB is the correct choice because it natively supports storing and querying JSON documents with a flexible schema via its SQL API, and it guarantees single-digit millisecond read latencies at the 99th percentile, which meets the low-latency requirement. Unlike other Azure storage services, Cosmos DB is a fully managed NoSQL database designed for REST API access with automatic indexing of all JSON properties.
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 Blob Storage
Why it's wrong here
Azure Blob Storage is optimized for storing large amounts of unstructured data, such as binary files, images, or log files, as individual blobs. While it can store JSON documents as text blobs, it does not provide native indexing or querying capabilities for the content *within* those JSON documents. Retrieving specific data points would require downloading the entire blob and parsing it client-side, which is inefficient for document-based queries.
- ✓
Azure Cosmos DB
Why this is correct
Azure Cosmos DB is a globally distributed, multi-model database service that natively supports document data, including JSON, with a flexible schema. It automatically indexes all properties within documents, enabling powerful SQL-like query capabilities over JSON data with low-latency access. This makes it an excellent choice for solutions requiring dynamic data structures and efficient querying of document content.
- ✗
Azure Table Storage
Why it's wrong here
Azure Table Storage is a NoSQL key-value store designed for large sets of structured, non-relational data, primarily accessed via PartitionKey and RowKey. Although it can store entities with varying properties, it lacks the rich indexing and query capabilities over arbitrary JSON document fields that a document database provides. It is not optimized for querying complex, nested JSON structures or for flexible schema evolution beyond simple property additions.
- ✗
Azure Files
Why it's wrong here
Azure Files provides fully managed file shares in the cloud, accessible via the Server Message Block (SMB) protocol or Network File System (NFS). It is primarily used for traditional file share scenarios, such as lift-and-shift applications or shared storage for virtual machines. Azure Files does not offer any database-like indexing or querying capabilities for content within files, including JSON documents, making it unsuitable for storing and retrieving data based on document content.
Go deeper
Related to this question
About these practice questions
This AZ-204 question is part of Courseiva's 881-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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.