Google Cloud IoT concepts in IOT Protocols - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the protocol used by Google Cloud IoT Core for device communication.

IOT Protocols

protocol = "[1]"

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

AMQTT

BSMTP

CFTP

DHTTP

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing HTTP which is heavier and less efficient for IoT messaging.

Confusing FTP or SMTP which are unrelated to IoT device communication.

Google Cloud IoT Core primarily uses MQTT as the protocol for device communication because it is lightweight and efficient for IoT devices.

2fill in blank

medium

Complete the code to define the Google Cloud IoT Core resource that groups devices.

IOT Protocols

device_registry = "projects/my-project/locations/us-central1/registries/[1]"

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

Adevice

BdeviceRegistry

CdeviceGroup

Dregistry

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'deviceRegistry' which is not the exact resource name.

Using 'deviceGroup' which is not a Cloud IoT Core term.

In Google Cloud IoT Core, devices are grouped into a registry, which manages device metadata and communication.

3fill in blank

hard

Fix the error in the device authentication method by completing the code with the correct key format.

IOT Protocols

device_auth = {
  "publicKey": {
    "format": "[1]",
    "key": "BASE64_ENCODED_KEY"
  }
}

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

AES256_PEM

BRSA_PEM

CRSA_X509_PEM

DX509_PEM

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'X509_PEM' which is incomplete and invalid.

Using 'ES256_PEM' which is for elliptic curve keys, not RSA.

The correct format for device public keys in Google Cloud IoT Core is RSA_X509_PEM when using RSA keys in PEM format with X.509 certificates.

4fill in blank

hard

Fill both blanks to create a device configuration update message with the correct fields.

IOT Protocols

{
  "versionToUpdate": [1],
  "binaryData": "[2]"
}

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

A0

B1

CSGVsbG8gd29ybGQ=

DV29ybGQgaGVsbG8=

Attempts:

3 left

💡 Hint

Common Mistakes

Using version 1 which may cause version mismatch errors.

Using non-base64 strings in binaryData causing decoding errors.

The versionToUpdate is usually set to 0 to update the latest version, and binaryData must be base64 encoded, such as "SGVsbG8gd29ybGQ=" which decodes to 'Hello world'.

5fill in blank

hard

Fill all three blanks to define a device telemetry message with topic and payload fields.

IOT Protocols

{
  "topicName": "/devices/[1]/events",
  "payload": "[2]",
  "qos": [3]
}

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

Adevice123

Btemperature=22.5

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using QoS 0 which is at-most-once and may lose messages.

Putting raw text instead of base64 in payload (though here simplified).

The topicName includes the device ID like 'device123'. The payload is the telemetry data, here 'temperature=22.5'. The qos (quality of service) is set to 1 for at-least-once delivery.