Question 612 of 982

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. A key principle to apply: azure Cosmos DB for NoSQL API stores data as JSON documents.. 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 application stores user posts as JSON documents in Azure Cosmos DB. Each post includes fields such as postId, userId, content, timestamp, and an array of tags. The development team wants to query posts by userId and timestamp range using a SQL-like syntax. Which Azure Cosmos DB API should they choose?

Question 1easymultiple choice
Full question →

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

B. Azure Cosmos DB for NoSQL API (Core SQL API)

The Azure Cosmos DB for NoSQL API (Core SQL API) is the correct choice because it natively supports SQL-like querying (SELECT, WHERE, ORDER BY) over JSON documents. The team's requirement to query posts by userId and timestamp range using SQL-like syntax is directly supported by this API, which treats each JSON document as an item and allows filtering on nested fields like userId and timestamp. Other APIs either lack native SQL-like syntax or are optimized for different data models (e.g., MongoDB uses a JSON-like query language, Table API uses OData, Cassandra uses CQL).

Key principle: Azure Cosmos DB for NoSQL API stores data as JSON documents.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • A. Azure Cosmos DB for MongoDB API

    Why it's wrong here

    The MongoDB API supports JSON documents and querying, but its query language is MongoDB-specific (e.g., db.posts.find()). The team prefers SQL-like syntax, so the NoSQL API is a better fit.

  • B. Azure Cosmos DB for NoSQL API (Core SQL API)

    Why this is correct

    The NoSQL API natively supports JSON documents and provides a SQL-like query language (SELECT ... WHERE ...). It can efficiently query on userId and timestamp fields, making it the optimal choice.

    Related concept

    Azure Cosmos DB for NoSQL API stores data as JSON documents.

  • C. Azure Cosmos DB for Table API

    Why it's wrong here

    The Table API is a key-value store for semi-structured data, but it does not support querying on nested JSON fields or timestamps with range filters. It is designed for simple key lookups.

  • D. Azure Cosmos DB for Apache Cassandra API

    Why it's wrong here

    The Cassandra API uses CQL (Cassandra Query Language) which is SQL-like, but it is optimized for wide-column tables, not hierarchical JSON documents. It would require flattening the JSON structure, adding complexity.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse 'SQL-like syntax' with any API that supports querying, but only the Core SQL API provides native SQL SELECT statements over JSON documents, while other APIs use different query languages (e.g., MongoDB's query operators, Cassandra's CQL) that are not SQL-like in the standard sense.

Detailed technical explanation

How to think about this question

Under the hood, the Core SQL API uses a partitioned index over JSON documents, enabling efficient range scans on timestamp when combined with a partition key like userId. A common subtlety is that without a composite index on (userId, timestamp), range queries may result in cross-partition scans, impacting performance. In real-world scenarios, teams often use the Core SQL API for social media feeds because it supports JOINs across tags arrays and server-side JavaScript stored procedures for complex aggregations.

KKey Concepts to Remember

  • Azure Cosmos DB for NoSQL API stores data as JSON documents.
  • It supports a SQL-like query language for data manipulation.
  • Automatic indexing of all properties within JSON documents is a default feature.
  • It is ideal for flexible schema and document-oriented data models.

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

Azure Cosmos DB for NoSQL API stores data as JSON documents.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Azure Cosmos DB for NoSQL API stores data as JSON documents. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Review azure Cosmos DB for NoSQL API stores data as JSON documents., then practise related DP-900 questions on the same topic to reinforce the concept.

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.

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 — Azure Cosmos DB for NoSQL API stores data as JSON documents..

What is the correct answer to this question?

The correct answer is: B. Azure Cosmos DB for NoSQL API (Core SQL API) — The Azure Cosmos DB for NoSQL API (Core SQL API) is the correct choice because it natively supports SQL-like querying (SELECT, WHERE, ORDER BY) over JSON documents. The team's requirement to query posts by userId and timestamp range using SQL-like syntax is directly supported by this API, which treats each JSON document as an item and allows filtering on nested fields like userId and timestamp. Other APIs either lack native SQL-like syntax or are optimized for different data models (e.g., MongoDB uses a JSON-like query language, Table API uses OData, Cassandra uses CQL).

What should I do if I get this DP-900 question wrong?

Review azure Cosmos DB for NoSQL API stores data as JSON documents., then practise related DP-900 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Azure Cosmos DB for NoSQL API stores data as JSON documents.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More DP-900 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.