- A
Azure Table Storage
Why wrong: Azure Table Storage is a NoSQL key-value store that does not support document models with nested attributes easily. It also does not provide global distribution with low-latency guarantees across regions.
- B
Azure Blob Storage
Why wrong: Blob Storage stores unstructured binary or text data, not designed for querying individual documents by key. It is not a document database.
- C
Azure Cosmos DB
Azure Cosmos DB is a globally distributed NoSQL database that supports flexible schemas and document models via its SQL API. It offers low-latency reads and writes with guarantees of <10 ms for reads and can be replicated across Azure regions.
- D
Azure SQL Database
Why wrong: Azure SQL Database is a relational database requiring a fixed schema. It does not natively support flexible document schemas without using JSON functions, but it is not designed as a NoSQL document store for high-throughput read-heavy workloads with global distribution.
Quick Answer
Azure Cosmos DB is the correct choice because it is a globally distributed, multi-model NoSQL database that natively supports JSON documents with a flexible schema, making it ideal for a product catalog where different categories have varying attributes. Its automatic indexing enables single-digit-millisecond latency for read-heavy lookups by product ID, while turnkey global distribution allows you to replicate data across Azure regions to serve customers worldwide with low latency. On the Microsoft Azure Data Fundamentals DP-900 exam, this question tests your understanding of when to choose Cosmos DB over other Azure data stores like SQL Database or Table Storage—a common trap is selecting Azure SQL Database for structured data, but remember that Cosmos DB is the go-to for globally distributed, schema-flexible JSON workloads. A helpful memory tip: think “Cosmos = global + flexible JSON + fast reads,” and recall that if the scenario mentions “millions of products” and “worldwide low latency,” Cosmos DB is almost always the answer.
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
This DP-900 practice question tests your understanding of describe considerations for working with non-relational data on azure. 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.
A company stores JSON documents for a product catalog. Each document has a flexible schema because different product categories have different attributes. The catalog is read-heavy and requires low-latency lookups by product ID. The company expects to handle millions of products and needs to serve customers globally with low latency. Which Azure NoSQL data store should they choose?
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 is a globally distributed, multi-model NoSQL database that natively supports JSON documents with flexible schemas, provides single-digit-millisecond latency for read-heavy workloads via automatic indexing, and offers turnkey global distribution across Azure regions to serve customers worldwide with low latency.
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
Azure Table Storage is a NoSQL key-value store that does not support document models with nested attributes easily. It also does not provide global distribution with low-latency guarantees across regions.
- ✗
Azure Blob Storage
Why it's wrong here
Blob Storage stores unstructured binary or text data, not designed for querying individual documents by key. It is not a document database.
- ✓
Azure Cosmos DB
Why this is correct
Azure Cosmos DB is a globally distributed NoSQL database that supports flexible schemas and document models via its SQL API. It offers low-latency reads and writes with guarantees of <10 ms for reads and can be replicated across Azure regions.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Azure SQL Database
Why it's wrong here
Azure SQL Database is a relational database requiring a fixed schema. It does not natively support flexible document schemas without using JSON functions, but it is not designed as a NoSQL document store for high-throughput read-heavy workloads with global distribution.
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 a document database, overlooking that Table Storage does not support flexible JSON schemas or global distribution with low-latency reads, while Cosmos DB is explicitly designed for these requirements.
Detailed technical explanation
How to think about this question
Azure Cosmos DB uses a schema-agnostic indexing engine that automatically indexes every property in a JSON document without requiring schema definitions, enabling efficient point reads by partition key (e.g., product ID) with predictable latency. Its global distribution is powered by active-active replication across any number of Azure regions, with multi-homing APIs that route requests to the nearest region, ensuring sub-10-ms reads at the 99th percentile. In a real-world scenario, a global e-commerce platform storing millions of product variants with differing attributes (e.g., electronics vs. clothing) would leverage Cosmos DB's automatic indexing and turnkey multi-region writes to maintain low-latency lookups worldwide.
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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Describe considerations for working with non-relational data on Azure — study guide chapter
Learn the concepts, then practise the questions
- →
Describe considerations for working with non-relational data on Azure practice questions
Targeted practice on this topic area only
- →
All DP-900 questions
982 questions across all exam domains
- →
Microsoft Azure Data Fundamentals DP-900 study guide
Full concept coverage aligned to exam objectives
- →
DP-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DP-900 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Describe core data concepts practice questions
Practise DP-900 questions linked to Describe core data concepts.
Describe an analytics workload on Azure practice questions
Practise DP-900 questions linked to Describe an analytics workload on Azure.
Identify considerations for relational data on Azure practice questions
Practise DP-900 questions linked to Identify considerations for relational data on Azure.
Describe considerations for working with non-relational data on Azure practice questions
Practise DP-900 questions linked to Describe considerations for working with non-relational data on Azure.
DP-900 fundamentals practice questions
Practise DP-900 questions linked to DP-900 fundamentals.
DP-900 scenario practice questions
Practise DP-900 questions linked to DP-900 scenario.
DP-900 troubleshooting practice questions
Practise DP-900 questions linked to DP-900 troubleshooting.
Practice this exam
Start a free DP-900 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DP-900 question test?
Describe considerations for working with non-relational data on Azure — This question tests Describe considerations for working with non-relational data on Azure — 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 is a globally distributed, multi-model NoSQL database that natively supports JSON documents with flexible schemas, provides single-digit-millisecond latency for read-heavy workloads via automatic indexing, and offers turnkey global distribution across Azure regions to serve customers worldwide with low latency.
What should I do if I get this DP-900 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 →
Same concept, more angles
5 more ways 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. A retail company is designing a product catalog for its e-commerce website. Each product has a unique ProductID, a name, a price, and a variable number of attributes (e.g., size, color, weight) that differ across product categories. The application requires ability to read a product's details by ProductID with single-digit millisecond latency from any Azure region globally. The schema must be flexible to accommodate new attributes without schema changes. Which Azure data store should the company choose?
medium- ✓ A.Azure Cosmos DB using the NoSQL API
- B.Azure Table Storage
- C.Azure SQL Database
- D.Azure Blob Storage
Why A: Azure Cosmos DB with the NoSQL API is correct because it provides a fully managed, globally distributed NoSQL database that supports flexible schemas (allowing variable product attributes without schema changes) and guarantees single-digit millisecond read latency at any scale from any Azure region via its multi-region write and read replicas. The unique ProductID serves as a natural partition key, enabling efficient point reads with consistent low latency.
Variation 2. A retail company stores product catalog data as JSON documents. Each product has a different set of attributes depending on its category (e.g., electronics have 'voltage', clothing has 'size'). The application needs to query products by category and price range efficiently. Which Azure data store is most appropriate for this workload?
easy- ✓ A.Azure Cosmos DB
- B.Azure SQL Database
- C.Azure Blob Storage
- D.Azure Table Storage
Why A: Azure Cosmos DB is the most appropriate choice because it natively supports JSON documents with flexible schemas, enabling each product to have a different set of attributes per category. Its indexing policies can be configured to efficiently support queries filtering by category and price range, and it offers low-latency, high-throughput access ideal for retail catalog workloads.
Variation 3. A retail company plans to store product catalog data that includes product ID, name, description, price, and a varying set of attributes (e.g., size, color, material). The application requires low-latency reads and writes, global distribution, and the ability to handle schema flexibility. Which Azure data store is best suited for this workload?
easy- A.Azure SQL Database
- ✓ B.Azure Cosmos DB
- C.Azure Table Storage
- D.Azure Blob Storage
Why B: Azure Cosmos DB is the best choice because it provides low-latency reads and writes (single-digit milliseconds at the 99th percentile), global distribution with multi-region writes, and automatic schema flexibility through its document model. It supports varying product attributes (e.g., size, color, material) without requiring schema changes, and its turnkey global distribution ensures data is replicated across regions for fast access.
Variation 4. A retail company wants to store product catalog data in a non-relational format. The data includes product ID, name, description, price, and an array of tags. The data is frequently updated and must support low-latency reads and writes at global scale. Which Azure service should they use?
easy- ✓ A.Azure Cosmos DB
- B.Azure Table Storage
- C.Azure Blob Storage
- D.Azure Cache for Redis
Why A: Option B is correct because Azure Cosmos DB is a globally distributed NoSQL database that supports low-latency reads/writes and can store JSON documents with arrays. Option A is wrong because Azure Blob Storage is for unstructured blob data, not transactional updates. Option C is wrong because Azure Table Storage is a key-value store but does not support complex queries or global distribution as well as Cosmos DB. Option D is wrong because Azure Cache for Redis is an in-memory cache, not a durable data store.
Variation 5. You need to store a collection of JSON documents that contain user profile data. The data is frequently queried by user ID and by email address. The solution must support indexing on multiple fields and provide low-latency queries. Which Azure service should you use?
easy- A.Azure Table Storage
- B.Azure Cache for Redis
- ✓ C.Azure Cosmos DB
- D.Azure Blob Storage
Why C: Option C is correct because Azure Cosmos DB is a NoSQL database that supports indexing on multiple fields and provides low-latency queries on JSON documents. Option A is wrong because Azure Blob Storage does not support indexing on document fields. Option B is wrong because Azure Table Storage is a key-value store with limited indexing. Option D is wrong because Azure Cache for Redis is an in-memory cache, not a durable indexed store.
Last reviewed: Jun 11, 2026
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.
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.