Configuration Steps 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:

In order to implement the scenario described, the following configuration steps should be made in the IoT Hub:

Option A: Create a custom route to Event Grid and configure enrichments to Event Grid message route

• This option involves creating a custom route in the IoT Hub to forward device telemetry data to an Event Grid topic, and configuring enrichments to add additional metadata to the Event Grid message. The enriched data can then be consumed by downstream services like the Logic App workflow for processing and alerting.
• To implement this option, follow these steps:
  1. Create an Event Grid topic in Azure and obtain the endpoint URL.
  2. In the IoT Hub, create a custom route to forward telemetry data to the Event Grid topic.
  3. Configure the custom route to use message enrichments to add additional metadata to the Event Grid message, such as device information, timestamp, and any other relevant data points.
  4. Configure the Logic App workflow to consume events from the Event Grid topic and process the data as needed.

Option B: Create a custom route to telemetryAlert-001 Logic App; add enrichments to the route

• This option involves creating a custom route in the IoT Hub to forward device telemetry data directly to the Logic App workflow, and adding enrichments to the route to include additional metadata in the message payload.
• To implement this option, follow these steps:
  1. Create a Logic App workflow to process telemetry data from the IoT Hub.
  2. In the IoT Hub, create a custom route to forward telemetry data to the Logic App workflow.
  3. Configure the custom route to use message enrichments to add additional metadata to the message payload, such as device information, timestamp, and any other relevant data points.
  4. Configure the Logic App workflow to consume messages from the IoT Hub and process the data as needed.

Option C: Create an event subscription to Logic App topic; add enrichments to Event Grid message route

• This option involves creating an event subscription in Event Grid to consume messages from a Logic App topic, and adding enrichments to the message route to include additional metadata in the message payload.
• To implement this option, follow these steps:
  1. Create a Logic App workflow to process telemetry data from the IoT Hub.
  2. In Event Grid, create an event subscription to consume messages from the Logic App topic.
  3. Configure the event subscription to use message enrichments to add additional metadata to the message payload, such as device information, timestamp, and any other relevant data points.
  4. Configure the Logic App workflow to consume events from the Logic App topic and process the data as needed.

Option D: Create an alert for telemetry data and connect it to an Event Grid topic; add enrichments as needed.

• This option involves creating an alert in the IoT Hub to trigger when telemetry data meets certain criteria, and connecting the alert to an Event Grid topic for consumption by downstream services like the Logic App workflow. Enrichments can be added to the message route to include additional metadata in the message payload.
• To implement this option, follow these steps:
  1. Create an alert in the IoT Hub to trigger when telemetry data meets certain criteria, such as extreme values.
  2. Connect the alert to an Event Grid topic for consumption by downstream services like the Logic App workflow.
  3. Configure the message route to use message enrichments to add additional metadata to the message payload, such as device information, timestamp, and any other relevant data points.
  4. Configure the Logic App workflow to consume events from the Event Grid topic and process the data as needed.

Overall, Option A seems to be the best choice for the scenario described, as it involves