Cloud Shell and gcloud CLI in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all active projects using gcloud CLI.

GCP

gcloud [1] list

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

Aprojects

Bconfig

Cauth

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' instead of 'projects' will try to create a project, not list them.

Using 'config' or 'auth' commands won't list projects.

The gcloud projects list command lists all active projects you have access to.

2fill in blank

medium

Complete the code to set the default project in gcloud CLI.

GCP

gcloud config set [1] my-project-id

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

Aaccount

Bproject

Czone

Dregion

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'account' sets the user account, not the project.

Using 'zone' or 'region' sets location, not the project.

Setting the default project tells gcloud which project to use for commands.

3fill in blank

hard

Fix the error in the command to authenticate gcloud CLI with your Google account.

GCP

gcloud [1] login

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

Aprojects

Bconfig

Cauth

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'config login' is invalid.

Using 'projects login' is invalid.

Using 'init' starts configuration but is not the direct login command.

The correct command to authenticate is gcloud auth login.

4fill in blank

hard

Fill both blanks to create a new Compute Engine VM instance named 'my-vm' in zone 'us-central1-a'.

GCP

gcloud compute instances [1] my-vm --zone=[2]

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

Acreate

Bdelete

Cus-central1-a

Dus-east1-b

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' instead of 'create' will remove instances.

Using the wrong zone will cause errors or create VM in a different location.

Use create to make a new instance and specify the correct zone us-central1-a.

5fill in blank

hard

Fill all three blanks to list all VM instances in the project with detailed information and filter by zone 'europe-west1-b'.

GCP

gcloud compute instances list --filter="zone:[1]" --format=[2] --project=[3]

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

Aus-central1-a

Btable

Cmy-project-id

Deurope-west1-b

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong zone filter will show no or wrong results.

Omitting the project ID may cause errors if default project is not set.

Using incorrect format will change output style.

Filter by zone europe-west1-b, format output as a table, and specify your project ID.

Practice

1. What is the primary purpose of Google Cloud Shell?

easy

A. To create graphical user interfaces for cloud services

B. To provide a browser-based command-line interface pre-configured for Google Cloud

C. To store large amounts of data in the cloud

D. To host virtual machines for running applications

Solution

1. Step 1: Understand Cloud Shell functionality

   Cloud Shell is a tool that gives you a command-line environment in your browser, ready to use with Google Cloud tools.

2. Step 2: Compare options with Cloud Shell purpose

   Options A, B, and C describe other cloud services, not Cloud Shell's main use.

3. Final Answer:

   To provide a browser-based command-line interface pre-configured for Google Cloud -> Option B

4. Quick Check:

   Cloud Shell = browser CLI [OK]

Hint: Cloud Shell is a browser terminal for Google Cloud commands [OK]

Common Mistakes:

• Confusing Cloud Shell with VM hosting
• Thinking Cloud Shell stores data
• Assuming Cloud Shell creates GUIs

2. Which of the following is the correct command to list all active Google Cloud projects using gcloud CLI?

easy

A. gcloud list projects

B. gcloud projects show

C. gcloud projects list

D. gcloud list all-projects

Solution

1. Step 1: Recall gcloud CLI syntax for listing projects

   The correct command to list projects is 'gcloud projects list'.

2. Step 2: Verify other options

   Options A, C, and D do not follow the correct gcloud command structure and will cause errors.

3. Final Answer:

   gcloud projects list -> Option C

4. Quick Check:

   List projects command = gcloud projects list [OK]

Hint: Remember: gcloud <resource> list to show resources [OK]

Common Mistakes:

• Swapping 'list' and 'projects' order
• Using 'show' instead of 'list'
• Adding extra words like 'all-projects'

3. What will be the output of the following command run in Cloud Shell?

gcloud config get-value project

medium

A. An error saying 'command not found'

B. A list of all available projects

C. The current user's email address

D. The currently set Google Cloud project ID

Solution

1. Step 1: Understand the command purpose

   'gcloud config get-value project' retrieves the project ID currently set in gcloud configuration.

2. Step 2: Analyze other options

   A list of all available projects lists projects, which requires 'projects list'. An error saying 'command not found' is incorrect because the command exists. The current user's email address returns user info, not project.

3. Final Answer:

   The currently set Google Cloud project ID -> Option D

4. Quick Check:

   Get project config = current project ID [OK]

Hint: get-value returns current config setting [OK]

Common Mistakes:

• Expecting a list of projects instead of one project
• Confusing project ID with user email
• Assuming command is invalid

4. You run the command gcloud compute instances create my-vm --zone=us-central1-a but get an error saying the zone is invalid. What is the most likely fix?

medium

A. Change the zone to a valid one like us-central1-b

B. Remove the --zone flag completely

C. Use --region instead of --zone

D. Rename the instance to a different name

Solution

1. Step 1: Understand zone error cause

   The error indicates the specified zone 'us-central1-a' is invalid or unavailable in your project or region.

2. Step 2: Fix by choosing a valid zone

   Changing to a valid zone like 'us-central1-b' resolves the error. Removing the flag or using region instead won't fix zone-specific errors. Renaming instance is unrelated.

3. Final Answer:

   Change the zone to a valid one like us-central1-b -> Option A

4. Quick Check:

   Zone error = pick valid zone [OK]

Hint: Check available zones with 'gcloud compute zones list' [OK]

Common Mistakes:

• Removing zone flag instead of correcting it
• Using region flag where zone is required
• Changing instance name instead of zone

5. You want to automate setting the default project in Cloud Shell for multiple users. Which gcloud CLI command sequence correctly sets the project and verifies it?

hard

A. gcloud config set project my-project-id && gcloud config get-value project

B. gcloud projects set my-project-id && gcloud projects get my-project-id

C. gcloud set project my-project-id && gcloud get project

D. gcloud config project set my-project-id && gcloud config project get

Solution

1. Step 1: Identify correct command to set project

   The correct command to set the default project is 'gcloud config set project '.

2. Step 2: Verify project setting

   To verify, use 'gcloud config get-value project' which returns the current project ID.

3. Step 3: Check other options for correctness

   Options B, C, and D use invalid command syntax and will cause errors.

4. Final Answer:

   gcloud config set project my-project-id && gcloud config get-value project -> Option A

5. Quick Check:

   Set and get project config = gcloud config set project my-project-id && gcloud config get-value project [OK]

Hint: Use 'gcloud config set' and 'gcloud config get-value' for config changes [OK]

Common Mistakes:

• Using incorrect command order or syntax
• Confusing 'projects' commands with 'config' commands
• Trying to set project with invalid commands