Handling Out-of-Order and Late Events in Stream Analytics
Your team is building a real-time dashboard using Azure Stream Analytics. The data source is an Azure Event Hub that receives clickstream events. You need to output aggregated data (counts per page per minute) to an Azure SQL Database for reporting. The query must handle late-arriving events and ensure exactly-once semantics. Which Stream Analytics feature should you use?
Quick Answer
The correct answer is to use the Input Order section in the Stream Analytics job configuration to set a late arrival tolerance window. This feature directly addresses the need to handle late-arriving events by defining a time span during which the system will wait for delayed data before closing a temporal window, such as a TumblingWindow, for aggregation. Combined with Stream Analytics’ built-in checkpointing and exactly-once output semantics, this ensures that your per-page-per-minute counts remain accurate even when events arrive out of order or behind schedule. On the DP-203 exam, this scenario tests your understanding of how Stream Analytics differs from Spark-based tools—watermarks are a Spark concept, not a Stream Analytics one. A common trap is confusing the “event ordering” policy (which handles out-of-order events within the stream) with the “late arrival” policy (which handles events arriving after the window closes). Remember: late arrival extends the window’s wait time, while event ordering reorders timestamps within that window. A useful mnemonic is “Late is a wait, order is a sort.”
⚠ Common exam trap
Many candidates confuse the late arrival tolerance window (set in job configuration) with window functions or watermarks used in other streaming systems, leading them to incorrectly select query-level options like temporal window functions or watermarks.
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
✓
Use the Input Order section in the Stream Analytics job configuration to set a late arrival tolerance window.
The Input Order section in Azure Stream Analytics job configuration allows you to set a late arrival tolerance window, which handles late-arriving events by buffering them for a specified duration. This ensures that events arriving after their timestamp are still included in the correct window for aggregation, supporting exactly-once semantics when combined with checkpointing and idempotent output to Azure SQL Database.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a temporal window function with a 'late arrival' policy specified in the query.
Why it's wrong here
Stream Analytics does not support a 'late arrival' policy in the query syntax; it is configured in job settings.
- ✓
Use the Input Order section in the Stream Analytics job configuration to set a late arrival tolerance window.
Why this is correct
Input Order policy allows handling late events, and Stream Analytics ensures exactly-once delivery to SQL Database.
- ✗
Define a watermark in the query to specify a maximum out-of-order tolerance.
Why it's wrong here
Watermarks are not a feature of Azure Stream Analytics; it uses other mechanisms.
- ✗
Set the event ordering policy to 'Adjust' to reorder events within a certain time window.
Why it's wrong here
Event ordering policy handles out-of-order events, not late-arriving events.
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 →
Same concept, more angles
1 more way this is tested on DP-203
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 building a real-time processing solution using Azure Stream Analytics. The solution must handle out-of-order events and late arrivals. Which THREE mechanisms should you configure in the Stream Analytics job?
medium- ✓ A.Set an 'Out-of-order tolerance' window in the event ordering settings.
- B.Adjust the 'Streaming units' to handle higher throughput.
- ✓ C.Configure a 'Late-arrival tolerance' window.
- D.Enable 'Event hub capture' to store raw events for reprocessing.
- ✓ E.Choose an output adapter that supports exactly-once delivery.
Why A: Azure Stream Analytics allows you to configure an 'Out-of-order tolerance' window in the event ordering settings. This window defines the maximum time difference that out-of-order events can be reordered before being considered late. By setting this tolerance, you ensure that events arriving slightly out of sequence are still processed correctly, which is critical for real-time analytics where event order matters.
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.