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
You need to store telemetry data from millions of devices. Each record includes a device ID, timestamp, and metric value. The data will be queried by device ID and time range. Which Azure data store is best suited for this scenario?
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 Data Explorer
Azure Data Explorer (ADX) is optimized for time-series data and can ingest high volumes of telemetry, with fast queries on time ranges and device IDs. Azure Cosmos DB is good for real-time apps but less efficient for large-scale time-series analytics. Azure SQL Database is relational and may not scale as well. Azure Storage Queues are for messaging, not storage/query.
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 Data Explorer
Why this is correct
Azure Data Explorer (ADX) is a fully managed analytics database purpose-built for high-volume time-series and log data. Its columnar storage engine uses advanced indexing and compression to ingest millions of events per second while retaining interactive query performance via Kusto Query Language (KQL). KQL includes native time-series functions like bin(), summarize, and percentiles, enabling near-real-time telemetry analytics without external processing. This makes ADX the optimal choice for telemetry pipelines that demand fast ingestion, long-term retention, and complex temporal queries.
- ✗
Azure SQL Database
Why it's wrong here
Azure SQL Database is a relational database management system optimized for online transaction processing (OLTP) with row-based storage, which yields high overhead when ingesting and querying continuous telemetry streams. It lacks native time-series features such as automatic data retention policies, downsampling, or time-based partitioning, so you would need to manually implement partitioning and indexing to avoid performance degradation. While it can technically store telemetry data, its architecture struggles to scale cost-effectively to millions of devices generating high-cardinality events, making it a poor fit for this workload.
- ✗
Azure Storage Queues
Why it's wrong here
Azure Storage Queues is a message queuing service designed for asynchronous decoupling of application components, not for persistent storage or analytical querying. Messages are transient, have a maximum time-to-live of 7 days, and support a small payload size, so telemetry would be lost quickly and cannot be retained for historical analysis. Additionally, Storage Queues provides no query language, aggregation operators, or indexing, making it impossible to run analytical queries on the data. It could serve as a temporary ingestion buffer, but it is not a storage solution for telemetry.
- ✗
Azure Cosmos DB
Why it's wrong here
Azure Cosmos DB is a multi-model NoSQL database with low-latency access and global distribution, but it incurs high request-unit (RU) costs when ingesting high-throughput telemetry because every write is indexed on multiple paths by default. Its document-oriented storage is not columnar, and it lacks time-series-specific optimizations like time-based partitioning, retention policies, and specialized temporal query functions (e.g., downsampling, interpolations). Although Cosmos DB can store IoT data, its per-operation cost and lack of analytical performance make it significantly more expensive and less suitable than Azure Data Explorer for large-scale time-series analytics.
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
Azure Cosmos DB
Azure Cosmos DB is a fully managed, globally distributed NoSQL database service that offers fast reads and writes anywhere in the world with automatic scaling and multiple consistency models.
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.