- A
A. Azure Table Storage
Why wrong: Azure Table Storage is a NoSQL key-value store, but it does not support SQL-like queries on document attributes or flexible JSON schemas as well as Cosmos DB.
- B
B. Azure Cosmos DB Core (SQL) API
Azure Cosmos DB with the Core (SQL) API natively stores JSON documents with varying schemas, provides low-latency point reads, and supports advanced SQL-like queries on any attribute.
- C
C. Azure Blob Storage
Why wrong: Azure Blob Storage is designed for storing large unstructured objects like files or images, not for querying individual document fields with SQL.
- D
D. Azure Database for PostgreSQL
Why wrong: Azure Database for PostgreSQL is a relational database that requires a predefined schema; it is not optimized for storing and querying 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 gaming company stores player profiles as JSON documents. Each profile can have different attributes; for example, some profiles include an 'achievements' field while others include a 'purchaseHistory' field. The application must retrieve profiles by player ID with single-digit-millisecond latency and also support SQL-like queries on any attribute. Which Azure data store should the company use?
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 Core (SQL) API
Azure Cosmos DB Core (SQL) API is the correct choice because it natively stores JSON documents with flexible schemas, supports indexing on any attribute for SQL-like queries, and guarantees single-digit-millisecond latency for point reads by player ID. This meets the requirement for both fast key-based lookups and ad-hoc querying across varying profile attributes.
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.
- ✗
A. Azure Table Storage
Why it's wrong here
Azure Table Storage is a NoSQL key-value store, but it does not support SQL-like queries on document attributes or flexible JSON schemas as well as Cosmos DB.
- ✓
B. Azure Cosmos DB Core (SQL) API
Why this is correct
Azure Cosmos DB with the Core (SQL) API natively stores JSON documents with varying schemas, provides low-latency point reads, and supports advanced SQL-like queries on any attribute.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
C. Azure Blob Storage
Why it's wrong here
Azure Blob Storage is designed for storing large unstructured objects like files or images, not for querying individual document fields with SQL.
- ✗
D. Azure Database for PostgreSQL
Why it's wrong here
Azure Database for PostgreSQL is a relational database that requires a predefined schema; it is not optimized for storing and querying documents with varying attributes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse Azure Table Storage's key-value capabilities with the need for flexible schema and SQL-like queries, overlooking that Table Storage does not support querying arbitrary attributes or guarantee single-digit-millisecond latency for such queries.
Detailed technical explanation
How to think about this question
Under the hood, Cosmos DB uses a write-optimized, index-anywhere architecture where every attribute in a JSON document is automatically indexed by default, enabling efficient SQL-like queries via the Core (SQL) API. The single-digit-millisecond latency for point reads is achieved through a combination of SSD-backed storage, automatic indexing, and a globally distributed, multi-master replication model. In a real-world scenario, a gaming company might have millions of player profiles with different fields, and Cosmos DB's schema-agnostic indexing allows querying 'achievements' or 'purchaseHistory' without predefining a schema, while still maintaining low latency.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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: B. Azure Cosmos DB Core (SQL) API — Azure Cosmos DB Core (SQL) API is the correct choice because it natively stores JSON documents with flexible schemas, supports indexing on any attribute for SQL-like queries, and guarantees single-digit-millisecond latency for point reads by player ID. This meets the requirement for both fast key-based lookups and ad-hoc querying across varying profile attributes.
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.