Azure IoT Hub Message Routing with Enrichment Options | Exam AZ-220

Does IoT Hub Message Routing with Enrichment Options Help Achieve the Goal?

Question

You are building an industrial IoT solution where using several IoT hubs, you collect telemetry data from several field sensors.

The ingested data must be distributed through a Service Bus, so you need to establish a route to forward messages from your IoT hubs to a Service Bus topic.

Besides, each message needs to be stamped with the name of the IoT hub ($iothubname) which it originates from, in order to enable further classification.

You decide to use IoT hub's message routing with enrichment options.

Does it help you to achieve your goal?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

Correct Answer: A.

Option A is CORRECT because, with IoT hub's routing capability, you can forward incoming messages to other Azure services as custom endpoints, like Blob Storage or Service Bus.

Enrichment of message also can be applied as part of the routing.

Option B is incorrect Azure Service Bus (both topics and queues) are possible custom endpoints for IoT Hub, hence they are valid targets in message routing.

References:

Yes, using IoT Hub's message routing with enrichment options can help achieve the goal of forwarding telemetry data from IoT hubs to a Service Bus topic and stamping each message with the name of the IoT hub ($iothubname) it originates from for further classification.

IoT Hub's message routing with enrichment options allows you to specify routes that enable you to forward messages from IoT hubs to different endpoints, such as Azure Service Bus, Event Hubs, and Blob Storage. Additionally, you can use message enrichment to add custom properties to the messages based on IoT Hub metadata, such as device ID, IoT hub name, and timestamp.

In this scenario, you can use IoT Hub's message routing with enrichment options to forward the telemetry data from each IoT hub to a Service Bus topic. By using message enrichment, you can add a custom property that stamps each message with the name of the IoT hub ($iothubname) it originates from. This enables further classification of the telemetry data based on the originating IoT hub.

Overall, IoT Hub's message routing with enrichment options can help you achieve the goal of distributing telemetry data through a Service Bus topic while stamping each message with the name of the IoT hub it originates from for further classification.