Describe considerations for working with non-relational data on Azure →mediumMultiple ChoiceObjective-mapped
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
A real-time leaderboard for an online game needs to store player scores and quickly retrieve the top 100 players. The data must update frequently as players achieve new scores, and the application requires sub-millisecond read and write latency. Which Azure data store is best suited for this requirement?
⚠ Common exam trap
Microsoft often tests the misconception that any low-latency NoSQL store (like Cosmos DB) can match Redis for sub-millisecond, in-memory operations, but the key differentiator is Redis's exclusive sorted set data structure and its dedicated in-memory architecture.
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 Cache for Redis
Azure Cache for Redis is an in-memory data store that provides sub-millisecond read and write latency, making it ideal for real-time leaderboards that require frequent updates and fast retrieval of top scores. Its sorted set data structure (ZADD/ZRANGEBYSCORE) allows efficient insertion of player scores and O(log N) retrieval of the top 100 players without disk I/O overhead.
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 Cosmos DB Core (SQL) API
Why it's wrong here
Cosmos DB can store and query data with low latency, but it is not optimized for real-time leaderboard sorted sets; it is a full-featured NoSQL database with higher latency (typically a few milliseconds) and cost compared to an in-memory cache.
When this WOULD be correct
Azure Cosmos DB Core (SQL) API would be correct for a globally distributed leaderboard that requires multi-region writes, strong consistency, and complex querying (e.g., filtering by date range or player attributes) while still needing low latency (though not sub-millisecond).
- ✗
Azure Table Storage
Why it's wrong here
Azure Table Storage is a NoSQL key-value store that organizes entities by partition key and row key. It supports fast point reads and range scans on keys, but it does not natively support sorted sets, score-based ordering, or server-side rank calculations; to produce a leaderboard, a client would need to pull every player's score and perform sorting and ranking locally, which scales poorly and cannot provide real-time freshness.
When this WOULD be correct
A question requiring a cost-effective, schema-less NoSQL store for large volumes of structured data (e.g., logging telemetry from millions of devices) where latency requirements are in the millisecond range (not sub-millisecond) and complex queries are not needed.
- ✓
Azure Cache for Redis
Why this is correct
Azure Cache for Redis is built on an in-memory data store that provides native sorted set data structures (e.g., ZADD, ZRANGE, ZREVRANK). Leaderboard operations such as inserting a player's score, retrieving the top N players, and finding a player's exact rank execute in O(log N) time with sub-millisecond latency, making it purpose-built for real-time scenarios where millions of players update scores concurrently.
- ✗
Azure Blob Storage
Why it's wrong here
Azure Blob Storage is an object storage service intended for massive, unstructured data such as files, images, videos, and backups. It exposes a flat namespace with blobs accessed via HTTP, but it has no built-in query engine, no secondary indexes, and no data structures for maintaining ordered scores; retrieving a leaderboard would require downloading and sorting all blobs client-side, introducing far too much latency for real-time updates.
When this WOULD be correct
A question requiring storage of large binary files (e.g., game replays, screenshots) with high throughput and low cost, where latency is not critical. For example: 'Which Azure service should be used to store video clips of game highlights for archival and batch processing?'
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The DP-900 exam frequently reuses these exact scenarios with slightly different constraints.
✓Azure Cache for RedisCorrect answer▾
Why this is correct
Azure Cache for Redis is built on an in-memory data store that provides native sorted set data structures (e.g., ZADD, ZRANGE, ZREVRANK). Leaderboard operations such as inserting a player's score, retrieving the top N players, and finding a player's exact rank execute in O(log N) time with sub-millisecond latency, making it purpose-built for real-time scenarios where millions of players update scores concurrently.
✗Azure Cosmos DB Core (SQL) APIWrong answer — click to see why▾
Why this is wrong here
Azure Cosmos DB Core (SQL) API provides low latency and high throughput, but for a real-time leaderboard requiring sub-millisecond read/write latency and frequent updates, Azure Cache for Redis is more suitable due to its in-memory data store and built-in sorted set data structure for leaderboards.
★ When this WOULD be the correct answer
Azure Cosmos DB Core (SQL) API would be correct for a globally distributed leaderboard that requires multi-region writes, strong consistency, and complex querying (e.g., filtering by date range or player attributes) while still needing low latency (though not sub-millisecond).
Why candidates choose this
Candidates may associate Cosmos DB with low latency and high performance, overlooking that Redis is specifically optimized for in-memory, real-time leaderboard scenarios with sub-millisecond latency.
✗Azure Table StorageWrong answer — click to see why▾
Why this is wrong here
Azure Table Storage does not support sub-millisecond read/write latency or built-in leaderboard ranking operations like sorted sets, making it unsuitable for real-time leaderboard updates and top-100 retrieval.
★ When this WOULD be the correct answer
A question requiring a cost-effective, schema-less NoSQL store for large volumes of structured data (e.g., logging telemetry from millions of devices) where latency requirements are in the millisecond range (not sub-millisecond) and complex queries are not needed.
Why candidates choose this
Candidates may associate Table Storage with fast key-value lookups and scalability, overlooking its lack of native sorted set operations and higher latency compared to in-memory caches like Redis.
✗Azure Blob StorageWrong answer — click to see why▾
Why this is wrong here
Azure Blob Storage is designed for storing large amounts of unstructured data like images, videos, and backups, not for low-latency, high-frequency updates of leaderboard scores. It lacks sub-millisecond read/write latency and does not support real-time ranking queries efficiently.
★ When this WOULD be the correct answer
A question requiring storage of large binary files (e.g., game replays, screenshots) with high throughput and low cost, where latency is not critical. For example: 'Which Azure service should be used to store video clips of game highlights for archival and batch processing?'
Why candidates choose this
Candidates may think Blob Storage can handle any data type because it's a general-purpose storage solution, overlooking its unsuitability for real-time, low-latency transactional workloads.
Analysis generated from the official DP-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
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
Redis
Redis is an open-source, in-memory data structure store used as a database, cache, and message broker for high-speed data access.
About these practice questions
Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.