Google Cloud IoT concepts in IOT Protocols - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Google Cloud IoT Core?

Google Cloud IoT Core is a fully managed service that allows you to securely connect, manage, and ingest data from globally dispersed devices.

beginner

What protocols does Google Cloud IoT Core support for device communication?

Google Cloud IoT Core supports MQTT and HTTP protocols for device communication.

intermediate

What is a 'registry' in Google Cloud IoT Core?

A registry is a container in Google Cloud IoT Core that groups devices and manages their configurations and credentials.

intermediate

How does Google Cloud IoT Core ensure secure device connections?

It uses device authentication with public/private key pairs or JSON Web Tokens (JWT) to ensure secure connections.

intermediate

What is the role of Cloud Pub/Sub in Google Cloud IoT architecture?

Cloud Pub/Sub acts as a messaging service that receives data from devices via IoT Core and routes it to other Google Cloud services for processing.

Which protocols are supported by Google Cloud IoT Core for device communication?

A TCP and UDP

B FTP and SMTP

C MQTT and HTTP

D SSH and Telnet

Google Cloud IoT Core supports MQTT and HTTP protocols for device communication.

What is the purpose of a device registry in Google Cloud IoT Core?

A To store device firmware

B To group devices and manage their credentials

C To host device web pages

D To provide device GPS location

A registry groups devices and manages their configurations and credentials.

How does Google Cloud IoT Core authenticate devices?

A Using public/private key pairs or JWT

B Using username and password only

C Using IP address filtering

D Using biometric data

Devices authenticate using public/private key pairs or JSON Web Tokens (JWT).

What role does Cloud Pub/Sub play in Google Cloud IoT?

A It provides device GPS tracking

B It stores device firmware

C It manages device credentials

D It routes device data to other services

Cloud Pub/Sub routes data from devices to other Google Cloud services.

Which of these is NOT a feature of Google Cloud IoT Core?

A Device firmware hosting

B Secure device connection

C Device management

D Data ingestion

Google Cloud IoT Core does not host device firmware; it manages devices and ingests data.

Explain how Google Cloud IoT Core manages device security and authentication.

Think about how devices prove their identity to the cloud.

Describe the data flow from a device to Google Cloud services using Google Cloud IoT Core.

Follow the path of data from device to cloud.

Practice

1. What is the main purpose of a device registry in Google Cloud IoT?

easy

A. To organize and manage devices by project and region

B. To store device data permanently

C. To provide internet access to devices

D. To update device firmware automatically

Solution

1. Step 1: Understand device registry role

   A device registry groups devices logically, usually by project and region, to manage them easily.

2. Step 2: Compare options with registry function

   Only To organize and manage devices by project and region matches the purpose of organizing and managing devices by project and region.

3. Final Answer:

   To organize and manage devices by project and region -> Option A

4. Quick Check:

   Device registry = Organize devices [OK]

Hint: Registries group devices by project and location [OK]

Common Mistakes:

• Thinking registries store device data
• Confusing registries with device firmware update tools
• Assuming registries provide internet access

2. Which of the following is the correct way to authenticate a device in Google Cloud IoT?

easy

A. Using device serial number only

B. Using device IP address only

C. Using device MAC address

D. Using keys or certificates

Solution

1. Step 1: Identify authentication methods in Google Cloud IoT

   Devices authenticate using cryptographic keys or certificates to ensure secure communication.

2. Step 2: Eliminate incorrect options

   IP address, MAC address, or serial number alone do not provide secure authentication.

3. Final Answer:

   Using keys or certificates -> Option D

4. Quick Check:

   Device authentication = Keys or certificates [OK]

Hint: Authentication uses keys or certificates, not addresses [OK]

Common Mistakes:

• Confusing IP or MAC addresses as authentication methods
• Ignoring the need for cryptographic security
• Assuming serial numbers are secure authentication

3. Given a device registry in region 'us-central1' with devices registered, what happens if you try to add a device with the same ID twice?

medium

A. The second device overwrites the first device silently

B. An error occurs indicating duplicate device ID

C. Both devices are registered with the same ID

D. The registry automatically renames the second device

Solution

1. Step 1: Understand device ID uniqueness in registries

   Device IDs must be unique within a registry to avoid conflicts.

2. Step 2: Check behavior on duplicate device ID addition

   Google Cloud IoT returns an error if a device ID already exists in the registry.

3. Final Answer:

   An error occurs indicating duplicate device ID -> Option B

4. Quick Check:

   Duplicate device ID = Error [OK]

Hint: Device IDs must be unique; duplicates cause errors [OK]

Common Mistakes:

• Assuming duplicate devices overwrite existing ones
• Thinking registry renames duplicates automatically
• Believing multiple devices can share one ID

4. You created a device registry but devices cannot connect. Which of these is the most likely cause?

medium

A. Devices are not authenticated with valid keys or certificates

B. The registry region is set to 'us-central1'

C. Device IDs are too long

D. The registry name contains uppercase letters

Solution

1. Step 1: Identify common connection issues

   Devices must authenticate with valid keys or certificates to connect securely.

2. Step 2: Evaluate other options

   Region setting, device ID length, or registry name case do not prevent connection if authentication is correct.

3. Final Answer:

   Devices are not authenticated with valid keys or certificates -> Option A

4. Quick Check:

   Connection failure = Authentication issue [OK]

Hint: Check device authentication first when connection fails [OK]

Common Mistakes:

• Blaming region or naming conventions for connection issues
• Ignoring authentication as the root cause
• Assuming device ID length causes connection failure

5. You want to securely manage thousands of devices across multiple regions in Google Cloud IoT. Which approach best supports this goal?

hard

A. Create one registry in a single region and use device IP addresses for authentication

B. Create multiple registries but authenticate devices using their MAC addresses

C. Create multiple registries, each in a different region, and use keys or certificates for device authentication

D. Use a single registry and allow devices to connect without authentication

Solution

1. Step 1: Understand scalability and security in Google Cloud IoT

   Multiple registries in different regions help organize devices geographically and improve latency.

2. Step 2: Confirm secure authentication method

   Keys or certificates provide strong device authentication, essential for security.

3. Step 3: Evaluate other options for flaws

   Using IP or MAC addresses is insecure; no authentication risks data breaches.

4. Final Answer:

   Create multiple registries, each in a different region, and use keys or certificates for device authentication -> Option C

5. Quick Check:

   Multiple registries + secure keys = Best practice [OK]

Hint: Use multiple registries and keys for secure, scalable management [OK]

Common Mistakes:

• Using insecure authentication methods like IP or MAC addresses
• Trying to manage all devices in one registry only
• Allowing devices to connect without authentication