DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
Your team is running a critical Azure Stream Analytics job that writes results to Azure SQL Database. Recently, the job has been failing with high latency and occasional data loss. You need to monitor the job's performance and set up alerts for when the watermark delay exceeds a threshold. What should you use?
⚠ Common exam trap
DP-203 often tests the difference between Azure Monitor metrics and Log Analytics for Stream Analytics; candidates who assume diagnostic logs are required for alerting choose Log Analytics instead of the native metric-based alerting approach.
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 Monitor metrics for the Stream Analytics job.
Azure Monitor metrics for the Stream Analytics job provide built-in performance metrics such as Watermark Delay, Input Events, Output Events, and Runtime Errors, and you can create alert rules on these metrics when the watermark delay exceeds a threshold. This is the native, recommended way to monitor Stream Analytics job performance and set up alerts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Application Insights SDK integration in the job.
Why it's wrong here
Application Insights SDK instrumentation captures custom application telemetry, not Stream Analytics runtime metrics such as watermark delay, so no alert threshold can be set on it. It is tempting because App Insights does support metric alerts, and would be right for monitoring a custom application's own performance.
- ✗
Azure Log Analytics workspace connected to the job diagnostics logs.
Why it's wrong here
While Azure Log Analytics is excellent for ingesting and querying diagnostic logs for detailed operational troubleshooting and correlating events, it does not directly provide "watermark delay" as a native metric for threshold-based alerting. Watermark delay is a specific metric of Azure Stream Analytics, which is best monitored and alerted upon using Azure Monitor Metrics. Log Analytics would be the correct choice for analysing specific error messages, custom application logs, or complex event patterns within the logs themselves, enabling deep post-mortem analysis.
- ✓
Azure Monitor metrics for the Stream Analytics job.
Why this is correct
Azure Monitor exposes the Stream Analytics watermark delay metric, which directly quantifies the latency causing failures. Alert rules on that metric trigger when the threshold is breached, satisfying the monitoring and alerting requirement without custom instrumentation.
- ✗
Azure Data Explorer for querying job performance data.
Why it's wrong here
Azure Data Explorer stores and queries data but does not collect Stream Analytics job metrics or raise alerts on watermark delay. It is tempting because Data Explorer excels at ad-hoc log analytics, and would be correct for interactively exploring exported telemetry, not for metric-based alerting.
Go deeper
Related to this question
About these practice questions
This DP-203 question is part of Courseiva's 509-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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.