What is the primary purpose of a Device Registry in Google Cloud IoT?
Think about where device information and security settings are kept.
A Device Registry holds metadata about devices, including authentication credentials and communication protocols. It does not process data or act as a physical gateway.
What is the expected output when running the following command to create a device in Google Cloud IoT?
gcloud iot devices create my-device --region=us-central1 --registry=my-registry --project=my-project
Consider the typical JSON response from a successful device creation.
The command outputs a JSON object with device details including id, full resource name, and credentials. Errors or silent success are not typical here.
Arrange the steps in the correct order to connect a new IoT device to Google Cloud IoT Core.
Think about setting up infrastructure before device configuration and data sending.
First, create the registry, then register the device with credentials, configure the device to connect, and finally send data.
A device fails to connect to Google Cloud IoT Core with an authentication error. Which of the following is the most likely cause?
Authentication errors usually relate to credentials or keys.
If the device's public key is missing or incorrect in the registry, authentication will fail. Other options do not cause authentication errors.
Which practice best ensures secure communication between IoT devices and Google Cloud IoT Core?
Security best practices involve authentication and key management.
JWT tokens signed with private keys provide secure authentication. Key rotation improves security. Other options weaken security.