Describe considerations for working with non-relational data on Azure →easyMultiple ChoiceObjective-mapped
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
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?
⚠ Common exam trap
It's easy for candidates to 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.
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.
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 enforces a fixed relational schema, which cannot accommodate the varying attributes per player profile without costly schema redesign or nullable columns, and its global read latency under 10 ms would require geo-replication and read-scale-out configurations that add complexity and cost. It is tempting because it offers robust transactional consistency and complex querying, making it the correct choice for applications requiring ACID compliance, joins, or reporting on structured data with predictable schemas.
- ✓
Azure Cosmos DB
Why this is correct
Azure Cosmos DB is a globally distributed, multi-model NoSQL database that natively supports schema-flexible JSON documents, making it ideal for player profiles whose attributes evolve over time. It provides turnkey global distribution with multi-region writes, and its SLA guarantees point reads under 10 ms at the 99th percentile from any Azure region, directly meeting both the low-latency and flexible-schema requirements of a mobile gaming startup. Cosmos DB also offers automatic indexing, tunable consistency levels, and RU-based throughput scaling, which together support fast, consistent player-profile lookups without the need for costly schema redesigns.
- ✗
Azure Table Storage
Why it's wrong here
Azure Table Storage is a NoSQL key-value store that does accept flexible schema, but it lacks Cosmos DB's global active-active distribution, offering only storage-redundancy options like LRS or RA-GRS failover rather than multi-region write capability. Its read latency is not governed by the same under-10-ms point-read SLA across arbitrary regions, and it does not provide automatic secondary indexes or rich querying over document properties. While Table Storage can store player profiles cheaply, it would require secondary lookup tables or manual denormalization to achieve the same low-latency, globally available access pattern, making it a poor fit for this scenario.
- ✗
Azure Blob Storage
Why it's wrong here
Azure Blob Storage is designed for unstructured binary data such as images, videos, logs, and backups, not for individual record-level reads of application entities. Although blob data is schemaless, Blob Storage has no query engine that can filter or project properties inside a blob, so using it for player profiles would force entire blobs to be downloaded and deserialized just to access one record, yielding latency far above 10 ms for point lookups. It is therefore unsuitable for a mobile gaming backend that needs fast, schema-flexible profile retrieval; a document or key-value database is the correct pattern here.
Go deeper
Related to this question
Learn chapter
Data Roles and Core Concepts
Key term
Data
Data is raw, unprocessed information, like numbers, words, or measurements, that can be stored, processed, and analyzed by computers.
Key term
Schema
A schema is a blueprint or logical structure that defines how data is organized, stored, and accessed in a database or information system.
About these practice questions
This DP-900 question is part of Courseiva's 820-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.