Configure Industrial IoT Solution with Modbus Protocol and Edge Device Connectivity
Question
You are building an industrial IoT solution for a manufacturing plant equipped with a number of field devices which communicate using the Modbus protocol.
Because of security and traffic monitoring reasons, you want the devices to connect to the IoT Hub via an edge device.
How would you configure the solution for this scenario?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: A.
Option A is CORRECT because so that the field devices can communicate with the IoT Hub, their protocols need to be translated.
This translation role can be played by a protocol translation gateway.
In this case, the devices don't have IoT Hub identities.
Option B is incorrect because the Modbus devices cannot communicate with the IoT Hub directly.
Protocol translation is needed and the devices must be connected to the IoT Hub through the edge gateway device.
Therefore, transparent gateways are not suitable for the given scenario.
Option C is incorrect because the Modbus devices cannot communicate with the IoT Hub directly.
Protocol translation is needed and the devices must be connected to the IoT Hub through the edge gateway device.
Therefore, transparent gateways are not suitable for the given scenario.
Option D is incorrect because while the translation gateway is the right solution here, there will be no IoT Hub identities created.
Diagram:
/answer/imgz9kNZMsXGfjXKDM1-Wj9zD6dv13TE3-ShpZi5h7_-8dQMeWo6afqbQVO2-4pOboyoyODDe6MoKID-hIP_OP0XC0f-LFYmE2Tm1dEqTOmbTmXH0lAO8ACKuS_Z5sAZ43MPcYn-9cK)
Reference:
In this scenario, the goal is to enable communication between Modbus-based field devices in a manufacturing plant and the Azure IoT Hub while ensuring security and traffic monitoring. To achieve this, an edge device is used as an intermediary between the field devices and the IoT Hub.
The question asks for the correct configuration for this scenario. Let's go through the answer options one by one:
A. No IoT Hub identity is needed for the leaf devices; Use edge as a translation gateway
This answer suggests that no identity is required for the field devices to connect to the IoT Hub, and the edge device acts as a translation gateway. However, this is not a recommended approach because it doesn't provide authentication and authorization for the devices. Without identities, anyone with access to the edge device can potentially connect to the IoT Hub.
B. Create IoT Hub identity for each leaf device; Use edge as a transparent gateway
This option suggests creating an IoT Hub identity for each field device, which enables secure communication between the devices and the IoT Hub. The edge device is configured as a transparent gateway, which allows the field devices to communicate with the IoT Hub directly, without any translation or modification of messages. This is the recommended approach for this scenario as it provides secure and authenticated communication.
C. No IoT Hub identity is needed for the leaf devices; Use edge as a transparent gateway
This answer is similar to option A, suggesting that no identity is required for the field devices. This approach is not recommended for the same reasons stated in option A.
D. Create IoT Hub identities for the leaf devices; Use edge as a translation gateway.
This option suggests creating IoT Hub identities for each field device and using the edge device as a translation gateway. This approach is not recommended because it introduces additional complexity, requires more configuration and management, and may add latency to the communication between the field devices and the IoT Hub.
In summary, option B is the correct configuration for this scenario, as it provides secure and authenticated communication between the field devices and the IoT Hub.