MQTT keep-alive and timeout in IOT Protocols - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding MQTT Keep-Alive Interval

What is the primary purpose of the MQTT keep-alive interval in a client connection?

A To specify how often the client must send a message to the broker to confirm it is alive

B To set the maximum size of messages the client can send

C To determine the quality of service level for message delivery

D To configure the encryption method used for the connection

💡 Hint

Think about how the broker knows if the client is still connected.

The keep-alive interval tells the client how often it must send a message (like a ping) to the broker to show it is still connected. This helps the broker detect if the client has disconnected unexpectedly.

💻 Command Output

intermediate

Detecting MQTT Client Timeout

Given the MQTT broker log snippet below, what does it indicate about the client connection?

Client client123 timed out, disconnecting

A The client sent a malformed message causing disconnection

B The client did not send any message within the keep-alive timeout period

C The broker rejected the client due to authentication failure

D The client requested to disconnect gracefully

💡 Hint

Timeout usually means no response was received in time.

This log means the broker did not receive any message from the client within the expected keep-alive timeout period, so it disconnected the client assuming it is offline.

❓ Configuration

advanced

Configuring MQTT Keep-Alive in mosquitto.conf

Which configuration line correctly sets the maximum keep-alive interval to 120 seconds in the mosquitto broker configuration file?

A max_keepalive 120

B default_keepalive = 120

C keep_alive_timeout 120

D keepalive_timeout=120s

💡 Hint

Check the official mosquitto configuration syntax for keepalive.

The correct syntax in mosquitto.conf to set the maximum keep-alive interval is max_keepalive 120. Other options are invalid or do not exist.

❓ Troubleshoot

advanced

Troubleshooting Unexpected MQTT Client Disconnects

A client frequently disconnects with a 'keep-alive timeout' error. Which of the following is the most likely cause?

A The client is using an unsupported MQTT protocol version

B The broker is overloaded and drops connections randomly

C The client is not sending any packets within the keep-alive interval

D The client certificate has expired

💡 Hint

Focus on what triggers a keep-alive timeout error specifically.

A keep-alive timeout error means the client did not send any message within the expected interval. Other causes would produce different errors.

🔀 Workflow

expert

Sequence of MQTT Keep-Alive and Timeout Handling

Order the steps the MQTT broker takes when handling a client keep-alive timeout:

A 1,2,4,3

B 1,3,2,4

C 2,1,3,4

D 1,2,3,4

💡 Hint

Think about what happens after the timeout is detected before closing connection.

The broker first waits for a message within the keep-alive interval (1). If none arrives within 1.5 times that interval, it detects a timeout (2). Then it sends a disconnect message to the client (3). Finally, it closes the client connection and frees resources (4).