Protocol Buffers (protobuf) in IOT Protocols - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Protocol Buffers message named Person.

IOT Protocols

message Person {
  string name = [1];
}

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

Astring

Bname

C1

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using the field name instead of a number for the tag.

Using zero or negative numbers for the tag.

The number 1 is the field tag number, which uniquely identifies the field in the message.

2fill in blank

medium

Complete the code to declare an integer field called id in a protobuf message.

IOT Protocols

message User {
  [1] id = 1;
}

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

Aint32

Bbool

Cstring

Dfloat

Attempts:

3 left

💡 Hint

Common Mistakes

Using string type for numeric fields.

Using bool or float for integer fields.

The int32 type is used for 32-bit integer fields in protobuf.

3fill in blank

hard

Fix the error in the protobuf field declaration for a repeated string called tags.

IOT Protocols

message Item {
  [1] string tags = 2;
}

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

Arequired

Bsingle

Coptional

Drepeated

Attempts:

3 left

💡 Hint

Common Mistakes

Using optional or required for repeated fields.

Using single which is not a protobuf keyword.

The repeated keyword is used to declare a list of values in protobuf.

4fill in blank

hard

Fill both blanks to define a nested message Address inside Person with a string field city.

IOT Protocols

message Person {
  message [1] {
    [2] city = 1;
  }
}

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

AAddress

Bstring

Cint32

DLocation

Attempts:

3 left

💡 Hint

Common Mistakes

Using int32 for city which is text.

Using wrong nested message name.

The nested message is named Address and the field city is a string type.

5fill in blank

hard

Fill all three blanks to create a map field from string keys to int32 values named scores.

IOT Protocols

message Game {
  map<[1], [2]> [3] = 1;
}

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

Astring

Bint32

Cscores

Dfloat

Attempts:

3 left

💡 Hint

Common Mistakes

Using float instead of int32 for values.

Using wrong field name.

The map field uses string keys and int32 values, named scores.

Practice

1. What is the main purpose of Protocol Buffers (protobuf) in IoT devices?

easy

A. To create graphical user interfaces for IoT devices

B. To organize data into small, typed messages for fast communication

C. To store large video files on IoT devices

D. To replace the operating system on IoT devices

Solution

1. Step 1: Understand Protocol Buffers' role

   Protocol Buffers organize data into messages with typed fields, making data small and fast to send.

2. Step 2: Match purpose to options

   Only To organize data into small, typed messages for fast communication describes organizing data into small, typed messages for fast communication.

3. Final Answer:

   To organize data into small, typed messages for fast communication -> Option B

4. Quick Check:

   Purpose of protobuf = Organize data small and fast [OK]

Hint: Remember protobuf is for small, typed data messages [OK]

Common Mistakes:

• Confusing protobuf with UI tools
• Thinking protobuf stores large files
• Assuming protobuf replaces OS

2. Which of the following is the correct syntax to define a simple protobuf message with an integer field named id?

easy

A. message Device { int32 id = 1; }

B. message Device { int id = 1 }

C. message Device { integer id = 1; }

D. message Device { id int32 = 1; }

Solution

1. Step 1: Recall protobuf field syntax

   Protobuf fields use type name, field name, equals sign, and field number ending with semicolon.

2. Step 2: Check each option

   message Device { int32 id = 1; } matches correct syntax: int32 id = 1;. Others have syntax errors or wrong keywords.

3. Final Answer:

   message Device { int32 id = 1; } -> Option A

4. Quick Check:

   Correct protobuf field syntax = message Device { int32 id = 1; } [OK]

Hint: Field syntax: type name = number; ends with semicolon [OK]

Common Mistakes:

• Omitting semicolon at line end
• Using 'int' instead of 'int32'
• Wrong order of field name and type

3. Given this protobuf message definition:

message SensorData {
  string name = 1;
  int32 value = 2;
}

What will be the output type when you decode a protobuf binary of this message in Python?

medium

A. A Python dict with keys 'name' and 'value'

B. A list containing 'name' and 'value' values

C. A string containing the raw binary data

D. An object with attributes 'name' and 'value'

Solution

1. Step 1: Understand protobuf decoding in Python

   Protobuf generates classes; decoding returns an object with fields as attributes.

2. Step 2: Match output type

   Decoded message is an object with attributes 'name' and 'value', not dict or list.

3. Final Answer:

   An object with attributes 'name' and 'value' -> Option D

4. Quick Check:

   Protobuf decode output = Object with attributes [OK]

Hint: Decoded protobuf = object with fields as attributes [OK]

Common Mistakes:

• Expecting a dict instead of an object
• Thinking output is raw binary string
• Assuming output is a list

4. You wrote this protobuf message:

message Device {
  int32 id = 1
  string name = 2;
}

When compiling, you get a syntax error. What is the problem?

medium

A. Message name cannot be Device

B. Field numbers must start at 0

C. Missing semicolon after id = 1

D. Field names cannot be id

Solution

1. Step 1: Check protobuf field syntax

   Each field line must end with a semicolon.

2. Step 2: Identify error in code

   The line int32 id = 1 misses a semicolon at the end, causing syntax error.

3. Final Answer:

   Missing semicolon after id = 1 -> Option C

4. Quick Check:

   Every field line ends with semicolon [OK]

Hint: Check every field line ends with semicolon [OK]

Common Mistakes:

• Omitting semicolon at end of field
• Wrong field numbering assumptions
• Thinking message names are restricted

5. You want to add a new optional field status (string) to an existing protobuf message without breaking compatibility. Which is the correct way?

hard

A. Add optional string status = 3; to the message

B. Change name field number to 3 and add string status = 2;

C. Remove field value and add string status = 2;

D. Add string status = 1; replacing name

Solution

1. Step 1: Understand protobuf compatibility rules

   Adding new fields with new unique numbers keeps compatibility; changing existing field numbers breaks it.

2. Step 2: Evaluate options

   Add optional string status = 3; to the message adds new optional field with new number 3, safe and compatible. Others change or remove existing fields, breaking compatibility.

3. Final Answer:

   Add optional string status = 3; to the message -> Option A

4. Quick Check:

   Add new field with new number to keep compatibility [OK]

Hint: Add new fields with new numbers, never change existing ones [OK]

Common Mistakes:

• Changing existing field numbers
• Removing existing fields
• Reusing field numbers