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?
Click on the arrows to vote for the correct answerA. 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.
Yes, using IoT hub's message routing with enrichment options can help achieve the goal of forwarding telemetry data from multiple IoT hubs to a Service Bus topic and also stamping each message with the name of the IoT hub ($iothubname) from which it originated.
IoT Hub's message routing allows users to route device-to-cloud messages to built-in and custom endpoints such as Service Bus, Event Hubs, and storage accounts based on a set of rules. In this case, the messages need to be routed to a Service Bus topic.
IoT Hub's message enrichment option enables adding or modifying message properties based on the values of other message properties or fixed values. By using this option, users can add a property to each message that identifies the IoT hub that the message originated from. This can be done by adding a new property to the message that carries the value of $iothubname.
So, by combining IoT Hub's message routing and enrichment options, users can route messages from multiple IoT hubs to a Service Bus topic and also stamp each message with the name of the IoT hub from which it originated.