Edge-to-cloud data pipeline in IOT Protocols - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to publish data from an edge device using MQTT.

IOT Protocols

client.connect('[1]')

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

Abroker.hivemq.com

Blocalhost

Cexample.com

D192.168.1.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using localhost when the broker is remote

Using an invalid IP address

The MQTT client connects to the public broker at broker.hivemq.com to send data.

2fill in blank

medium

Complete the code to subscribe to a topic on the cloud server.

IOT Protocols

client.subscribe('[1]')

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

Adevice/command

Bsensor/data

Calerts

Dstatus/update

Attempts:

3 left

💡 Hint

Common Mistakes

Subscribing to the wrong topic

Using a topic meant for commands

The client subscribes to the 'sensor/data' topic to receive sensor readings.

3fill in blank

hard

Fix the error in the QoS level setting for MQTT publish.

IOT Protocols

client.publish('sensor/data', payload, qos=[1])

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

A3

B0

C1

D2

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid QoS values like 3

Using QoS 0 when delivery guarantee is needed

QoS levels for MQTT are 0, 1, or 2. Level 1 ensures message delivery at least once.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension filtering sensor readings above threshold.

IOT Protocols

filtered_data = {k: v[1] for k, v in readings.items() if v [2] 50}

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

A**2

B>

C<

D*3

Attempts:

3 left

💡 Hint

Common Mistakes

Using multiplication instead of exponentiation

Using wrong comparison operators

The comprehension squares the values and filters those greater than 50.

5fill in blank

hard

Fill all three blanks to build a dictionary with uppercase keys, values, and filter condition.

IOT Protocols

result = { [1]: [2] for k, v in data.items() if v [3] 10 }

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

Ak.upper()

Bv

C>

Dk.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using k.lower() instead of k.upper()

Using wrong comparison operator

Keys are converted to uppercase, values kept as is, filtering values greater than 10.

Practice

1. What is the main purpose of an edge-to-cloud data pipeline in IoT?

easy

A. To replace cloud servers with edge devices completely

B. To store data only on local devices without sending it anywhere

C. To disconnect devices from the internet for security

D. To send data from local devices to cloud servers for processing and storage

Solution

1. Step 1: Understand the data flow in IoT

   Edge-to-cloud pipelines move data from devices at the edge to cloud servers.

2. Step 2: Identify the purpose of this movement

   This allows data to be processed and stored centrally in the cloud for analysis and safety.

3. Final Answer:

   To send data from local devices to cloud servers for processing and storage -> Option D

4. Quick Check:

   Edge-to-cloud = data transfer to cloud [OK]

Hint: Edge-to-cloud means sending data from devices to cloud [OK]

Common Mistakes:

• Thinking data stays only on local devices
• Confusing edge devices with cloud servers
• Assuming edge devices replace cloud completely

2. Which protocol is commonly used in edge-to-cloud pipelines for lightweight messaging?

easy

A. FTP

B. MQTT

C. SMTP

D. Telnet

Solution

1. Step 1: Identify protocols for IoT messaging

   MQTT is designed for lightweight, low-bandwidth messaging in IoT.

2. Step 2: Compare with other protocols

   FTP is for file transfer, SMTP for email, Telnet for remote login, so they are not ideal for IoT messaging.

3. Final Answer:

   MQTT -> Option B

4. Quick Check:

   Lightweight messaging = MQTT [OK]

Hint: MQTT is lightweight and made for IoT messaging [OK]

Common Mistakes:

• Choosing FTP which is heavy for IoT
• Confusing SMTP with messaging protocol
• Selecting Telnet which is not for messaging

3. Given this MQTT publish command on an edge device:
mosquitto_pub -h broker.example.com -t sensors/temp -m "22.5"
What happens after this command runs successfully?

medium

A. The message "22.5" is sent to the topic sensors/temp on the broker

B. The broker subscribes to the topic sensors/temp

C. The edge device subscribes to sensors/temp topic

D. The message "22.5" is stored locally only

Solution

1. Step 1: Understand the mosquitto_pub command

   This command publishes a message (-m "22.5") to a topic (-t sensors/temp) on the broker (-h broker.example.com).

2. Step 2: Identify the effect of publishing

   Publishing sends the message to the broker under the specified topic for subscribers to receive.

3. Final Answer:

   The message "22.5" is sent to the topic sensors/temp on the broker -> Option A

4. Quick Check:

   Publish sends message to broker topic [OK]

Hint: Publish command sends message to broker topic [OK]

Common Mistakes:

• Confusing publish with subscribe
• Thinking message stays local only
• Assuming broker subscribes automatically

4. An edge device tries to send data using MQTT but gets a connection error. Which fix is most likely correct?

medium

A. Disable the network interface on the edge device

B. Change the message payload to JSON format

C. Check if the MQTT broker address is correct and reachable

D. Increase the message size beyond broker limits

Solution

1. Step 1: Identify cause of connection error

   Connection errors usually happen if the broker address is wrong or unreachable.

2. Step 2: Choose the fix that restores connection

   Verifying and correcting the broker address or network connectivity fixes the issue.

3. Final Answer:

   Check if the MQTT broker address is correct and reachable -> Option C

4. Quick Check:

   Connection error fix = verify broker address [OK]

Hint: Connection errors usually mean wrong broker address [OK]

Common Mistakes:

• Changing message format without fixing connection
• Increasing message size causing more errors
• Disabling network interface disables connection

5. You want to build an edge-to-cloud pipeline that sends sensor data every 10 seconds using MQTT. Which setup is best to ensure data is not lost if the edge device temporarily loses connection?

hard

A. Use MQTT QoS level 1 or 2 with persistent session and local message queue

B. Send data with QoS 0 and no message queue on the device

C. Use HTTP POST requests without retries

D. Send data only when the device boots up

Solution

1. Step 1: Understand MQTT QoS and persistence

   QoS 1 or 2 ensures messages are delivered at least once or exactly once, even if connection drops.

2. Step 2: Use persistent session and local queue

   Persistent sessions and local queues store messages on the device until they can be sent, preventing data loss.

3. Final Answer:

   Use MQTT QoS level 1 or 2 with persistent session and local message queue -> Option A

4. Quick Check:

   Reliable delivery = QoS 1/2 + persistence [OK]

Hint: Use QoS 1/2 and local queue for no data loss [OK]

Common Mistakes:

• Using QoS 0 which can lose messages
• Not queuing messages locally
• Sending data only once or without retries