Courseiva

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

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?

⚠ Common exam trap

Many exam-takers 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.

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

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.

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

    A key-value store, such as Redis or DynamoDB, treats the stored item as an opaque value addressed solely by a partition key. While a JSON blob could be saved as that value, the database engine does not parse its internal fields for querying, indexing, or updating. Storing social posts this way would force the application to read and rewrite entire documents to access a single nested field, which is not the flexible JSON-aware behavior described in this scenario.

  • Column-family

    Why it's wrong here

    Column-family databases like HBase or Cassandra organize data into sparse rows and column families, with each cell holding a single value. They are optimized for wide tables and high-throughput point lookups or range scans over row keys, but they do not natively model nested JSON objects; representing a post's nested tags, likes, and comments would require flattening or serializing them into column names or byte blobs. This makes them a poor fit for the document-centric JSON scenario, where nested structure should be directly queryable.

  • Document

    Why this is correct

    A document database, such as Azure Cosmos DB, stores each social media post as an independent JSON document and can index individual fields and nested properties for queries. The schema is flexible, so different posts can contain different fields without migrations, matching the naturally evolving JSON structure of user-generated content. This native JSON support with dot-notation field access and rich indexing is exactly why this scenario points to a document data store.

  • Graph

    Why it's wrong here

    Graph databases like Neo4j model the world as nodes and edges, optimizing queries that traverse relationships between entities (for example, who follows whom). The scenario focuses on persisting arbitrary JSON post documents with varying fields, not on representing or querying the connection graph between users. Adding a graph layer would impose a predefined schema for relationships and complicate straightforward content storage, so it is not the right primary model here.

About these practice questions

Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.