Why gcloud CLI matters for automation in GCP - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all Compute Engine instances using gcloud CLI.

GCP

gcloud compute instances [1]

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

Adelete

Blist

Ccreate

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' instead of 'list' will try to make a new instance.

Using 'delete' will remove instances, which is risky.

The list command shows all instances in your project. This is useful for automation to check existing resources.

2fill in blank

medium

Complete the code to set the default project for gcloud CLI automation.

GCP

gcloud config [1] project my-project-id

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

Aset

Bget

Cdelete

Dlist

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get' only reads the current setting.

Using 'delete' removes configuration, which is not desired here.

The set command changes the configuration, here setting the default project for future commands.

3fill in blank

hard

Fix the error in the command to create a new Compute Engine instance with automation.

GCP

gcloud compute instances create [1] --zone=us-central1-a

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

Amy-instance

Binstance

Ccreate-instance

D--instance-name

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags like '--instance-name' in place of the name causes errors.

Using generic words like 'instance' is not a valid name.

The instance name should be a simple string without flags. Here, my-instance is the correct name.

4fill in blank

hard

Fill both blanks to automate stopping a Compute Engine instance in a specific zone.

GCP

gcloud compute instances [1] [2] --zone=us-west1-b

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

Astop

Bmy-instance

Cstart

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' instead of 'stop' will turn the instance on.

Using 'delete' removes the instance permanently.

The stop command stops the instance named my-instance. This is useful in automation to save costs.

5fill in blank

hard

Fill all three blanks to automate listing all buckets in a specific project.

GCP

gcloud [1] storage [2] list --project=[3]

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

Aalpha

Bbuckets

Cmy-project-id

Dbeta

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'alpha' instead of 'beta' may not support all commands.

Using 'objects' instead of 'buckets' lists contents inside buckets, not buckets themselves.

The beta command group is used here for storage commands. buckets specifies the resource type, and my-project-id sets the project.

Practice

1. Why is the gcloud CLI important for automating tasks in Google Cloud?

easy

A. It only works for monitoring but not for creating resources.

B. It provides a graphical interface for manual resource management.

C. It allows running commands from scripts to manage resources automatically.

D. It replaces the need for any cloud account credentials.

Solution

1. Step 1: Understand automation needs

   Automation requires running commands without manual input, often via scripts.

2. Step 2: Role of gcloud CLI in automation

   The gcloud CLI lets you run commands from scripts to create, update, or delete cloud resources automatically.

3. Final Answer:

   It allows running commands from scripts to manage resources automatically. -> Option C

4. Quick Check:

   Automation needs command-line scripting = A [OK]

Hint: Automation means scripts run commands without clicking [OK]

Common Mistakes:

• Confusing CLI with graphical tools
• Thinking gcloud CLI only monitors resources
• Believing it removes need for credentials

2. Which of the following is the correct syntax to list all Compute Engine instances using gcloud CLI?

easy

A. gcloud compute list instances

B. gcloud list compute instances

C. gcloud instances compute list

D. gcloud compute instances list

Solution

1. Step 1: Recall gcloud CLI command structure

   Commands follow the pattern: gcloud [service] [resource] [action].

2. Step 2: Apply to Compute Engine instances listing

   Service is 'compute', resource is 'instances', action is 'list', so command is 'gcloud compute instances list'.

3. Final Answer:

   gcloud compute instances list -> Option D

4. Quick Check:

   gcloud + compute + instances + list = D [OK]

Hint: Remember command order: gcloud service resource action [OK]

Common Mistakes:

• Mixing order of service, resource, and action
• Using 'list' before resource name
• Adding extra words not in syntax

3. What will be the output of this command sequence?

gcloud config set project my-project
gcloud compute instances list

medium

A. Lists instances from the default project, ignoring 'my-project'.

B. Lists all instances in the 'my-project' project.

C. Shows an error because project is not set.

D. Deletes all instances in 'my-project'.

Solution

1. Step 1: Set project context with gcloud config

   The command 'gcloud config set project my-project' sets the active project for future commands.

2. Step 2: List instances in the set project

   'gcloud compute instances list' lists instances in the currently active project, which is 'my-project'.

3. Final Answer:

   Lists all instances in the 'my-project' project. -> Option B

4. Quick Check:

   Set project then list instances = C [OK]

Hint: Set project first, then commands use it automatically [OK]

Common Mistakes:

• Assuming project is not set after config command
• Thinking list command deletes resources
• Ignoring project context in commands

4. You wrote this script to create a VM instance:

gcloud compute instances create my-vm --zone=us-central1-a --machine-type=n1-standard-1

But it fails with an error about missing authentication. What is the likely fix?

medium

A. Run gcloud auth login to authenticate your account.

B. Change the zone to a valid one.

C. Add --project flag to specify the project.

D. Use gcloud config set compute/zone instead.

Solution

1. Step 1: Identify error cause - missing authentication

   The error indicates the CLI does not have permission to act on your behalf.

2. Step 2: Authenticate using gcloud auth login

   Running 'gcloud auth login' opens a browser to sign in and grant permissions.

3. Final Answer:

   Run gcloud auth login to authenticate your account. -> Option A

4. Quick Check:

   Authentication error fixed by login = A [OK]

Hint: Authentication errors need 'gcloud auth login' first [OK]

Common Mistakes:

• Changing zone without fixing auth
• Adding project flag without login
• Confusing config set zone with auth

5. You want to automate creating multiple VM instances in different zones using a script. Which approach best uses gcloud CLI for this automation?

hard

A. Write a shell script that loops over zones and runs gcloud compute instances create with each zone.

B. Manually run gcloud compute instances create for each zone one by one.

C. Use the Google Cloud Console web UI to create instances in each zone.

D. Create instances only in the default zone without specifying zones.

Solution

1. Step 1: Understand automation goal

   Automating means running commands automatically without manual repetition.

2. Step 2: Use scripting with gcloud CLI

   A script looping over zones and calling 'gcloud compute instances create' automates instance creation efficiently.

3. Step 3: Compare other options

   Manual runs or using web UI are not automation. Creating only in default zone ignores requirement.

4. Final Answer:

   Write a shell script that loops over zones and runs gcloud compute instances create with each zone. -> Option A

5. Quick Check:

   Scripting loops + gcloud commands = B [OK]

Hint: Automate repeated tasks with scripts looping gcloud commands [OK]

Common Mistakes:

• Trying manual commands instead of scripting
• Ignoring zone differences in automation
• Relying on UI for automation