Configure enrichments and message routes
Question
You are building an industrial IoT solution where, using several S1 IoT hubs, you collect telemetry data from a number of field sensors.
The data collected by the IoT hubs must be forwarded to a Blob Storage container and to be published to a Service Bus topic to make them available to consumer services.
Each forwarded message needs to be stamped with the location of the device ($twin.tags.location)
You need to configure the enrichments and the messages routes.
Which items are you recommended to configure?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: D.
Option A is incorrect because the messages/events is the default, built-in endpoint of the IoT hub.
For the given scenario, custom endpoints for Storage and Service Bus should be used.
Option B is incorrect because the Storage Container and the Service Bus are custom endpoints.
You can't configure them as built-in endpoints.
Option C is incorrect because while it is a valid option,the number of enrichments is limited to 10 per IoT hub, it is recommended to optimize their number where possible.
For this scenario, the same enrichment applies to both endpoints, hence one single enrichment does the job.
Option D is CORRECT because both of the targets (Storage and Service Bus) are defined as custom endpoints.
Both of them need to be created beforehand, and then the messages forwarded to them can be stamped in one single enrichment.
Because the number of enrichments is limited to 10 per IoT hub, it is the best solution to optimize their number where possible.
Diagram:
/answer/imgckeditor_48.png)
References:
In order to achieve the requirements of forwarding telemetry data to a Blob Storage container and publishing them to a Service Bus topic, and stamping each message with the device location, we need to configure IoT Hub message routes and message enrichments.
Message routes in IoT Hub allow us to direct messages to different endpoints, such as a Blob Storage container or a Service Bus topic, based on the message properties or message body.
Message enrichments in IoT Hub allow us to add, modify or delete custom properties of the message or its body, based on metadata or data from IoT devices.
Therefore, we need to configure at least one message route and one message enrichment to fulfill the requirement of stamping the device location on each message and forwarding it to both Blob Storage and Service Bus.
Option A suggests configuring two messages/events endpoints and one enrichment, which might not be sufficient to achieve the desired requirements.
Option B suggests configuring two built-in endpoints (likely referring to built-in endpoints for Blob Storage and Service Bus) and two enrichments, which may be overcomplicating the solution since we don't need to modify the messages beyond adding a custom property for the location.
Option C suggests configuring two custom endpoints and two enrichments, which might also be overcomplicating the solution since we don't need custom endpoints to fulfill the requirements.
Option D suggests configuring two custom endpoints and one enrichment, which is a reasonable approach, as we need to configure custom endpoints for Blob Storage and Service Bus, and we only need one enrichment to add the device location tag to the message.
Therefore, the recommended option is D: Two custom endpoints and one enrichment.
