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.