Project configuration in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

GCP

gcloud config set project [1]

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

Amy-project-id

B--project

Cproject-id

Dset-project

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags like --project instead of the project ID

Typing 'set-project' which is not a valid argument

The command gcloud config set project requires the actual project ID as the argument.

2fill in blank

medium

Complete the command to create a new GCP project with the given project ID.

GCP

gcloud projects create [1]

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

A--name

B--project

Cmy-new-project-123

Dcreate-project

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags like --name or --project incorrectly

Typing 'create-project' which is not a valid argument

The gcloud projects create command requires the project ID as a positional argument.

3fill in blank

hard

Fix the error in the command to list all projects.

GCP

gcloud [1] projects list

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

Alist

Bprojects

Ccompute

Dconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'config' or 'compute' which are unrelated command groups here

Using 'list' alone which is not a command group

The correct command to list projects is gcloud projects list.

4fill in blank

hard

Fill both blanks to set the billing account for a project.

GCP

gcloud billing projects link [1] --billing-account=[2]

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

Alink

Bmy-project-123

CbillingAccounts/01A2B3-C4D5E6-F7G8H9

Ddescribe

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'describe' instead of 'link' for billing

Putting the project ID instead of the billing account ID as the second argument

The command gcloud billing projects link [PROJECT_ID] --billing-account=[BILLING_ACCOUNT] links a billing account to a project.

5fill in blank

hard

Fill all three blanks to assign the 'viewer' role to a user on a project.

GCP

gcloud projects add-iam-policy-binding [1] --member='user:[2]' --role='[3]'

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

Amy-project-456

[e-mail]

Croles/viewer

Droles/editor

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'roles/editor' instead of 'roles/viewer' for viewer access

Putting the billing account or other IDs instead of project ID

Using incorrect member format

This command adds the IAM policy binding to give the user the viewer role on the project.

Practice

1. What is the main purpose of a project in Google Cloud Platform?

easy

A. To monitor internet traffic

B. To store user passwords securely

C. To group and organize cloud resources and settings

D. To create virtual machines automatically

Solution

1. Step 1: Understand the role of a project in GCP

   A project acts as a container that holds all your cloud resources and settings together.

2. Step 2: Identify the correct purpose

   Among the options, grouping and organizing resources is the key function of a project.

3. Final Answer:

   To group and organize cloud resources and settings -> Option C

4. Quick Check:

   Project groups resources = D [OK]

Hint: Projects group resources and settings simply [OK]

Common Mistakes:

• Confusing projects with user accounts
• Thinking projects create resources automatically
• Assuming projects monitor traffic

2. Which of the following is the correct way to set a default project using the gcloud CLI?

easy

A. gcloud default project [PROJECT_ID]

B. gcloud project set default [PROJECT_ID]

C. gcloud set project default [PROJECT_ID]

D. gcloud config set project [PROJECT_ID]

Solution

1. Step 1: Recall the gcloud command syntax for setting default project

   The correct command uses 'gcloud config set project' followed by the project ID.

2. Step 2: Compare options

   Only gcloud config set project [PROJECT_ID] matches the correct syntax exactly.

3. Final Answer:

   gcloud config set project [PROJECT_ID] -> Option D

4. Quick Check:

   Set default project with 'config set project' = C [OK]

Hint: Use 'gcloud config set project' to set default [OK]

Common Mistakes:

• Mixing command order or keywords
• Using 'project set default' instead of 'config set project'
• Omitting 'config' keyword

3. Given the following commands run in order:
gcloud config set project my-project-123
gcloud projects describe my-project-123
What will the second command do?

medium

A. Describe the project with ID 'my-project-123' regardless of default project

B. Describe the currently set default project

C. Fail because the project is not set as default

D. List all projects in the account

Solution

1. Step 1: Understand the commands

   The first command sets the default project to 'my-project-123'. The second command describes the project with the given ID explicitly.

2. Step 2: Analyze the behavior of 'gcloud projects describe'

   This command describes the project specified by the ID argument, independent of the default project setting.

3. Final Answer:

   Describe the project with ID 'my-project-123' regardless of default project -> Option A

4. Quick Check:

   'gcloud projects describe' uses given ID, not default project = A [OK]

Hint: 'gcloud projects describe' uses explicit ID, not default [OK]

Common Mistakes:

• Assuming 'describe' uses default project if ID given
• Thinking it lists all projects
• Believing it fails without default project

4. You tried to set the default project with the command:
gcloud set project my-project-123
But it failed. What is the most likely reason?

medium

A. The command syntax is incorrect; 'config' keyword is missing

B. The project ID does not exist

C. You need to be logged in first

D. The project is already set as default

Solution

1. Step 1: Check the command syntax

   The correct command to set default project is 'gcloud config set project [PROJECT_ID]'. The given command misses the 'config' keyword.

2. Step 2: Evaluate other options

   While login and project existence matter, the error is most likely due to wrong syntax here.

3. Final Answer:

   The command syntax is incorrect; 'config' keyword is missing -> Option A

4. Quick Check:

   Missing 'config' in command causes failure = A [OK]

Hint: Remember 'gcloud config set project' syntax [OK]

Common Mistakes:

• Omitting 'config' keyword
• Assuming project existence error without checking syntax
• Ignoring login status

5. You want to create a new project with a unique ID and a friendly name using the gcloud CLI. Which command correctly achieves this?

hard

A. gcloud create project my-new-project --display-name="My Friendly Project"

B. gcloud projects create my-new-project --name="My Friendly Project"

C. gcloud projects new my-new-project --label="My Friendly Project"

D. gcloud project create --id=my-new-project --name="My Friendly Project"

Solution

1. Step 1: Recall the correct command to create a project

   The correct syntax is 'gcloud projects create [PROJECT_ID] --name="Friendly Name"'.

2. Step 2: Compare options to the correct syntax

   Only gcloud projects create my-new-project --name="My Friendly Project" matches the correct command and flag usage.

3. Final Answer:

   gcloud projects create my-new-project --name="My Friendly Project" -> Option B

4. Quick Check:

   Create project with 'projects create' and --name flag = B [OK]

Hint: Use 'gcloud projects create' with --name for friendly name [OK]

Common Mistakes:

• Using wrong command order or flags
• Confusing 'project' and 'projects' commands
• Using --display-name or --label instead of --name