Azure Cosmos DB is the correct choice because it is a globally distributed JSON document database that offers native flexible schema support and low-latency queries. This service stores semi-structured JSON data directly, and its schema-agnostic indexing engine automatically adapts as your data schema changes over time, eliminating the need for manual schema migrations. On the DP-203 exam, this scenario tests your understanding of when to choose Cosmos DB over alternatives like Azure SQL Database or Azure Table Storage, which lack native JSON flexibility or global distribution. A common trap is selecting Azure SQL Database for its JSON functions, but remember that Cosmos DB is purpose-built for globally distributed, low-latency workloads with dynamic schemas. Memory tip: think “Cosmos = JSON + global + flexible” — if the question mentions changing schemas and worldwide access, Cosmos DB is your answer.
DP-203 Design and implement data storage Practice Question
This DP-203 practice question tests your understanding of design and implement data 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 need to store semi-structured JSON data from a web application. The data schema may change over time. The solution must support low-latency queries and be globally distributed. Which Azure data service should you use?
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 semi-structured JSON documents with a flexible schema, offers single-digit-millisecond latency for queries, and provides global distribution with turnkey multi-region replication. Its API for MongoDB or SQL API allows direct ingestion of JSON data, and its schema-agnostic indexing adapts automatically to schema changes over time.
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.
✗
Azure Table Storage
Why it's wrong here
Table Storage is a NoSQL key-value store but lacks the global distribution and low-latency guarantees of Cosmos DB.
✓
Azure Cosmos DB
Why this is correct
Cosmos DB natively supports JSON documents with automatic indexing and global distribution.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Data Lake Storage Gen2
Why it's wrong here
Data Lake Storage is for big data analytics, not low-latency operational queries.
✗
Azure SQL Database
Why it's wrong here
Azure SQL Database requires a defined schema, not ideal for evolving JSON data.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Azure Table Storage's key-value model with document storage, overlooking that it lacks native JSON support and global low-latency query capabilities, while Azure Cosmos DB is specifically designed for these requirements.
Detailed technical explanation
How to think about this question
Cosmos DB uses a write-optimized, log-structured index (LSM-tree) that automatically indexes every property in a JSON document without requiring schema definitions, enabling efficient queries on evolving schemas. Its global distribution is achieved through multi-master replication with multiple consistency levels (e.g., eventual, session, bounded staleness) to balance latency and data freshness. In a real-world scenario, a web application logging user events with varying fields (e.g., new metadata) can query instantly across regions without schema changes or downtime.
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 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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Azure Cosmos DB — Azure Cosmos DB is the correct choice because it natively supports semi-structured JSON documents with a flexible schema, offers single-digit-millisecond latency for queries, and provides global distribution with turnkey multi-region replication. Its API for MongoDB or SQL API allows direct ingestion of JSON data, and its schema-agnostic indexing adapts automatically to schema changes over time.
What should I do if I get this DP-203 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 →
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 need to store semi-structured JSON data from a web application that requires low-latency reads and writes at a global scale. The data must be indexed automatically and support SQL-like queries. Which Azure data store should you use?
easy
A.Azure SQL Database
B.Azure Blob Storage
✓ C.Azure Cosmos DB (NoSQL API)
D.Azure Table Storage
Why C: Azure Cosmos DB with the NoSQL API is the correct choice because it natively stores semi-structured JSON documents, provides automatic indexing of all properties, supports SQL-like queries via its query engine, and offers low-latency reads and writes at global scale through multi-region replication and configurable consistency levels. This combination directly matches the requirements for a globally distributed web application needing fast, queryable JSON storage.
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 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.
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.