Last Will and Testament (LWT) in IOT Protocols - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of Last Will and Testament (LWT) in MQTT?

In MQTT, the Last Will and Testament (LWT) feature is used to:

A Schedule messages to be sent at a later time

B Authenticate clients before connection

C Encrypt messages between clients

D Notify other clients if a client disconnects unexpectedly

💡 Hint

Think about what happens if a device suddenly loses connection without warning.

LWT allows the broker to send a predefined message to other clients if a client disconnects unexpectedly, signaling an abnormal disconnection.

💻 Command Output

intermediate

What output does this MQTT client command produce regarding LWT?

Consider this MQTT client connection command with LWT settings:

mosquitto_pub -h broker.example.com -t 'status/device1' -m 'offline' --will-topic 'status/device1' --will-message 'offline' --will-qos 1 --will-retain

What happens if the client disconnects unexpectedly?

A Broker publishes 'offline' to 'status/device1' with QoS 0 and no retain

B Broker publishes 'offline' to 'status/device1' with QoS 1 and retain flag set

C Client sends 'offline' message before disconnecting gracefully

D No message is published on unexpected disconnect

💡 Hint

Check the --will-* options for QoS and retain flags.

The --will-topic, --will-message, --will-qos, and --will-retain options define the LWT message that the broker publishes if the client disconnects unexpectedly.

❓ Configuration

advanced

Which MQTT broker configuration snippet correctly enables LWT with a retained message?

Given the following broker configuration options, which snippet correctly sets up LWT to publish a retained message when a client disconnects unexpectedly?

A

will_topic status/client
will_message offline
will_qos 1
will_retain true

B

last_will_topic status/client
last_will_message offline
last_will_qos 1
last_will_retain false

C

will_topic status/client
will_message offline
will_qos 0
will_retain false

D

last_will_topic status/client
last_will_message offline
last_will_qos 2
will_retain true

💡 Hint

Check the exact option names and retain flag value.

The correct broker config uses 'will_topic', 'will_message', 'will_qos', and 'will_retain' with retain set to true to ensure the LWT message is retained.

❓ Troubleshoot

advanced

Why does the LWT message not appear after unexpected client disconnect?

A client sets an LWT message, but when it disconnects unexpectedly, subscribers do not receive the LWT message. What is the most likely cause?

A The client connected with clean session set to true

B The LWT message was set with QoS 2

C The broker does not support LWT

D The client published a retained message before disconnect

💡 Hint

Consider how clean session affects session state and LWT delivery.

If a client connects with clean session true, the broker does not store session information, and LWT messages may not be delivered as expected on disconnect.

🔀 Workflow

expert

Order the steps to correctly implement LWT in an MQTT client connection

Arrange the following steps in the correct order to implement Last Will and Testament (LWT) in an MQTT client connection.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 2,3,1,4

💡 Hint

Think about configuration before connection, then broker behavior.

The client must first define LWT settings, then connect with those settings. The broker stores the LWT info and publishes it if the client disconnects unexpectedly.