Project configuration in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Understanding GCP Project Resource Hierarchy

In Google Cloud Platform, which of the following correctly describes the hierarchy from highest to lowest level for organizing resources?

A Project > Organization > Folder > Resource

B Folder > Organization > Project > Resource

C Organization > Folder > Project > Resource

D Resource > Project > Folder > Organization

💡 Hint

Think about how companies organize their cloud resources from broadest to most specific.

The correct hierarchy is Organization at the top, then Folder, then Project, and finally individual Resources. This helps manage permissions and billing effectively.

❓ security

intermediate

Project IAM Roles Assignment

You want to grant a user the ability to create and manage Compute Engine instances in a specific GCP project. Which IAM role should you assign to the user at the project level?

A roles/compute.admin

B roles/viewer

C roles/editor

D roles/owner

💡 Hint

Consider the principle of least privilege: assign only the permissions needed.

The roles/compute.admin role allows managing Compute Engine resources without granting full project editing or ownership rights.

❓ Configuration

advanced

Configuring Billing Account for a GCP Project

You have created a new GCP project but want to link it to an existing billing account. Which gcloud command correctly links the billing account to the project?

gcloud ...

A gcloud projects set-billing PROJECT_ID --billing-account=BILLING_ACCOUNT_ID

B gcloud billing projects link PROJECT_ID --billing-account=BILLING_ACCOUNT_ID

C gcloud beta billing projects link PROJECT_ID --billing-account=BILLING_ACCOUNT_ID

D gcloud beta projects set-billing PROJECT_ID --billing-account=BILLING_ACCOUNT_ID

💡 Hint

Check the latest gcloud command group for billing project linking.

The correct command uses 'gcloud projects set-billing' to associate a billing account with a project.

✅ Best Practice

advanced

Best Practice for Project Naming Conventions

Which of the following is the best practice for naming GCP projects to ensure clarity and uniqueness?

A Use only the project purpose in uppercase letters

B Use a combination of company name, environment, and project purpose, all lowercase with hyphens

C Use random alphanumeric strings to avoid conflicts

D Use the creator's username and date of creation

💡 Hint

Think about how to make project names meaningful and easy to identify.

Using company name, environment (like dev, prod), and project purpose in lowercase with hyphens helps keep project names clear and unique.

❓ service_behavior

expert

Effect of Deleting a GCP Project on Resources

What happens to the resources and services within a GCP project immediately after you delete the project?

A Only the project metadata is deleted; resources continue running and billing continues.

B The project and all resources are immediately and permanently deleted with no recovery option.

C The project is disabled but resources continue running until manually deleted.

D The project and all its resources enter a 30-day deletion grace period during which they can be recovered; after that, resources are permanently deleted.

💡 Hint

Consider Google's safety measures to prevent accidental data loss.

When a project is deleted, it enters a 30-day grace period where it can be restored. After this period, all resources are permanently deleted.

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