Bird
Raised Fist0
GCPcloud~30 mins

Project configuration in GCP - Mini Project: Build & Apply

Choose your learning style10 modes available

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
GCP Project Configuration Basics
📖 Scenario: You are setting up a new Google Cloud Platform (GCP) project for a small business. This project will host their website and store data securely.
🎯 Goal: Learn how to configure a GCP project by creating a project dictionary, setting a billing account, enabling APIs, and adding labels for organization.
📋 What You'll Learn
Create a dictionary named gcp_project with specific project details
Add a billing account ID as a configuration variable
Enable a list of APIs using a loop
Add labels to the project dictionary for better organization
💡 Why This Matters
🌍 Real World
Setting up and configuring cloud projects is a common task when starting new applications or services in GCP.
💼 Career
Cloud engineers and administrators often configure projects, billing, and APIs to prepare environments for development and production.
Progress0 / 4 steps
1
Create the initial GCP project dictionary
Create a dictionary called gcp_project with these exact entries: 'project_id': 'my-sample-project', 'name': 'Sample Project', and 'region': 'us-central1'.
GCP
Hint

Use curly braces to create a dictionary and include the keys and values exactly as shown.

2
Add the billing account ID configuration
Add a variable called billing_account_id and set it to the string '0123-4567-89AB'.
GCP
Hint

Assign the billing account ID as a string to the variable named exactly billing_account_id.

3
Enable required APIs for the project
Create a list called apis_to_enable with these exact strings: 'compute.googleapis.com', 'storage.googleapis.com', and 'cloudfunctions.googleapis.com'. Then use a for loop with the variable api to iterate over apis_to_enable.
GCP
Hint

Create the list with the exact API names and write a for loop using api as the loop variable.

4
Add labels to the GCP project dictionary
Add a key 'labels' to the gcp_project dictionary. Set it to another dictionary with these exact entries: 'env': 'development' and 'team': 'devops'.
GCP
Hint

Add the labels key with a nested dictionary inside the existing gcp_project dictionary.

Practice

(1/5)
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