- A
SQL API for profiles and Gremlin API for graph
Correct. The SQL API provides flexible querying of JSON documents, and the Gremlin API enables graph traversal. Both can coexist in a single Cosmos DB account using separate containers.
- B
MongoDB API for profiles and SQL API for graph
Why wrong: Incorrect. The SQL API is better for JSON document querying than MongoDB API in this context, and the SQL API is not a graph API; Gremlin is needed for graph traversal.
- C
Gremlin API for both profiles and graph
Why wrong: Incorrect. While you can store JSON documents in a Gremlin container, querying by arbitrary attributes is less efficient and more complex than using the SQL API for document retrieval.
- D
Table API for profiles and Gremlin API for graph
Why wrong: Incorrect. The Table API is a key-value store, not suitable for querying flexible JSON documents with varying attributes.
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 networking application stores user profiles as JSON documents. Each profile can have different fields (e.g., education, work history, interests) depending on what the user fills in. The application also needs to traverse friend connections as a graph to recommend new friends. The development team wants to use a single Azure Cosmos DB account for both workloads. Which combination of Azure Cosmos DB APIs should they choose?
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
SQL API for profiles and Gremlin API for graph
The SQL API (formerly DocumentDB API) is optimized for storing and querying JSON documents with flexible schemas, making it ideal for user profiles with varying fields. The Gremlin API is designed specifically for graph traversal queries, which is required for recommending friends based on friend connections. Using both APIs on the same Cosmos DB account allows the application to handle both workloads efficiently within a single service.
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.
- ✓
SQL API for profiles and Gremlin API for graph
Why this is correct
Correct. The SQL API provides flexible querying of JSON documents, and the Gremlin API enables graph traversal. Both can coexist in a single Cosmos DB account using separate containers.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
MongoDB API for profiles and SQL API for graph
Why it's wrong here
Incorrect. The SQL API is better for JSON document querying than MongoDB API in this context, and the SQL API is not a graph API; Gremlin is needed for graph traversal.
- ✗
Gremlin API for both profiles and graph
Why it's wrong here
Incorrect. While you can store JSON documents in a Gremlin container, querying by arbitrary attributes is less efficient and more complex than using the SQL API for document retrieval.
- ✗
Table API for profiles and Gremlin API for graph
Why it's wrong here
Incorrect. The Table API is a key-value store, not suitable for querying flexible JSON documents with varying attributes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume the Gremlin API can handle both document and graph workloads because it stores properties as JSON-like data, but they overlook that it lacks the flexible querying and indexing capabilities of the SQL API for unstructured documents.
Detailed technical explanation
How to think about this question
Under the hood, Azure Cosmos DB uses a single multi-model database engine that supports multiple wire protocols. The SQL API uses a SQL-like query language with native JSON support and automatic indexing of all properties, which is ideal for schema-flexible documents. The Gremlin API implements the Apache TinkerPop graph traversal language, allowing efficient traversal of edges and vertices for friend recommendation algorithms like breadth-first search or PageRank. A real-world scenario is a social network that stores user profiles as JSON documents with the SQL API and uses the Gremlin API to traverse the 'friend' edges to find second-degree connections for recommendations.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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.
- →
Describe considerations for working with non-relational data on Azure — study guide chapter
Learn the concepts, then practise the questions
- →
Describe considerations for working with non-relational data on Azure practice questions
Targeted practice on this topic area only
- →
All DP-900 questions
982 questions across all exam domains
- →
Microsoft Azure Data Fundamentals DP-900 study guide
Full concept coverage aligned to exam objectives
- →
DP-900 practice test guide
How to use practice tests most effectively before exam day
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.
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.
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: SQL API for profiles and Gremlin API for graph — The SQL API (formerly DocumentDB API) is optimized for storing and querying JSON documents with flexible schemas, making it ideal for user profiles with varying fields. The Gremlin API is designed specifically for graph traversal queries, which is required for recommending friends based on friend connections. Using both APIs on the same Cosmos DB account allows the application to handle both workloads efficiently within a single service.
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 →
Last reviewed: Jun 11, 2026
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.