Question 823 of 982

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

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 global gaming company develops a multiplayer game. Player profile data (username, email, preferences) is stored as simple key-value pairs and must be accessible with single-digit millisecond latency from any region. Game session logs are stored as JSON documents with varying fields (session ID, player actions, timestamps) and must be queryable by player ID and timestamp range using SQL-like syntax. The company wants to use a single Azure database service for both workloads. Which combination of Azure Cosmos DB APIs should they choose?

Question 1hardmultiple choice

Read the full NAT/PAT explanation →

A
Table API for profiles and SQL API for logs
The Table API provides key-value storage with single-digit millisecond latencies, ideal for player profiles. The SQL API supports JSON documents and full SQL query syntax, perfect for querying session logs by player ID and timestamp.
B
SQL API for both profiles and logs
Why wrong: While the SQL API can store both, it is not optimized for simple key-value lookups with the same performance as the Table API. Using the SQL API for profiles would still work but would be less efficient and more costly for simple reads.
C
MongoDB API for profiles and Cassandra API for logs
Why wrong: The MongoDB API is document-based and can handle JSON, but it is not as simple as the Table API for key-value. The Cassandra API is column-family and does not natively support SQL-like querying on JSON documents; it is designed for wide-column workloads.
D
Table API for both profiles and logs
Why wrong: The Table API only supports simple key-value lookups and does not support querying nested JSON properties or SQL-like syntax. It cannot handle the querying requirements for session logs.

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

✓

Table API for profiles and SQL API for logs

Option A is correct because the Table API provides a simple key-value store ideal for low-latency profile lookups, while the SQL API supports querying JSON documents with SQL-like syntax, enabling efficient queries on game session logs by player ID and timestamp range. This combination meets both workloads within a single Azure Cosmos DB account.

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.

✓
Table API for profiles and SQL API for logs
Why this is correct
The Table API provides key-value storage with single-digit millisecond latencies, ideal for player profiles. The SQL API supports JSON documents and full SQL query syntax, perfect for querying session logs by player ID and timestamp.
Related concept
Read the scenario before looking for a memorised answer.
✗
SQL API for both profiles and logs
Why it's wrong here
While the SQL API can store both, it is not optimized for simple key-value lookups with the same performance as the Table API. Using the SQL API for profiles would still work but would be less efficient and more costly for simple reads.
✗
MongoDB API for profiles and Cassandra API for logs
Why it's wrong here
The MongoDB API is document-based and can handle JSON, but it is not as simple as the Table API for key-value. The Cassandra API is column-family and does not natively support SQL-like querying on JSON documents; it is designed for wide-column workloads.
✗
Table API for both profiles and logs
Why it's wrong here
The Table API only supports simple key-value lookups and does not support querying nested JSON properties or SQL-like syntax. It cannot handle the querying requirements for session logs.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume a single API must serve both workloads, overlooking Azure Cosmos DB's ability to host multiple APIs in one account, and they may incorrectly choose the SQL API for both because it is the most versatile, ignoring the cost and simplicity benefits of the Table API for key-value data.

Detailed technical explanation

How to think about this question

Azure Cosmos DB's multi-API support allows a single database account to host multiple APIs via different endpoints, but each container is bound to a specific API. The Table API uses a fixed schema with PartitionKey and RowKey, achieving single-digit millisecond latency through automatic indexing. The SQL API (now called Core API) natively supports querying JSON documents with the SQL grammar, including WHERE clauses on nested fields like player ID and timestamp, leveraging a hash-based index for range scans.

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: Table API for profiles and SQL API for logs — Option A is correct because the Table API provides a simple key-value store ideal for low-latency profile lookups, while the SQL API supports querying JSON documents with SQL-like syntax, enabling efficient queries on game session logs by player ID and timestamp range. This combination meets both workloads within a single Azure Cosmos DB account.

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

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.