Scenario: You plan to use a 30-second period to calculate the average temperature reading of the sensors.
Tumbling window functions are used to segment a data stream into distinct time segments and perform a function against them, such as the example below. The key differentiators of a Tumbling window are that they repeat, do not overlap, and an event cannot belong to more than one tumbling window.
InAnswers:
A: Hopping window functions hop forward in time by a fixed period. It may be easy to think of them as Tumbling windows that can overlap, so events can belong to more than one Hopping window result set.
Reference:
https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-window-functions
Topic 1, Contoso
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Existing Environment. Current State of Development
Contoso produces a set of Bluetooth sensors that read the temperature and humidity. The sensors connect to IoT gateway devices that relay the data.
All the IoT gateway devices connect to an Azure IoT hub named iothub1.
Existing Environment. Device Twin
You plan to implement device twins by using the following JSON sample.

Existing Environment. Azure Stream Analytics
Each room will have between three to five sensors that will generate readings that are sent to a single IoT gateway device. The IoT gateway device will forward all the readings to iothub1 at intervals of between 10 and 60 seconds.
You plan to use a gateway pattern so that each IoT gateway device will have its own IoT Hub device identity.
You draft the following query, which is missing the GROUP BY clause.
SELECT
AVG(temperature),
System.TimeStamp() AS AsaTime
FROM
Iothub
You plan to use a 30-second period to calculate the average temperature reading of the sensors.
You plan to minimize latency between the condition reported by the sensors and the corresponding alert issued by the Stream Analytics job.
Existing Environment. Device Messages
The IoT gateway devices will send messages that contain the following JSON data whenever the temperature exceeds a specified threshold.

The level property will be used to route the messages to an Azure Service Bus queue endpoint named criticalep.
Existing Environment. Issues
You discover connectivity issues between the IoT gateway devices and iothub1, which cause IoT devices to lose connectivity and messages.
Requirements. Planning Changes
Contoso plans to make the following changes:
Use Stream Analytics to process and view data.
Use Azure Time Series Insights to visualize data.
Implement a system to sync device statuses and required settings.
Add extra information to messages by using message enrichment.
Create a notification system to send an alert if a condition exceeds a specified threshold.
Implement a system to identify what causes the intermittent connection issues and lost messages.
Requirements. Technical Requirements
Contoso must meet the following requirements:
Use the built-in functions of IoT Hub whenever possible.
Minimize hardware and software costs whenever possible.
Minimize administrative effort to provision devices at scale.
Implement a system to trace message flow to and from iothub1.
Minimize the amount of custom coding required to implement the planned changes.
Prevent read operations from being negatively affected when you implement additional services.

1 - From Azure IoT hub, create an IoT Edge device
2 - From an elevated PowerShell prompt, run the Deploy-IoTEdge cmdlet.
3 - From an elevated PowerShell prompt, run the Initialize-IoTEdge cmdlet
4 - Enter the IoT Edge device connection string.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/quickstart

Reference:
https://docs.microsoft.com/bs-cyrl-ba/azure/iot-hub/iot-hub-message-enrichments-overview
Topic 2, ADatum
To start the case study
To display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Requirements. Planned Changes
ADatum is developing an Azure IoT solution to monitor environmental conditions. The IoT solution consists of hardware devices and cloud services. All the devices will communicate directly to Azure IoT Hub.
The hardware devices will be deployed to the branch offices and will collect data about various environmental conditions such as temperature, humidity, air quality, and noise level. The devices will be wired by using Power over Ethernet (PoE) connections.
ADatum is developing the solution in the following three phases: proof of value (POV), pilot, and production.
Requirements. POV Requirements
The POV phase will demonstrate that a technical solution is viable. During this phase, 100 devices will be deployed to the main office and Azure Stream Analytics will be connected to an IoT hub to generate real-time alerts. Stream Analytics will perform the following processing:
Calculate the median rate of the telemetry across the entire devices that exceed the median rate by a factor of 4.
Compare the current telemetry to the specified thresholds and issue alerts when telemetry values are out of range.
Ensure that all message content during this phase is human readable to simplify debugging.
Requirements. Pilot Requirements
During the pilot phase, devices will be deployed to 10 offices. Each office will have up to 1,000 devices.
During this phase, you will add Azure Time Series Insights in parallel to Stream Analytics to support real-time graphs and queries in a dashboard web app.
The pilot deployment must minimize operating costs.
Requirements. Production Requirements
The production phase will include all the offices.
The production deployment will have one IoT hub in each Azure region. Devices must connect to the IoT hub in their region.
The production phase must meet the following requirements:
Ensure that the IoT solution can support performance and scale targets.
Ensure that the IoT solution support up to 1,000 devices per office.
Minimize operating costs of the IoT solution.
Requirements. Technical Requirements
Datum identifies the following requirements for the planned IoT solution:
The solution must generate real-time alerts when a fire condition is detected in an office. All the devices in that office must trigger an audible alarm siren within 10 seconds of the alert.
A dashboard UI must display alerts and the system status in real time and must allow device operators to make adjustments to the system.
Each device will send hourly updates to IoT Hub. Condition alerts will be sent immediately.
Multiple types of devices will collect telemetry that has different schemas.
IoT Hub must perform message routing based on the message body.
Direct methods must be used for cloud-to-device communication.
Reports must be provided monthly, quarterly, and annually.
Stored data queries must be as efficient as possible.
The device message size will be under 4 KB.
Development effort must be minimized.
Requirements. Throttle and Quotas
The relevant throttles and quotas for various IoT Hub tiers are shown in the following table.

Requirements. IoT Hub Routing
You plan to implement IoT Hub routing during the POV phase as shown in the following exhibit.

C: Device twins change notifications allow back end applications to be notified in real-time of twin changes and react as business logic requires. For instance, when building an application that notifies an operator directly that a device has a firmware update pending and is "ready to update". This is accomplished by creating a routing rule from the "Twin Change Events" source and filtering all events that involve the software update status.
D: Applying enrichments
The messages can come from any data source supported by IoT Hub message routing, including the following examples:
* -->device twin change notifications -- changes in the device twin
* device telemetry, such as temperature or pressure
* device life-cycle events, such as when the device is created or deleted Reference:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-message-enrichments-overview
https://azure.microsoft.com/en-us/blog/enhancements-to-azure-iot-hub-improve-management-of-the-full- device-lifecycle/