Exam DP-203 All QuestionsBrowse all questions from this exam
Go to Exam
Question 130

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You are designing an Azure Stream Analytics solution that will analyze Twitter data.

You need to count the tweets in each 10-second window. The solution must ensure that each tweet is counted only once.

Solution: You use a hopping window that uses a hop size of 10 seconds and a window size of 10 seconds.

Does this meet the goal?

    Correct Answer: A

    In Azure Stream Analytics, a hopping window with a hop size equal to the window size behaves like a tumbling window. Tumbling windows are a series of fixed-sized, non-overlapping time intervals. Since the goal is to count each tweet only once in a 10-second window, setting both the hop size and the window size to 10 seconds ensures that the windows are non-overlapping and each tweet is counted only once. Thus, using a hopping window with these parameters meets the stated requirements.

Discussion
[Removed]Option: A

The answer should be "Yes". Hopping window with hop size equals window size should be the same as Tumbling window.

YipingRuan

ensure that each tweet is counted only once

dsp17

Correct Ans: B. tumbling window Read the question carefully - "The solution must ensure that each tweet is counted only once." By defination, hopping window is not non-overlapping

strato

a hopping window with equal window size to the hopping is effectively non-overlapping. If the size of the hop was smaller, sure.

DataEngineer7331

A Tumbling Window would be correct. But as stated in the following, a hopping window can be the same as a tumbling window: "To make a Hopping window the same as a Tumbling window, specify the hop size to be the same as the window size." https://learn.microsoft.com/en-us/azure/stream-analytics/stream-analytics-window-functions#hopping-window

medsimusOption: B

Unlike tumbling windows, hopping windows model scheduled overlapping windows. A hopping window specification consist of three parameters: the timeunit, the windowsize (how long each window lasts) and the hopsize (by how much each window moves forward relative to the previous one). Additionally, offsetsize may be used as an optional fourth parameter. Note that a tumbling window is simply a hopping window whose ‘hop’ is equal to its ‘size’.

ElancheOption: B

B. No Using a hopping window with a hop size of 10 seconds and a window size of 10 seconds wouldn't ensure that each tweet is counted only once. A hopping window with these parameters would result in overlapping windows, which means that a tweet might fall into multiple windows and could potentially be counted multiple times. To ensure that each tweet is counted only once within a specific 10-second window, you should use a tumbling window with a size of 10 seconds. Tumbling windows are non-overlapping and fixed-size, ensuring that each tweet is counted within a single, distinct window.

Azure_2023Option: A

To make a Hopping window the same as a Tumbling window, specify the hop size to be the same as the window size.

saqib839Option: A

If you specify a hopping window in Azure Stream Analytics with a duration of 10 seconds and a hop size of 10 seconds (for example, HoppingWindow(second, 10, 10)), it will indeed behave like a tumbling window. In this case, the hop size is equal to the window size, which means that there is no overlap between the windows. Each hopping window will move forward by 10 seconds, which is the same as its duration. Therefore, every event will fall into exactly one window, ensuring that each tweet is counted only once per 10-second window. This setup meets the requirement of counting tweets in each 10-second window without double-counting any tweet.

sdg2844Option: A

While a tumbling window would be more straightforward, a Hopping window with 10/10 parameters will produce the same result, as it is set not to overlap.

positivitypeople

Got this question today on the exam

MomoanwarOption: B

Chatgpt : No The answer is **B. No**, this does not meet the goal. Using a hopping window with both the hop size and the window size set to 10 seconds would result in each tweet being counted multiple times as each tweet could appear in several windows. To ensure each tweet is counted only once, the hop size should be equal to the window size or a different type of windowing, such as tumbling windows, should be used.

DanweoOption: A

Overlapping only applies if the window size is larger than the hop size. Hopping is the same as tumbling with an equal hop to window size.

ageorgievaOption: B

The answer is B:No. Tumbling window should be used. With hopping window there is an overlap and an event can be counted more than once.

DusicaOption: A

Yes is correct

AlongiOption: A

A. Yes A tumbling window is the same as an hopping window with the window size equal to the hop size.

moneytimeOption: A

Answer is Yes. The solution actually defined Tumbling window using hopping window. The condition is ; if the hopping size equals window size,then the window is also Tumbling.

sr0017Option: B

risposta B corretta

Amir_AbedOption: B

Answer should be B

6d954dfOption: A

A. Yes The proposed solution meets the goal. In Azure Stream Analytics, a hopping window generates output every hop size interval, and it aggregates events for the window size period. If both the hop size and window size are set to 10 seconds, the system will count the tweets in each 10-second window, ensuring each tweet is counted only once. This is because the window “hops” forward by the specified hop size (10 seconds in this case) and does not overlap with the next window. Therefore, each tweet will fall into exactly one window and will be counted once. This makes the hopping window suitable for this scenario.

phydevOption: A

Yes, the solution described using a hopping window with a hop size of 10 seconds and a window size of 10 seconds would meet the goal of counting tweets in each 10-second window. In Azure Stream Analytics, a hopping window moves forward in time at regular intervals (the hop size) and collects data within the specified window size. In this case, with a window size of 10 seconds and a hop size of 10 seconds, you ensure that the system counts tweets