Question 264 of 982

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

Quick Answer

Azure Cosmos DB is the correct choice because it is purpose-built for globally distributed, low-latency, schema-agnostic data, exactly matching the startup’s need to read player profiles by PlayerID in under 10 milliseconds from anywhere in the world. Its multi-model, schema-agnostic design allows each player profile to have varying attributes like a nickname or avatar URL without requiring a fixed table structure, while its turnkey global distribution ensures that point reads—simple lookups by a single key—achieve single-digit-millisecond latency from any Azure region. On the DP-900 exam, this scenario tests your ability to match workload characteristics to Azure data services: Cosmos DB is the go-to for globally distributed, non-relational data that demands fast, key-based reads and flexible schemas, whereas Azure SQL Database or SQL Managed Instance would be traps for relational, join-heavy workloads. A common memory tip is to think “Cosmos for cosmos-wide, low-latency, schema-free reads”—if the data is non-relational, needs global scale, and requires fast point lookups, Cosmos DB is your answer.

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 gaming startup needs to store player profiles that can have varying attributes (e.g., some players have a 'nickname', others have 'avatar URL'). The application must read a player's profile by PlayerID with very low latency (under 10 ms) from any location worldwide. The data does not require complex queries or joins. Which Azure data store should they choose?

Question 1easymultiple choice

Full question →

A
Azure SQL Database
Why wrong: Azure SQL Database is a relational database that requires a fixed schema, making it less suitable for varying attributes. While it can be globally distributed via failover groups, it does not guarantee the same low latency for point reads as Cosmos DB.
B
Azure Cosmos DB
Azure Cosmos DB is a globally distributed NoSQL database that supports flexible schemas and offers low-latency reads (under 10 ms) at any scale. It is the best fit for this scenario.
C
Azure Table Storage
Why wrong: Azure Table Storage is a key-value store that supports flexible schemas, but it is not globally distributed by default and does not provide the same low-latency guarantees as Cosmos DB, especially across regions.
D
Azure Blob Storage
Why wrong: Azure Blob Storage is for storing unstructured data such as documents, images, and videos. It does not provide low-latency point reads for individual records or support flexible schemas for application data.

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

✓

Azure Cosmos DB

Azure Cosmos DB is the correct choice because it is a globally distributed, multi-model database service that guarantees single-digit-millisecond read latencies (under 10 ms) at any scale from any Azure region. Its schema-agnostic nature allows storing player profiles with varying attributes (e.g., nickname, avatar URL) without requiring a fixed schema, and it supports point reads by PlayerID with a consistency model that can be tuned for performance. This directly matches the requirements of low-latency global reads and flexible, non-relational data.

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.

✗
Azure SQL Database
Why it's wrong here
Azure SQL Database is a relational database that requires a fixed schema, making it less suitable for varying attributes. While it can be globally distributed via failover groups, it does not guarantee the same low latency for point reads as Cosmos DB.
✓
Azure Cosmos DB
Why this is correct
Azure Cosmos DB is a globally distributed NoSQL database that supports flexible schemas and offers low-latency reads (under 10 ms) at any scale. It is the best fit for this scenario.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Table Storage
Why it's wrong here
Azure Table Storage is a key-value store that supports flexible schemas, but it is not globally distributed by default and does not provide the same low-latency guarantees as Cosmos DB, especially across regions.
✗
Azure Blob Storage
Why it's wrong here
Azure Blob Storage is for storing unstructured data such as documents, images, and videos. It does not provide low-latency point reads for individual records or support flexible schemas for application data.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse Azure Table Storage with Cosmos DB Table API, but the question specifies 'Azure Table Storage' (the older, standalone service) which lacks the global distribution and low-latency guarantees of Cosmos DB, leading them to incorrectly choose Option C.

Detailed technical explanation

How to think about this question

Azure Cosmos DB achieves sub-10 ms read latencies through its multi-region write and read replicas combined with a direct connectivity mode using the TCP protocol, bypassing the gateway for lower overhead. It uses a hash-based partitioning scheme (partition key) to distribute data across physical partitions, enabling fast point reads by PlayerID when the partition key is set to PlayerID. In a real-world scenario, a mobile gaming startup would configure Cosmos DB with a consistency level of 'Session' or 'Eventual' to minimize latency while still providing strong consistency for the player's own session.

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.

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: Azure Cosmos DB — Azure Cosmos DB is the correct choice because it is a globally distributed, multi-model database service that guarantees single-digit-millisecond read latencies (under 10 ms) at any scale from any Azure region. Its schema-agnostic nature allows storing player profiles with varying attributes (e.g., nickname, avatar URL) without requiring a fixed schema, and it supports point reads by PlayerID with a consistency model that can be tuned for performance. This directly matches the requirements of low-latency global reads and flexible, non-relational data.

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 startup needs to store user sessions as key-value pairs. Each session has a unique session ID, and the data needs to be globally distributed across multiple Azure regions to support low-latency reads for users worldwide. The development team expects heavy write throughput and needs flexible schema. Which Azure data store should they choose?

medium

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

Why C: Azure Cosmos DB is the correct choice because it provides globally distributed, multi-region writes and reads with turnkey global distribution, supports flexible schema via its document model, and offers multiple consistency levels to balance performance and data integrity. It is designed for high-throughput, low-latency workloads like user sessions, with session IDs serving as natural partition keys for efficient key-value lookups.

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.