The answer is Azure Cosmos DB, because it provides the low-latency storage for IoT telemetry data that this scenario demands. Its native support for real-time streaming ingestion via the Change Feed, combined with automatic indexing and single-digit millisecond read/write latencies, makes it ideal for handling JSON payloads from millions of devices every five seconds. By partitioning data using a composite key of device ID and time, you enable efficient querying across both dimensions, which is a core requirement for telemetry workloads. On the DP-203 exam, this question tests your understanding of choosing the right storage for high-velocity, time-series data—a common trap is selecting Azure Blob Storage or Event Hubs alone, but remember that Event Hubs is for ingestion, not persistent, queryable storage. A useful memory tip: think of Cosmos DB as the "single pane of glass" for globally distributed, low-latency telemetry, where the Change Feed acts like a real-time stream you can react to instantly.
DP-203 Design and implement data storage Practice Question
This DP-203 practice question tests your understanding of design and implement data storage. 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.
You are designing a solution to store telemetry data from millions of devices. Each device sends a JSON payload every 5 seconds. The data must be partitioned by device ID and time for efficient querying and must support real-time streaming ingestion. Which Azure storage solution should you recommend?
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 offers a multi-model, globally distributed database service with native support for real-time streaming ingestion via the Change Feed and automatic indexing. Its partition key design (device ID + time) enables efficient querying across millions of devices, and it guarantees single-digit millisecond read/write latencies essential for telemetry data arriving every 5 seconds.
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
Incorrect. SQL Database can be expensive and may have scalability limits for such high velocity data.
✗
Azure Blob Storage with Azure Event Hubs
Why it's wrong here
Incorrect. This is a pipeline, not a storage solution; Blob Storage does not natively support real-time queries.
✓
Azure Cosmos DB
Why this is correct
Correct. Cosmos DB supports real-time ingestion, automatic partitioning, and low-latency queries.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Table Storage
Why it's wrong here
Incorrect. Table Storage is limited in query capabilities and indexing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Azure Blob Storage with Event Hubs as a streaming solution, but Blob Storage is not designed for real-time, low-latency writes from millions of devices, and the combination adds unnecessary complexity and latency compared to Cosmos DB's native streaming support.
Detailed technical explanation
How to think about this question
Azure Cosmos DB uses a hash-based partition key to distribute data across physical partitions, and when you choose a partition key like /deviceId, all data for a device is co-located, enabling fast queries. The Change Feed allows real-time processing of incoming telemetry, and the automatic indexing ensures that time-based queries (e.g., WHERE timestamp > ...) are efficient without manual index management. In a real-world scenario, a telemetry system ingesting 200,000 writes per second can use Cosmos DB's multi-region writes to maintain low latency globally.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Design and implement data storage — This question tests Design and implement data storage — 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 offers a multi-model, globally distributed database service with native support for real-time streaming ingestion via the Change Feed and automatic indexing. Its partition key design (device ID + time) enables efficient querying across millions of devices, and it guarantees single-digit millisecond read/write latencies essential for telemetry data arriving every 5 seconds.
What should I do if I get this DP-203 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 →
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. You are designing a data storage solution for IoT sensor data. The data is written thousands of times per second and requires low-latency reads for real-time dashboards. Which Azure storage solution should you use?
easy
A.Azure Blob Storage
✓ B.Azure Cosmos DB
C.Azure SQL Database
D.Azure Data Lake Storage Gen2
Why B: Azure Cosmos DB is the correct choice because it provides single-digit millisecond read and write latency at any scale, with automatic indexing and multi-region distribution. Its support for multiple APIs (SQL, MongoDB, Cassandra, etc.) and configurable consistency levels makes it ideal for IoT sensor data requiring high-throughput writes and low-latency reads for real-time dashboards.
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.
This DP-203 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-203 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.