What is the primary role of an MQTT broker in an IoT system?
Think about how messages travel between devices in MQTT.
The MQTT broker acts like a post office, receiving messages from publishers and sending them to subscribers based on topics. It does not store data permanently or control devices directly.
Given the following MQTT broker log snippet, what does it indicate?
Client connected: client123 on topic sensor/temperature
Look for keywords about connection and topic.
The log shows a successful client connection and subscription to a topic, which is typical broker behavior.
Arrange the steps below in the correct order for how an MQTT broker handles a published message.
Think about clients first subscribing, then publishing, then broker processing.
Clients subscribe first to topics, then publish messages. The broker receives these messages and forwards them to subscribers.
An MQTT client fails to connect to the broker and shows the error 'Connection Refused: Not Authorized'. What is the most likely cause?
Focus on the 'Not Authorized' part of the error.
This error means the broker rejected the connection due to bad credentials or missing permissions, not because of network or subscription issues.
Which practice best improves MQTT broker reliability and availability in a critical IoT deployment?
Think about avoiding single points of failure.
Using multiple brokers with load balancing and failover ensures the system stays up even if one broker fails, which is critical for reliability.