Courseiva

DP-203 InputEvents Practice Question

You are monitoring an Azure Stream Analytics job that processes streaming data from Event Hubs to Azure Synapse Analytics. Which TWO Azure Monitor metrics should you set alerts on to detect data loss or processing delays?

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

InputEvents and OutputEvents metrics

The correct metrics for detecting data loss or processing delays in an Azure Stream Analytics job are InputEvents and OutputEvents (Option A). By comparing these, you can determine if every event entering the job is being output; a mismatch indicates potential data loss. Backlogged input events (Option E) directly measures the number of events waiting to be processed, and a high or growing value signals processing delays. Option B (Duration) is not a direct indicator of data loss or processing delays in Stream Analytics. Option C (Data read/written) is not a metric for Stream Analytics. Option D (Pipeline run count) is not applicable to Stream Analytics streaming jobs.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • InputEvents and OutputEvents metrics

    Why this is correct

    InputEvents and OutputEvents (Option A) are correct. By comparing these two metrics, you can see if every event entering the Stream Analytics job is being output, indicating potential data loss if they diverge.

  • Duration metric

    Why it's wrong here

    Duration (Option B) is a metric for job runs, not streaming throughput. It does not directly indicate data loss or processing delays.

  • Data read and data written metrics

    Why it's wrong here

    Data read and data written metrics are not defined for Azure Stream Analytics; they apply to other services like copy activities in data integration.

  • Pipeline run count metric

    Why it's wrong here

    Pipeline run count metric is relevant for batch pipeline services, not for Stream Analytics streaming jobs.

  • Backlogged input events metric

    Why this is correct

    Backlogged input events (Option E) directly measures the number of events waiting to be processed; a high or growing value signals processing delays.

Visual reference

Client Server SYN (seq=100) SYN-ACK (seq=200, ack=101) ACK (ack=201) Connection established — data transfer begins

Go deeper

Related to this question

About these practice questions

This DP-203 question is part of Courseiva's 760-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 →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.