Last Will and Testament (LWT) in IOT Protocols - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the Last Will and Testament (LWT) topic in an MQTT client.

IOT Protocols

client.will_set(topic=[1], payload="Offline", qos=1, retain=False)

Drag options to blanks, or click blank then click option'

A"home/temperature"

B"home/status"

C"home/light"

D"home/command"

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a sensor data topic instead of a status topic.

The LWT topic is usually a status topic like "home/status" to notify others if the client disconnects unexpectedly.

2fill in blank

medium

Complete the code to set the LWT payload message indicating the client is offline.

IOT Protocols

client.will_set(topic="home/status", payload=[1], qos=1, retain=False)

Drag options to blanks, or click blank then click option'

A"Offline"

B"Online"

C"Connected"

D"Active"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Online' or 'Connected' which indicate the client is active.

The LWT payload should indicate the client is offline when it disconnects unexpectedly.

3fill in blank

hard

Fix the error in the code to correctly set the LWT with retain flag.

IOT Protocols

client.will_set(topic="home/status", payload="Offline", qos=1, retain=[1])

Drag options to blanks, or click blank then click option'

A1

B"True"

CFalse

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using string "True" instead of boolean True.

Using integer 1 instead of boolean.

The retain flag must be a boolean True or False, not a string or integer.

4fill in blank

hard

Fill both blanks to create a dictionary for LWT settings with topic and payload.

IOT Protocols

lwt_settings = {"topic": [1], "payload": [2]

Drag options to blanks, or click blank then click option'

A"home/status"

B"Offline"

C"home/command"

D"Online"

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping topic and payload values.

Using wrong topic or payload strings.

The LWT dictionary should have the topic as "home/status" and payload as "Offline" to notify disconnection.

5fill in blank

hard

Fill all three blanks to set LWT with topic, payload, and QoS level.

IOT Protocols

client.will_set(topic=[1], payload=[2], qos=[3], retain=True)

Drag options to blanks, or click blank then click option'

A"home/status"

B"Offline"

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using QoS 0 which is less reliable.

Using wrong topic or payload.

The LWT should use the status topic, offline payload, and QoS level 1 for reliable delivery.

Practice

1. What is the main purpose of the Last Will and Testament (LWT) in MQTT?

easy

A. To notify other clients if a device disconnects unexpectedly

B. To encrypt messages between devices

C. To store messages for offline clients

D. To authenticate devices connecting to the broker

Solution

1. Step 1: Understand LWT role in MQTT

   LWT is a message set by a client to be sent by the broker if the client disconnects unexpectedly.

2. Step 2: Identify the purpose of LWT

   This helps notify other clients about the unexpected disconnection, improving system reliability.

3. Final Answer:

   To notify other clients if a device disconnects unexpectedly -> Option A

4. Quick Check:

   LWT notifies disconnections [OK]

Hint: LWT alerts others when a device drops connection unexpectedly [OK]

Common Mistakes:

• Confusing LWT with message encryption
• Thinking LWT stores messages for offline clients
• Assuming LWT is for device authentication

2. Which MQTT client method is used to set the Last Will and Testament (LWT) message when connecting?

easy

A. client.publish(topic, message)

B. client.subscribe(topic)

C. client.setWill(topic, message, qos, retain)

D. client.connect()

Solution

1. Step 1: Identify method to set LWT

   The method setWill is used to define the LWT message before connecting.

2. Step 2: Differentiate from other methods

   publish sends normal messages, subscribe listens to topics, and connect starts connection without setting LWT.

3. Final Answer:

   client.setWill(topic, message, qos, retain) -> Option C

4. Quick Check:

   Set LWT with setWill() method [OK]

Hint: LWT is set before connect using setWill() method [OK]

Common Mistakes:

• Using publish() to set LWT
• Trying to set LWT after connecting
• Confusing subscribe() with setting LWT

3. Given this MQTT client code snippet, what will happen if the client disconnects unexpectedly?

client.setWill('status/device1', 'offline', 1, true);
client.connect();

medium

A. The client reconnects automatically

B. The broker publishes 'offline' to 'status/device1' topic

C. The broker deletes the 'status/device1' topic

D. Nothing happens because LWT is not set

Solution

1. Step 1: Analyze setWill parameters

   The LWT is set to publish 'offline' on topic 'status/device1' with QoS 1 and retain flag true.

2. Step 2: Understand broker behavior on unexpected disconnect

   If the client disconnects unexpectedly, the broker sends the LWT message to the specified topic.

3. Final Answer:

   The broker publishes 'offline' to 'status/device1' topic -> Option B

4. Quick Check:

   LWT message sent on unexpected disconnect [OK]

Hint: LWT message publishes on unexpected disconnect [OK]

Common Mistakes:

• Assuming client auto reconnects
• Thinking broker deletes topics on disconnect
• Believing LWT is not set here

4. Identify the error in this MQTT client code snippet related to LWT setup:

client.connect({
  will: {
    topic: 'device/status',
    payload: 'offline'
  }
});

medium

A. Payload should be a JSON object, not string

B. Incorrect topic name format

C. LWT must be set after connecting

D. Missing QoS and retain flags in LWT configuration

Solution

1. Step 1: Review LWT configuration fields

   MQTT LWT requires topic, payload, QoS, and retain flags to be set for proper behavior.

2. Step 2: Identify missing fields

   The code sets topic and payload but omits QoS and retain, which are important for message delivery and persistence.

3. Final Answer:

   Missing QoS and retain flags in LWT configuration -> Option D

4. Quick Check:

   LWT needs QoS and retain flags [OK]

Hint: Always include QoS and retain when setting LWT [OK]

Common Mistakes:

• Ignoring QoS and retain flags
• Setting LWT after connect call
• Assuming payload must be JSON

5. You want to monitor device connectivity using LWT. Which combination of settings ensures the broker retains the last known status and notifies subscribers if the device disconnects unexpectedly?

hard

A. Set LWT with retain=true and QoS=1; publish online status with retain=true

B. Set LWT with retain=false and QoS=0; publish online status without retain

C. Set LWT with retain=true and QoS=0; publish online status with retain=false

D. Set LWT with retain=false and QoS=1; publish online status with retain=true

Solution

1. Step 1: Understand retain flag usage

   Retain=true ensures the broker keeps the last message on the topic for new subscribers.

2. Step 2: Understand QoS role in LWT

   QoS=1 guarantees message delivery at least once, important for reliable LWT notification.

3. Step 3: Combine settings for monitoring

   Publishing online status with retain=true keeps current status; LWT with retain=true and QoS=1 ensures offline status is sent reliably and retained.

4. Final Answer:

   Set LWT with retain=true and QoS=1; publish online status with retain=true -> Option A

5. Quick Check:

   Retain and QoS=1 for LWT and status [OK]

Hint: Use retain=true and QoS=1 for reliable LWT and status messages [OK]

Common Mistakes:

• Setting retain=false loses last status message
• Using QoS=0 risks missing LWT delivery
• Not retaining online status message