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.