MQTT broker role in IOT Protocols - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the primary role of an MQTT broker?

The MQTT broker acts like a post office that receives messages from devices (publishers) and sends them to other devices (subscribers) that want those messages.

beginner

How does the MQTT broker manage message delivery?

It routes messages based on topics, ensuring only subscribers to a topic receive the messages published to that topic.

intermediate

What happens if a subscriber is offline when the broker receives a message?

The broker can store the message if the subscriber requested it (using Quality of Service levels), then deliver it when the subscriber reconnects.

beginner

Why is the MQTT broker important for device communication?

It simplifies communication by decoupling devices, so publishers and subscribers don’t need to know about each other directly.

intermediate

Can the MQTT broker handle multiple clients at the same time?

Yes, the broker manages many clients simultaneously, handling their subscriptions and message exchanges efficiently.

What does an MQTT broker do?

A Subscribes to topics on behalf of devices

B Publishes messages to devices

C Routes messages between publishers and subscribers

D Stores all messages permanently

The broker routes messages from publishers to subscribers based on topics.

How does the MQTT broker know where to send a message?

A By the message timestamp

B By the message topic

C By the message size

D By the device IP address

The broker uses the topic to route messages to interested subscribers.

What feature allows the broker to deliver messages to offline subscribers later?

A Quality of Service (QoS)

B Encryption

C Topic filtering

D Load balancing

QoS levels let the broker store messages for offline clients and deliver them when they reconnect.

Which of these is NOT a role of the MQTT broker?

A Storing messages temporarily

B Routing messages

C Managing client connections

D Directly controlling devices

The broker does not control devices; it only manages message exchange.

Why is using an MQTT broker better than direct device-to-device communication?

A It reduces the need for devices to know each other

B It increases device battery usage

C It requires devices to connect directly

D It slows down message delivery

The broker decouples devices, so they don’t need direct connections.

Explain the role of an MQTT broker in simple terms.

Think of the broker as a mail sorter for messages.

Describe how the MQTT broker handles messages when a subscriber is offline.

Consider how the broker ensures messages are not lost.

Practice

1. What is the main role of an MQTT broker in IoT communication?

easy

A. To receive messages from devices and forward them to subscribers

B. To generate sensor data for devices

C. To act as a device that publishes messages only

D. To encrypt messages between devices

Solution

1. Step 1: Understand MQTT broker function

   The MQTT broker acts as a middleman that receives messages from publishers and forwards them to subscribers.

2. Step 2: Eliminate incorrect roles

   Generating data, acting only as a publisher, or encrypting messages are not the broker's main roles.

3. Final Answer:

   To receive messages from devices and forward them to subscribers -> Option A

4. Quick Check:

   Broker = message receiver and forwarder [OK]

Hint: Broker forwards messages between devices [OK]

Common Mistakes:

• Thinking broker generates data
• Confusing broker with publisher device
• Assuming broker only encrypts messages

2. Which network port does an MQTT broker usually listen on by default?

easy

A. 8080

B. 22

C. 443

D. 1883

Solution

1. Step 1: Recall default MQTT port

   The MQTT protocol commonly uses port 1883 for unencrypted communication.

2. Step 2: Identify other ports

   Port 8080 is for HTTP alternate, 443 for HTTPS, and 22 for SSH, not MQTT.

3. Final Answer:

   1883 -> Option D

4. Quick Check:

   MQTT default port = 1883 [OK]

Hint: MQTT default port is 1883 [OK]

Common Mistakes:

• Choosing common web ports like 80 or 443
• Confusing MQTT port with SSH port 22
• Assuming MQTT uses random ports

3. Given this MQTT broker behavior: A device publishes a message to topic home/livingroom/temperature. What does the broker do next?

medium

A. Sends the message to all devices regardless of subscription

B. Sends the message to all devices subscribed to home/livingroom/temperature

C. Deletes the message immediately after receiving

D. Saves the message locally and does not forward it

Solution

1. Step 1: Understand topic-based forwarding

   The MQTT broker forwards messages only to devices subscribed to the specific topic.

2. Step 2: Eliminate incorrect behaviors

   Broker does not just save or delete messages without forwarding, nor does it broadcast to all devices.

3. Final Answer:

   Sends the message to all devices subscribed to home/livingroom/temperature -> Option B

4. Quick Check:

   Broker forwards by topic subscription [OK]

Hint: Broker forwards messages only to subscribed topics [OK]

Common Mistakes:

• Assuming broker broadcasts to all devices
• Thinking broker stores messages without forwarding
• Believing broker deletes messages immediately

4. You configured an MQTT broker but devices cannot connect. Which of these is a likely cause?

medium

A. Broker is not listening on the correct port

B. Devices are publishing to the correct topic

C. Broker is forwarding messages correctly

D. Devices have correct subscription filters

Solution

1. Step 1: Check broker listening port

   If the broker is not listening on the expected port (usually 1883), devices cannot connect.

2. Step 2: Understand other options

   Publishing topics, forwarding messages, and subscription filters affect message flow but not initial connection.

3. Final Answer:

   Broker is not listening on the correct port -> Option A

4. Quick Check:

   Connection issue = wrong broker port [OK]

Hint: Check broker port if devices can't connect [OK]

Common Mistakes:

• Blaming topic or subscription before connection
• Ignoring broker network settings
• Assuming forwarding affects connection

5. You want to ensure that an MQTT broker only forwards messages to devices subscribed to topics starting with office/. Which broker feature helps achieve this?

hard

A. Device authentication

B. Message encryption

C. Topic filtering with wildcards

D. Retained messages

Solution

1. Step 1: Understand topic filtering

   MQTT brokers use topic filters with wildcards to forward messages only to matching subscriptions.

2. Step 2: Exclude unrelated features

   Encryption secures data, authentication controls access, and retained messages store last message; none filter topics.

3. Final Answer:

   Topic filtering with wildcards -> Option C

4. Quick Check:

   Topic filtering controls message forwarding [OK]

Hint: Use topic filters with wildcards to control forwarding [OK]

Common Mistakes:

• Confusing encryption with filtering
• Thinking authentication filters topics
• Assuming retained messages control forwarding