The answer is Document data model. This is correct because Azure Cosmos DB’s document data model is built for semi-structured, schema-agnostic data stored as JSON, where each document can have a unique set of fields and nested objects—exactly matching the scenario of user posts with varying structures. On the Microsoft Azure Data Fundamentals DP-900 exam, this question tests your understanding of how Cosmos DB’s core data models (document, column-family, graph, and key-value) map to real-world use cases. A common trap is confusing the document model with the relational model, but remember: if the data is JSON with flexible schemas and nested objects, it’s a document model. For a quick memory tip, think “JSON = Document” and recall that the SQL API and MongoDB API both use this model to handle varying fields without requiring a predefined schema.
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 social media company stores user posts as JSON documents in Azure Cosmos DB. Each post may have a different number of fields and nested objects. Which type of data model does this represent?
Why wrong: Incorrect. Key-value stores treat data as an opaque value accessed by a key. Here, the content is structured JSON with nested fields, not an opaque blob.
B
Column-family
Why wrong: Incorrect. Column-family databases (e.g., HBase) store data in rows with varying columns per row, but they do not natively support nested JSON objects as documents do.
C
Document
Correct. Document databases like Azure Cosmos DB store each record as a self-contained document (JSON) with a flexible schema, allowing varying fields and nesting.
D
Graph
Why wrong: Incorrect. Graph databases focus on storing nodes (entities) and edges (relationships). The scenario describes posts with arbitrary structure, not a graph of relationships.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Document
The scenario describes user posts stored as JSON documents with varying fields and nested objects. Azure Cosmos DB's Document data model (using the SQL API or MongoDB API) is designed for semi-structured, schema-agnostic data where each document can have a different structure, making it the correct choice.
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.
✗
Key-value
Why it's wrong here
Incorrect. Key-value stores treat data as an opaque value accessed by a key. Here, the content is structured JSON with nested fields, not an opaque blob.
✗
Column-family
Why it's wrong here
Incorrect. Column-family databases (e.g., HBase) store data in rows with varying columns per row, but they do not natively support nested JSON objects as documents do.
✓
Document
Why this is correct
Correct. Document databases like Azure Cosmos DB store each record as a self-contained document (JSON) with a flexible schema, allowing varying fields and nesting.
Related concept
Read the scenario before looking for a memorised answer.
✗
Graph
Why it's wrong here
Incorrect. Graph databases focus on storing nodes (entities) and edges (relationships). The scenario describes posts with arbitrary structure, not a graph of relationships.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse the document model with key-value because both handle unstructured data, but key-value stores lack the ability to query on nested fields or perform rich queries like those supported by Cosmos DB's SQL API.
Trap categories for this question
Scenario analysis trap
Incorrect. Graph databases focus on storing nodes (entities) and edges (relationships). The scenario describes posts with arbitrary structure, not a graph of relationships.
Detailed technical explanation
How to think about this question
Under the hood, Azure Cosmos DB's document model uses a schema-agnostic indexing engine that automatically indexes all properties within JSON documents, enabling efficient queries on any field without manual index management. A real-world scenario where this matters is when posts include optional metadata like location, tags, or embedded media, which can be added or removed per document without schema migrations. The document model also supports atomic transactions within a single document (e.g., updating a post's content and nested comments in one operation) via stored procedures or the transactional batch API.
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-900 question in full detail.
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: Document — The scenario describes user posts stored as JSON documents with varying fields and nested objects. Azure Cosmos DB's Document data model (using the SQL API or MongoDB API) is designed for semi-structured, schema-agnostic data where each document can have a different structure, making it the correct choice.
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 →
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-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.