Bird
Raised Fist0
GCPcloud~5 mins

GCP Console walkthrough - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
The GCP Console is a web interface that helps you manage your Google Cloud resources easily. It solves the problem of managing cloud services without needing to use complex commands.
When you want to create a new virtual machine without using command line tools
When you need to check the status of your cloud resources quickly
When you want to monitor usage and billing information in one place
When you want to configure access permissions for your team members
When you want to deploy a simple app using Google Cloud services with guided steps
Commands
This command opens a browser window to log in to your Google account and authenticate your CLI session with GCP.
Terminal
gcloud auth login
Expected OutputExpected
Go to the following link in your browser: https://accounts.google.com/o/oauth2/auth?... You are now logged in as [your-email@example.com].
This command lists all the Google Cloud projects you have access to, helping you choose which project to work on.
Terminal
gcloud projects list
Expected OutputExpected
PROJECT_ID NAME PROJECT_NUMBER my-sample-project Sample Project 123456789012
This command shows all the virtual machine instances running in your current project, so you can see what resources are active.
Terminal
gcloud compute instances list
Expected OutputExpected
NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS example-vm us-central1-a e2-medium false 10.128.0.2 34.68.123.45 RUNNING
This command creates a new virtual machine named example-vm in the specified zone with a medium machine type.
Terminal
gcloud compute instances create example-vm --zone=us-central1-a --machine-type=e2-medium
Expected OutputExpected
Created [https://www.googleapis.com/compute/v1/projects/my-sample-project/zones/us-central1-a/instances/example-vm]. NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS example-vm us-central1-a e2-medium false 10.128.0.3 34.68.123.46 RUNNING
→
--zone - Specifies the location where the VM will run
→
--machine-type - Defines the size and power of the VM
This command deletes the example-vm virtual machine without asking for confirmation, cleaning up resources you no longer need.
Terminal
gcloud compute instances delete example-vm --zone=us-central1-a --quiet
Expected OutputExpected
Deleted [https://www.googleapis.com/compute/v1/projects/my-sample-project/zones/us-central1-a/instances/example-vm].
→
--quiet - Skips confirmation prompt to delete immediately
Key Concept

If you remember nothing else, remember: the GCP Console and gcloud CLI let you manage cloud resources easily without complex setup.

Common Mistakes
Trying to create a VM without specifying the zone
The command fails because GCP needs to know where to place the VM physically.
Always include the --zone flag with a valid zone like us-central1-a.
Not logging in before running gcloud commands
Commands fail because you are not authenticated to access your cloud resources.
Run 'gcloud auth login' first to authenticate your session.
Deleting a VM without the --quiet flag and expecting no prompt
The command pauses asking for confirmation, which can interrupt scripts.
Use --quiet to skip confirmation when you want automated deletion.
Summary
Use 'gcloud auth login' to authenticate your Google Cloud session.
List projects and resources with 'gcloud projects list' and 'gcloud compute instances list'.
Create and delete virtual machines with 'gcloud compute instances create' and 'gcloud compute instances delete'.

Practice

(1/5)
1. What is the primary purpose of the GCP Console?
easy
A. To install software on your local computer
B. To manage and control Google Cloud resources through a web interface
C. To write and run code directly on Google Cloud servers
D. To create offline backups of your cloud data

Solution

  1. Step 1: Understand what GCP Console offers

    The GCP Console is a website that lets users manage cloud resources like virtual machines and storage.

  2. Step 2: Identify the main function

    It provides a web interface to create, view, and control cloud services, not to write code or install software locally.

  3. Final Answer:

    To manage and control Google Cloud resources through a web interface -> Option B

  4. Quick Check:

    GCP Console = Manage cloud resources [OK]
Hint: Remember: Console means web control panel [OK]
Common Mistakes:
  • Confusing GCP Console with coding environment
  • Thinking it installs software locally
  • Assuming it creates offline backups
2. Which section in the GCP Console would you visit to check your current billing and costs?
easy
A. Compute Engine
B. IAM & Admin
C. Billing
D. Cloud Storage

Solution

  1. Step 1: Locate billing information in GCP Console

    The Billing section is dedicated to showing your current costs and billing details.

  2. Step 2: Differentiate from other sections

    IAM & Admin manages permissions, Compute Engine manages virtual machines, and Cloud Storage manages files, so they don't show billing.

  3. Final Answer:

    Billing -> Option C

  4. Quick Check:

    Billing section = Costs info [OK]
Hint: Look for 'Billing' to find cost details fast [OK]
Common Mistakes:
  • Choosing Compute Engine for billing info
  • Confusing IAM & Admin with billing
  • Selecting Cloud Storage instead of Billing
3. You want to create a new virtual machine in GCP Console. Which menu path should you follow?
medium
A. Navigation menu > Cloud Storage > Buckets > Create Bucket
B. Navigation menu > Billing > Reports > Create Report
C. Navigation menu > IAM & Admin > Service Accounts > Create Service Account
D. Navigation menu > Compute Engine > VM instances > Create Instance

Solution

  1. Step 1: Identify where virtual machines are managed

    Virtual machines are managed under Compute Engine in the GCP Console.

  2. Step 2: Follow the correct menu path

    To create a VM, go to Compute Engine, then VM instances, and click Create Instance.

  3. Final Answer:

    Navigation menu > Compute Engine > VM instances > Create Instance -> Option D

  4. Quick Check:

    Create VM = Compute Engine > VM instances > Create [OK]
Hint: VMs live under Compute Engine menu [OK]
Common Mistakes:
  • Choosing Cloud Storage for VM creation
  • Confusing Service Accounts with VM setup
  • Looking in Billing for VM options
4. You tried to create a new storage bucket but received an error. What is a common reason for this in the GCP Console?
medium
A. You did not select a unique bucket name
B. You forgot to write code in the console
C. You did not install the GCP Console app
D. You tried to create a VM instead of a bucket

Solution

  1. Step 1: Understand bucket naming rules

    Storage bucket names must be unique across all users worldwide.

  2. Step 2: Identify common error cause

    If the name is already taken, the console shows an error preventing creation.

  3. Final Answer:

    You did not select a unique bucket name -> Option A

  4. Quick Check:

    Bucket name uniqueness = creation success [OK]
Hint: Bucket names must be unique globally [OK]
Common Mistakes:
  • Thinking code is needed in the console
  • Believing an app install is required
  • Mixing up VM creation with bucket creation
5. You want to monitor your project's resource usage and costs in one place. Which GCP Console feature should you use?
hard
A. Cloud Monitoring dashboard combined with Billing reports
B. Compute Engine VM instances page
C. Cloud Storage bucket list
D. IAM & Admin user permissions page

Solution

  1. Step 1: Identify monitoring and cost tracking tools

    Cloud Monitoring dashboard shows resource usage metrics, and Billing reports show cost details.

  2. Step 2: Combine these features for full overview

    Using both together in the console gives a complete picture of usage and costs.

  3. Final Answer:

    Cloud Monitoring dashboard combined with Billing reports -> Option A

  4. Quick Check:

    Monitor usage + costs = Cloud Monitoring + Billing [OK]
Hint: Use Monitoring plus Billing for full project overview [OK]
Common Mistakes:
  • Looking only at VM instances for costs
  • Checking storage buckets for usage stats
  • Confusing permissions page with monitoring