Download Microsoft.AZ-220.NewDumps.2021-07-14.93q.vcex

Box 1: iothub1 -The Azure IoT hub is named iothub1. Box 2: azure-devices.net -The format of the device connection string looks like:HostName={YourIoTHubName}.azure-devices.net;DeviceId=MyNodeDevice;SharedAccessKey={YourSharedAccessKey} Box 1: device1 -Device1 has a primary key of Uihuih76hbHb. Reference:https://docs.microsoft.com/en-us/azure/iot-hub/quickstart-control-device-dotnet

Scenario: You discover connectivity issues between the IoT gateway devices and iothub1, which cause IoT devices to lose connectivity and messages. To log device connection events and errors, turn on diagnostics for IoT Hub. We recommend turning on these logs as early as possible, because if diagnostic logs aren't enabled, when device disconnects occur, you won't have any information to troubleshoot the problem with. Step 1:Sign in to the Azure portal. Browse to your IoT hub. Select Diagnostics settings. Select Turn on diagnostics. Enable Connections logs to be collected. For easier analysis, turn on Send to Log Analytics (see pricing). Step 2:Set up alerts for device disconnect at scale To get alerts when devices disconnect, configure alerts on the Connected devices (preview) metric. Reference:https://docs.microsoft.com/bs-cyrl-ba/azure/iot-hub/iot-hub-troubleshoot-connectivity

Box 1: ID Scope -In the Azure portal, select the Overview blade for your Device Provisioning service and copy the ID Scope value. The ID Scope is generated by the service and guarantees uniqueness. It is immutable and used to uniquely identify the registration IDs. Box 2: Global device endpoint -  The global_prov_uri variable, which allows the IoT Hub client registration API IoTHubClient_LL_CreateFromDeviceAuth to connect with the designated Device Provisioning Service instance. Example code:static const char* global_prov_uri = "global.azure-devices-provisioning.net"; static const char* id_scope = "[ID Scope]"; Reference:https://docs.microsoft.com/en-us/azure/iot-dps/tutorial-set-up-device

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. Reference:https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-how-to-add-an-event-source-iothub

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. Incorrect Answers: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

https://docs.microsoft.com/bs-cyrl-ba/azure/iot-hub/iot-hub-message-enrichments-overview

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. Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-distributed-tracing

You may find it necessary to deprovision devices that were previously auto-provisioned through the Device Provisioning Service. In general, deprovisioning a device involves two steps:Disenroll the device from your provisioning service, to prevent future auto-provisioning. Depending on whether you want to revoke access temporarily or permanently, you may want to either disable or delete an enrollment entry. Deregister the device from your IoT Hub, to prevent future communications and data transfer. Again, you can temporarily disable or permanently delete the device's entry in the identity registry for the IoT Hub where it was provisioned. Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-unprovision-devices

Instead, from the Device Provisioning Service, you disable the enrollment group, and you disable device entries in the identity registry of the IoT hub to which the IoT devices are provisioned. Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-unprovision-devices