300-915 · Question #52
An IoT engineer is working on a connected machines project. Which two protocols must be used during the data provisioning process when data is sent from the shop floor IoT system to the customer's pub
The correct answer is C. MQTT D. AMQP. MQTT (C) is the industry-standard lightweight publish/subscribe protocol designed for constrained IoT devices sending telemetry over unreliable networks - it is natively supported by virtually every public cloud IoT platform (AWS IoT Core, Azure IoT Hub, Google Cloud IoT). AMQP (
Question
An IoT engineer is working on a connected machines project. Which two protocols must be used during the data provisioning process when data is sent from the shop floor IoT system to the customer's public cloud? (Choose two.)
Options
- ACOAP
- BModbus TCP
- CMQTT
- DAMQP
- EOPC-DA
How the community answered
(50 responses)- A4% (2)
- B12% (6)
- C78% (39)
- E6% (3)
Explanation
MQTT (C) is the industry-standard lightweight publish/subscribe protocol designed for constrained IoT devices sending telemetry over unreliable networks - it is natively supported by virtually every public cloud IoT platform (AWS IoT Core, Azure IoT Hub, Google Cloud IoT). AMQP (D) is an enterprise-grade message queuing protocol used for reliable, ordered message delivery between systems, commonly bridging IoT gateways to cloud messaging services like Azure Service Bus or RabbitMQ.
Why the distractors are wrong:
- CoAP (A) is designed for device-to-device communication within constrained local networks, not for cloud data provisioning at scale.
- Modbus TCP (B) is a shop-floor/SCADA protocol for device control and sensor polling - it stops at the machine/PLC layer and is not used to transport data to the cloud.
- OPC-DA (E) is a legacy Windows COM/DCOM-based factory automation protocol; its successor OPC-UA is cloud-relevant, but OPC-DA itself is not used for cloud data provisioning.
Memory tip: Think in two layers - MQTT moves sensor data up to the cloud broker (lightweight, pub/sub), and AMQP moves messages reliably between enterprise services (heavyweight, queuing). Together they cover the full shop-floor-to-cloud pipeline. If you see "cloud data provisioning," reach for the M+A pair.
Topics
Community Discussion
No community discussion yet for this question.