AZ-220 Exam Dumps - Microsoft Azure IoT Developer

The device telemetry is usually passed as JSON from the device through the IoT Hub - this is handled nicely by Azure Streaming Analytics queries.

The IoT Hub message routing should be configured as follows: Data source: Device Telemetry Messages

Routing query: true (as the routing query is an expression that evaluates to true or false for each received

message, the simplest way to send all messages to the endpoint is to just supply true as the query).

A common problem with many legacy devices is that they often have an identity that is composed of a single piece of information. This identity information is usually a MAC address or a serial number. Legacy devices may not have a certificate, TPM, or any other security feature that can be used to securely identify the device. The Device Provisioning Service for IoT hub includes symmetric key attestation. Symmetric key attestation can be used to identify a device based off information like the MAC address or a serial number.

IoT Hub is one of the first Azure services to support distributed tracing. As more Azure services support distributed tracing, you'll be able trace IoT messages throughout the Azure services involved in your solution.

Note:

Enabling distributed tracing for IoT Hub gives you the ability to:

Precisely monitor the flow of each message through IoT Hub using trace context. This trace context includes correlation IDs that allow you to correlate events from one component with events from another component. It can be applied for a subset or all IoT device messages using device twin.

Automatically log the trace context to Azure Monitor diagnostic logs.

Measure and understand message flow and latency from devices to IoT Hub and routing endpoints. Start considering how you want to implement distributed tracing for the non-Azure services in your IoT solution.

Create a dedicated consumer group in the IoT hub for the Time Series Insights environment to consume from. Each Time Series Insights event source must have its own dedicated consumer group that isn't shared with any other consumer. If multiple readers consume events from the same consumer group, all readers are likely to exhibit failures.

Consider using jobs when you need to schedule and track progress any of the following activities on a set of devices:

• Invoke direct methods
• Update desired properties
• Update tags

When you create a Time Series Insights Preview pay-as-you-go (PAYG) SKU environment, you create two Azure resources:

An Azure Storage general-purpose V1 blob account for cold data storage.

An Azure Time Series Insights Preview environment that can be configured for warm data storage.

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.

Step 1: Provision Time Series Insights

Select Provision new IoT Hub to create a new IoT hub.

Step 2: Route telemetry from IoT Hub to a custom event.

Step 3: Add a data access policy to Time Series Insights for the dashboard web app

Scenario: 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.