DP-900 Describe an analytics workload on Azure Practice Question
Which TWO are valid use cases for Azure Stream Analytics?
⚠ Common exam trap
Many exam-takers confuse real-time stream processing (Stream Analytics) with batch processing (Azure Synapse) or pipeline orchestration (Azure Data Factory), leading them to select options that describe different Azure services.
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
✓
Real-time fraud detection on credit card transactions
Azure Stream Analytics is a fully managed, real-time stream processing engine designed to ingest high-velocity event streams from sources like Event Hubs and IoT Hub and run continuous SQL-like queries over them, so option C (real-time fraud detection on credit card transactions) is correct because it requires low-latency, continuous evaluation of streaming transaction events to flag suspicious patterns as they occur. Option D (processing IoT sensor data and alerting when thresholds are exceeded) is also correct because Stream Analytics natively integrates with IoT Hub/Event Hubs and can emit alerts to outputs such as Service Bus, Event Grid, or Functions whenever a sliding or tumbling window query detects a threshold breach. Option A is incorrect because building and training ML models is the role of Azure Machine Learning, not a stream-processing service. Option B is incorrect because orchestrating pipelines with dependencies is handled by Azure Data Factory or Synapse Pipelines, not Stream Analytics. Option E is incorrect because batch processing of historical sales data is better served by Azure Data Factory, Synapse, Databricks, or HDInsight rather than a real-time streaming engine.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Building and training a machine learning model
Why it's wrong here
Building and training a machine learning model is not a Stream Analytics use case. Stream Analytics is a real-time event-processing engine that handles unbounded streams with temporal queries, whereas model training requires iterative, offline computation over historical datasets. Training is performed in Azure Machine Learning or Azure Databricks, and Stream Analytics only consumes already-trained models for real-time scoring via its integration with Azure ML, not for creating or optimizing them.
- ✗
Orchestrating complex data pipelines with dependencies
Why it's wrong here
Orchestrating complex data pipelines with dependencies is outside Stream Analytics' scope. Stream Analytics runs continuous, always-on queries over live data streams and has no concept of workflow dependencies, conditional branching, or scheduling of dependent tasks. Multi-step pipeline orchestration with explicit dependencies and control flow belongs to Azure Data Factory or Azure Logic Apps, which manage activities, triggers, and data movement across heterogeneous stores.
- ✓
Real-time fraud detection on credit card transactions
Why this is correct
Real-time fraud detection on credit card transactions is a classic Stream Analytics scenario. It ingests millions of transaction events per second from Event Hubs or IoT Hub, applies windowed functions (e.g., tumbling, hopping) and pattern matching to identify anomalies, and can join incoming streams with reference data such as customer spending history. This enables millisecond-latency responses that block or flag fraudulent transactions before they settle, a requirement that batch systems cannot meet.
- ✓
Processing IoT sensor data and alerting when thresholds are exceeded
Why this is correct
Processing IoT sensor data and alerting when thresholds are exceeded is a core Stream Analytics workload. It natively connects to IoT Hub/Event Hubs to subscribe to continuous telemetry streams, then uses SQL-like queries with filters and conditional logic to evaluate sensor readings against defined thresholds in near real time. When a condition matches, Stream Analytics can route the alert to output sinks like Azure Functions, Service Bus, or Power BI for immediate action, making it ideal for real-time monitoring.
- ✗
Batch processing of historical sales data
Why it's wrong here
Batch processing of historical sales data does not fit Stream Analytics because it is built for unbounded, live data streams rather than bounded, static datasets. In contrast, historical batch jobs typically involve reading stored data from a data lake or database, applying transformations, and writing aggregated results—this is the domain of Azure Data Factory, Azure Databricks, or Azure Synapse pipelines. Stream Analytics uses sliding or tumbling windows that move continuously over incoming events, and it cannot process a fixed historical snapshot in the same way.
Go deeper
Related to this question
Learn chapter
Databricks Notebooks and Clusters
Key term
Azure Data Factory
Azure Data Factory is a cloud-based data integration service that lets you create, schedule, and orchestrate data pipelines to move and transform data from various sources to destinations.
Key term
Azure Stream Analytics
Azure Stream Analytics is a fully managed, real-time data processing service that analyzes and transforms high volumes of streaming data from various sources to deliver low-latency insights and trigger actions.
About these practice questions
One of 851 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.