The answer is Azure Stream Analytics with a tumbling window of 1 minute and a late-arrival policy of 30 seconds. This service is the correct choice because it natively supports windowed aggregations—such as tumbling, hopping, sliding, and session windows—and allows you to configure a late-arrival tolerance to handle out-of-order events, which is essential for building a real-time dashboard from Azure Event Hubs. The aggregated results can be written directly to Azure Cosmos DB for low-latency reads, meeting the requirement exactly. On the DP-203 exam, this scenario tests your understanding of stream processing semantics and windowing functions; a common trap is confusing tumbling windows with hopping windows or forgetting that late-arrival policies must be explicitly set. Memory tip: think “Tumbling for time, late policy for lag”—the window shape controls aggregation timing, while the late-arrival policy controls how long the engine waits for straggling events.
DP-203 Develop data processing Practice Question
This DP-203 practice question tests your understanding of develop data processing. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are building a real-time dashboard to monitor user activity on a website. The data is ingested via Azure Event Hubs and must be aggregated every minute with a 30-second late-arrival tolerance. The aggregated results should be stored in Azure Cosmos DB for low-latency reads. Which Azure service should you use to perform the windowed aggregation?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Stream Analytics with a tumbling window of 1 minute and a late-arrival policy of 30 seconds.
Azure Stream Analytics is the correct choice because it natively supports windowed aggregations (tumbling, hopping, sliding, session) and allows you to define a late-arrival policy to handle out-of-order events. A tumbling window of 1 minute with a late-arrival tolerance of 30 seconds meets the requirement exactly, and the output can be directly written to Azure Cosmos DB for low-latency reads.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 Stream Analytics with a tumbling window of 1 minute and a late-arrival policy of 30 seconds.
Why this is correct
Stream Analytics provides built-in windowing functions and late-arrival handling, perfect for this scenario.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Functions triggered by Event Hubs to aggregate data and write to Cosmos DB.
Why it's wrong here
Azure Functions doesn't natively support windowed aggregation; you would need to implement state management manually.
✗
Azure Databricks with structured streaming and a sliding window.
Why it's wrong here
While capable, it introduces unnecessary complexity and cost for a simple aggregation.
✗
Azure Analysis Services to process streaming data directly from Event Hubs.
Why it's wrong here
Analysis Services is a tabular model engine, not a streaming processor.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse tumbling windows (fixed, non-overlapping) with sliding windows (continuous, overlapping) or assume that any compute service (like Functions or Databricks) can easily replicate Stream Analytics' built-in windowing and late-arrival handling, ignoring the complexity of state management and exactly-once semantics.
Detailed technical explanation
How to think about this question
Under the hood, Azure Stream Analytics uses a time-ordered processing engine that assigns a watermark based on the late-arrival policy. For a 1-minute tumbling window with a 30-second late-arrival tolerance, events arriving up to 30 seconds after the window end are still included, but the output is delayed by that tolerance to ensure completeness. This is critical in scenarios like clickstream analytics where network delays or client-side buffering cause out-of-order events.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Develop data processing — This question tests Develop data processing — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Azure Stream Analytics with a tumbling window of 1 minute and a late-arrival policy of 30 seconds. — Azure Stream Analytics is the correct choice because it natively supports windowed aggregations (tumbling, hopping, sliding, session) and allows you to define a late-arrival policy to handle out-of-order events. A tumbling window of 1 minute with a late-arrival tolerance of 30 seconds meets the requirement exactly, and the output can be directly written to Azure Cosmos DB for low-latency reads.
What should I do if I get this DP-203 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.