Event Grid Integration for Telemetry Alerting in IoT Hub

Correct Answer: C.

Option A is incorrect because the Event Grid integration is not available through message routing.

Message routes can only be created for the built-in endpoint and for Storage Containers, Event Hubs and Service Bus.

Option B is incorrect because Logic App is not a message routing endpoint.

Message routes can only be created for the built-in endpoint and for Storage Containers, Event Hubs and Service Bus.

Option C is CORRECT because if you want to send enriched telemetry data through Event Grid, you need to configure an IoT Hub event subscription (linked to your Logic App topic), which, in the background, creates a message route to Event Grid.

When it is done, you can already add a query and message enrichments to this route as you would so for any other endpoints.

Option D is incorrect because Alerts are designed for monitoring the health and performance of the IoT Hub.

They are not suitable for the given use case.

References:

Based on the given scenario, the goal is to ensure secure and uninterrupted operation of an industrial IoT solution, consisting of multiple field devices. In case of extreme telemetry data values from certain devices, an alert must be triggered immediately. To accomplish this, Event Grid integration is to be used to forward enriched device telemetry data to a Logic App workflow for further processing (evaluation, alerting, etc.).

To achieve this goal, the following steps need to be taken:

Step 1: Create an Event Grid Subscription The first step is to create an Event Grid subscription to the IoT Hub that is receiving telemetry data from the field devices. An Event Grid subscription allows you to route events to various endpoints such as Azure Functions, Logic Apps, Event Hubs, etc. To create an Event Grid subscription, you need to provide a name for the subscription, a resource group, and the name of the IoT Hub.

Step 2: Configure a Custom Route to Event Grid Once the Event Grid subscription is created, the next step is to configure a custom route to Event Grid. A custom route allows you to specify the endpoint where the enriched telemetry data will be forwarded. To create a custom route, you need to provide a name for the route, the endpoint URL for Event Grid, and the authentication details (if any).

Step 3: Configure Enrichments to Event Grid Message Route The enriched telemetry data needs to be forwarded to the Logic App for further processing. To achieve this, enrichments need to be added to the Event Grid message route. Enrichments allow you to add additional metadata to the telemetry data, which can be used by the Logic App for further processing. For example, you can add a timestamp or a device ID to the telemetry data.

Step 4: Create a Logic App Workflow The next step is to create a Logic App workflow for processing the enriched telemetry data. The Logic App workflow can be used to evaluate the telemetry data and trigger an alert if certain conditions are met. For example, you can evaluate the telemetry data to check if a certain threshold has been exceeded and trigger an alert if it has.

Step 5: Add Enrichments to the Route to Logic App To forward the enriched telemetry data to the Logic App, a custom route needs to be created. Enrichments need to be added to this route as well. These enrichments can be used by the Logic App for further processing.

Based on the above steps, we can eliminate options B, C, and D as they do not follow the correct sequence of steps. Option A is the correct answer as it includes all the necessary steps in the correct order.