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).

Practice

1. What is the main purpose of the MQTT keep-alive timer?

easy

A. To check if the connection between client and broker is still active

B. To encrypt messages sent between client and broker

C. To increase the message sending speed

D. To store messages on the broker

Solution

1. Step 1: Understand MQTT keep-alive role

   The keep-alive timer is used to monitor connection health by expecting regular messages or pings.

2. Step 2: Identify the purpose from options

   Only To check if the connection between client and broker is still active describes checking if the connection is still active, which matches the keep-alive function.

3. Final Answer:

   To check if the connection between client and broker is still active -> Option A

4. Quick Check:

   Keep-alive checks connection health = D [OK]

Hint: Keep-alive means connection check timer [OK]

Common Mistakes:

• Confusing keep-alive with encryption
• Thinking keep-alive speeds up messages
• Assuming keep-alive stores messages

2. Which of the following is the correct way for an MQTT client to avoid a keep-alive timeout?

easy

A. Send a PINGREQ message before the keep-alive timer expires

B. Disconnect immediately after connecting

C. Send a CONNECT message repeatedly without waiting

D. Ignore the keep-alive timer completely

Solution

1. Step 1: Review MQTT client behavior for keep-alive

   Clients must send any message or a PINGREQ before the keep-alive timer expires to keep the connection alive.

2. Step 2: Match correct action with options

   Send a PINGREQ message before the keep-alive timer expires correctly states sending PINGREQ before timeout; others are incorrect or harmful.

3. Final Answer:

   Send a PINGREQ message before the keep-alive timer expires -> Option A

4. Quick Check:

   Send PINGREQ before timer ends = A [OK]

Hint: Send PINGREQ before timer ends to stay connected [OK]

Common Mistakes:

• Sending CONNECT repeatedly causes errors
• Disconnecting breaks connection
• Ignoring timer causes timeout

3. Given a client with a keep-alive interval of 10 seconds, what happens if the client sends no messages or pings for 15 seconds?

medium

A. The client automatically reconnects

B. The broker waits indefinitely without closing

C. The broker sends a PINGRESP to the client

D. The broker closes the connection due to timeout

Solution

1. Step 1: Understand keep-alive timeout behavior

   If no message or ping is received within the keep-alive interval, the broker considers the client disconnected and closes the connection.

2. Step 2: Analyze the 15-second no message case

   Since 15 seconds > 10 seconds interval, the broker will close the connection due to timeout.

3. Final Answer:

   The broker closes the connection due to timeout -> Option D

4. Quick Check:

   No message > keep-alive interval = connection closed [OK]

Hint: No message past keep-alive means disconnect [OK]

Common Mistakes:

• Thinking broker waits forever
• Assuming client auto reconnects immediately
• Confusing PINGRESP as timeout action

4. A developer sets the MQTT keep-alive interval to 0. What issue will most likely occur?

medium

A. The client will immediately timeout and disconnect

B. The client will never timeout, causing stale connections

C. The broker ignores the keep-alive setting and uses default

D. The client sends continuous PINGREQ messages flooding the broker

Solution

1. Step 1: Understand keep-alive value 0 meaning

   A keep-alive value of 0 turns off the keep-alive mechanism. The broker does not expect PINGREQs and will not timeout the connection based on keep-alive.

2. Step 2: Identify effect on connection

   This can lead to stale connections if the client dies without sending DISCONNECT.

3. Final Answer:

   The client will never timeout, causing stale connections -> Option B

4. Quick Check:

   Keep-alive 0 disables mechanism = no timeout = A [OK]

Hint: Keep-alive 0 disables mechanism, no timeout, risk of stale connections [OK]

Common Mistakes:

• Thinking keep-alive 0 causes immediate timeout
• Assuming broker uses default automatically
• Believing client floods with pings

5. You want to configure an MQTT client to keep the connection alive even if no messages are sent for 30 seconds. Which setting and action combination is correct?

hard

A. Set keep-alive to 10 seconds and send PINGREQ every 40 seconds

B. Set keep-alive to 60 seconds and never send PINGREQ messages

C. Set keep-alive to 30 seconds and send PINGREQ before 30 seconds expire

D. Set keep-alive to 0 and rely on broker to keep connection alive

Solution

1. Step 1: Match keep-alive interval with desired timeout

   To keep connection alive for 30 seconds without messages, set keep-alive to 30 seconds so broker expects activity within that time.

2. Step 2: Ensure client sends PINGREQ before timeout

   Client must send PINGREQ before 30 seconds expire to reset timer and avoid timeout.

3. Final Answer:

   Set keep-alive to 30 seconds and send PINGREQ before 30 seconds expire -> Option C

4. Quick Check:

   Keep-alive = 30s + timely PINGREQ = A [OK]

Hint: Keep-alive time = max wait; send PINGREQ before then [OK]

Common Mistakes:

• Setting keep-alive too low or too high without matching pings
• Not sending PINGREQ within keep-alive interval
• Using 0 disables keep-alive causing disconnect