Installing and initializing gcloud in GCP - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of the 'gcloud init' command?

After installing the Google Cloud SDK, you run gcloud init. What does this command do?

A It deletes all existing Google Cloud projects linked to your account.

B It installs additional Google Cloud services on your local machine.

C It updates the Google Cloud SDK to the latest version.

D It configures your local environment by setting up authentication, project, and default settings.

💡 Hint

Think about what you need to do after installing a tool to start using it.

The gcloud init command helps you set up your local environment by authenticating your account, selecting a default project, and configuring default settings. It does not install services, delete projects, or update the SDK.

❓ Configuration

intermediate

Which command correctly installs the Google Cloud SDK on a Debian-based Linux system?

You want to install the Google Cloud SDK on your Debian-based Linux machine. Which command sequence is correct?

A yum install google-cloud-sdk

B apt-get install google-cloud-sdk

C curl https://sdk.cloud.google.com | bash

D pip install google-cloud-sdk

💡 Hint

The official installation script is often run via curl and bash.

The recommended way to install the Google Cloud SDK on Debian-based systems is to run the installation script via curl https://sdk.cloud.google.com | bash. The apt-get command requires adding Google Cloud repositories first, which is not shown here. yum is for RedHat-based systems, and pip is not used for this SDK.

❓ Architecture

advanced

What happens if you run 'gcloud auth login' without prior 'gcloud init'?

You installed the Google Cloud SDK but skipped gcloud init. You run gcloud auth login to authenticate. What is the expected behavior?

A It will authenticate and set a default project automatically.

B You will authenticate successfully, but no default project will be set.

C The command will fail because the SDK is not initialized.

D It will automatically run <code>gcloud init</code> for you.

💡 Hint

Authentication and initialization are related but separate steps.

gcloud auth login allows you to authenticate your account independently of gcloud init. However, without gcloud init, no default project or configuration is set, so you must specify projects manually in commands.

❓ security

advanced

Which of the following is a best practice when initializing gcloud on a shared machine?

You are setting up Google Cloud SDK on a shared workstation. Which practice helps keep your credentials secure?

A Use service account keys instead of user credentials for automation.

B Use <code>gcloud auth login --no-launch-browser</code> and manually copy the token.

C Store your credentials in a shared folder accessible by all users.

D Run <code>gcloud init</code> as root user to avoid permission issues.

💡 Hint

Think about automation and least privilege principles.

Using service account keys for automation and shared environments is a best practice because it avoids exposing personal user credentials. Running as root or sharing credentials folders risks security. The --no-launch-browser flag is useful but less secure than service accounts for shared machines.

❓ service_behavior

expert

What is the effect of running 'gcloud config set project [PROJECT_ID]' after initialization?

After running gcloud init, you execute gcloud config set project my-project-123. What does this command do?

A It changes the default project for all subsequent gcloud commands in the current configuration.

B It creates a new Google Cloud project named 'my-project-123'.

C It deletes the previously set default project from your account.

D It logs you out and requires re-authentication.

💡 Hint

Consider what 'config set' commands usually do.

The command gcloud config set project [PROJECT_ID] updates the default project in your current gcloud configuration. It does not create or delete projects, nor does it affect authentication status.

Practice

1. What is the main purpose of installing the gcloud command-line tool on your computer?

easy

A. To replace the Google Cloud Console website

B. To create virtual machines automatically

C. To manage Google Cloud resources directly from your computer

D. To install operating systems on cloud servers

Solution

1. Step 1: Understand what gcloud does

   The gcloud tool is designed to let users control Google Cloud services from their local machine.

2. Step 2: Compare options to the main purpose

   Only To manage Google Cloud resources directly from your computer correctly states that gcloud manages cloud resources from your computer, while others describe unrelated tasks.

3. Final Answer:

   To manage Google Cloud resources directly from your computer -> Option C

4. Quick Check:

   Installing gcloud = Manage cloud from PC [OK]

Hint: Think: local tool to control cloud resources [OK]

Common Mistakes:

• Confusing gcloud with cloud VM creation
• Thinking it replaces the web console
• Assuming it installs OS on servers

2. Which command correctly initializes the gcloud tool after installation?

easy

A. gcloud init

B. gcloud configure

C. gcloud start

D. gcloud setup

Solution

1. Step 1: Recall the initialization command

   The official command to start setup and login for gcloud is gcloud init.

2. Step 2: Verify other options

   Commands like gcloud start, gcloud configure, and gcloud setup do not exist or are incorrect for initialization.

3. Final Answer:

   gcloud init -> Option A

4. Quick Check:

   Initialize gcloud = gcloud init [OK]

Hint: Remember: init means initialize [OK]

Common Mistakes:

• Typing gcloud start instead of gcloud init
• Using non-existent commands like gcloud setup
• Confusing with other CLI tools

3. After running gcloud init, which of the following happens?

medium

A. You are prompted to log in to your Google account

B. Your cloud project is automatically deleted

C. The tool installs a new operating system

D. Your local files are uploaded to the cloud

Solution

1. Step 1: Understand the purpose of gcloud init

   This command helps you log in and select your Google Cloud project.

2. Step 2: Evaluate the options

   Only You are prompted to log in to your Google account correctly describes the login prompt. Other options describe unrelated or harmful actions.

3. Final Answer:

   You are prompted to log in to your Google account -> Option A

4. Quick Check:

   gcloud init = login prompt [OK]

Hint: Init means login and setup project [OK]

Common Mistakes:

• Thinking it deletes projects
• Assuming it installs OS
• Believing it uploads local files automatically

4. You ran gcloud init but got an error saying 'command not found'. What is the most likely cause?

medium

A. You typed the command correctly but your internet is down

B. You did not install the gcloud tool before running the command

C. Your Google Cloud project is inactive

D. You need to restart your computer after running gcloud init

Solution

1. Step 1: Analyze the error message

   'command not found' means the system does not recognize the command, usually because the tool is not installed or not in the system path.

2. Step 2: Check other options

   Internet issues or project status do not cause this error. Restarting computer is not required before installation.

3. Final Answer:

   You did not install the gcloud tool before running the command -> Option B

4. Quick Check:

   'command not found' = tool missing [OK]

Hint: Error means tool not installed or path missing [OK]

Common Mistakes:

• Blaming internet for 'command not found'
• Thinking project status affects command recognition
• Restarting computer unnecessarily

5. You want to set up gcloud for a new project and ensure you can switch projects easily later. Which sequence of commands should you run after installing gcloud?

hard

A. Run gcloud login to log in, then gcloud project select [PROJECT_ID] to choose a project

B. Run gcloud configure to set up, then gcloud project change [PROJECT_ID] to switch projects

C. Run gcloud start to initialize, then gcloud switch project [PROJECT_ID] to change projects

D. Run gcloud init to log in and select a project, then use gcloud config set project [PROJECT_ID] to switch projects

Solution

1. Step 1: Identify correct initialization command

   The correct command to start setup is gcloud init, which logs you in and lets you pick a project.

2. Step 2: Identify how to switch projects

   To switch projects later, the command is gcloud config set project [PROJECT_ID]. Other commands listed do not exist or are incorrect.

3. Final Answer:

   Run gcloud init to log in and select a project, then use gcloud config set project [PROJECT_ID] to switch projects -> Option D

4. Quick Check:

   Init + config set project = setup and switch [OK]

Hint: Use gcloud init then gcloud config set project [OK]

Common Mistakes:

• Using non-existent commands like gcloud login
• Trying commands like gcloud start or gcloud switch project
• Confusing project switching commands