Question 527 of 982

Describe considerations for working with non-relational data on Azure →mediumMultiple ChoiceObjective-mapped

Quick Answer

The Core (SQL) API is the correct choice because it natively supports SQL-like queries for fast point reads by playerId and range queries on score, while also enabling Azure Cosmos DB global distribution with multi-region writes for low latency worldwide. This API directly handles the document model with arrays like inventory, making it ideal for player profiles and game state. On the DP-900 exam, this scenario tests your understanding that the Core API is the default, multi-model option for SQL-based querying and global distribution—a common trap is confusing it with the Table API (which lacks SQL querying) or MongoDB API (which uses a different syntax). Remember: if the requirement says "SQL-like queries" and "multi-region writes," think Core API. A simple memory tip: "SQL for queries, Core for global writes."

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 mobile game company stores player profiles and game state in Azure Cosmos DB. Each document contains playerId, level, score, inventory (an array of items), and lastLogin. The application requires fast point reads by playerId, queries to find all players within a specific score range, and global distribution with multi-region writes for low latency worldwide. They also want to use a familiar SQL-like query language. Which Azure Cosmos DB API should they choose?

Question 1mediummultiple choice

Full question →

A
Core (SQL) API
Correct. The Core (SQL) API provides a SQL-like query language, supports point reads and range queries, and enables multi-region writes for global distribution.
B
MongoDB API
Why wrong: The MongoDB API uses MongoDB's query language (not SQL) and supports multi-region writes, but the team prefers a SQL-like syntax, so it is not the best fit.
C
Cassandra API
Why wrong: The Cassandra API uses CQL, which resembles SQL, but the primary querying pattern is by partition key. Range queries on non-partition key fields like score may require careful modelling and are less efficient than the Core (SQL) API for arbitrary queries.
D
Gremlin API
Why wrong: The Gremlin API is designed for graph data and graph traversals, not for document-based queries with SQL-like syntax. It would not be appropriate for player profiles and scores.

Full breakdown with real-world context →

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

✓

Core (SQL) API

The Core (SQL) API is the correct choice because it provides native support for SQL-like queries, enabling the required point reads by playerId and range queries on score. It also offers multi-region writes for global distribution with low latency, which aligns with the application's need for worldwide player access. The document model with arrays (inventory) is directly supported, making it ideal for storing player profiles and game state.

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.

✓
Core (SQL) API
Why this is correct
Correct. The Core (SQL) API provides a SQL-like query language, supports point reads and range queries, and enables multi-region writes for global distribution.
Related concept
Read the scenario before looking for a memorised answer.
✗
MongoDB API
Why it's wrong here
The MongoDB API uses MongoDB's query language (not SQL) and supports multi-region writes, but the team prefers a SQL-like syntax, so it is not the best fit.
✗
Cassandra API
Why it's wrong here
The Cassandra API uses CQL, which resembles SQL, but the primary querying pattern is by partition key. Range queries on non-partition key fields like score may require careful modelling and are less efficient than the Core (SQL) API for arbitrary queries.
✗
Gremlin API
Why it's wrong here
The Gremlin API is designed for graph data and graph traversals, not for document-based queries with SQL-like syntax. It would not be appropriate for player profiles and scores.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse the MongoDB API's use of a familiar query language (MongoDB's own) with SQL-like syntax, or assume that any NoSQL API can handle range queries equally, but the Core (SQL) API is the only one that provides native SQL-like querying with automatic indexing for such patterns.

Detailed technical explanation

How to think about this question

Under the hood, the Core (SQL) API uses a native JSON document store with automatic indexing of all properties by default, which enables efficient range queries on score without requiring manual index management. For multi-region writes, it leverages a multi-master replication protocol that provides conflict resolution (e.g., last-writer-wins) to handle concurrent updates across regions, ensuring low-latency writes globally. A subtle behavior is that the SQL-like query language supports JOINs and subqueries on arrays like inventory, which is not available in the MongoDB API without aggregation pipelines.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

DP-900 practice-test guide →Study guide →Browse all practice tests

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: Core (SQL) API — The Core (SQL) API is the correct choice because it provides native support for SQL-like queries, enabling the required point reads by playerId and range queries on score. It also offers multi-region writes for global distribution with low latency, which aligns with the application's need for worldwide player access. The document model with arrays (inventory) is directly supported, making it ideal for storing player profiles and game state.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 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 social media company stores user-generated posts as JSON documents. Each post contains fields such as postId, userId, timestamp, and content. The application needs to query posts by userId and timestamp ranges with low latency, and also perform SQL-like queries across all posts. The data volume is growing rapidly and must scale globally. Which Azure data store should the company use?

medium

A.A) Azure Table Storage
✓ B.B) Azure Cosmos DB SQL API
C.C) Azure Blob Storage
D.D) Azure Cache for Redis

Why B: Azure Cosmos DB SQL API is the correct choice because it provides native support for querying JSON documents with low-latency, including indexed queries on fields like userId and timestamp. Its global distribution capability ensures data can be replicated across multiple Azure regions for low-latency access worldwide, while its SQL API allows SQL-like queries across all posts, meeting both requirements.

Keep practising

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…

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.