Folders for grouping projects in GCP - Mini Project: Build & Apply

Folders for grouping projects

📖 Scenario: You work in a company that uses Google Cloud Platform (GCP) to manage many projects. To keep things organized, you want to group related projects under folders. This helps your team find and manage projects easily.

🎯 Goal: Create a folder structure in GCP to group projects by department. You will first define a folder, then add a label to it, then list projects under it, and finally set a policy to control access.

📋 What You'll Learn

Create a folder named departments under the organization

Add a label env:production to the folder

List projects under the departments folder

Set an IAM policy binding to allow a user to view projects in the folder

💡 Why This Matters

🌍 Real World

Organizing cloud projects into folders helps companies manage resources better and apply policies consistently.

💼 Career

Cloud engineers and administrators often create folder structures and manage access to keep cloud environments secure and organized.

1

Create a folder named departments

Write a gcloud command to create a folder named departments under the organization with ID 1234567890. Use the command gcloud resource-manager folders create --display-name=departments --organization=1234567890.

GCP

# Your command here

Hint

Use the gcloud resource-manager folders create command with the --display-name and --organization flags.

2

Add a label env:production to the departments folder

Write a gcloud command to add the label env=production to the folder with ID 9876543210. Use the command gcloud resource-manager folders update 9876543210 --update-labels=env=production.

GCP

gcloud resource-manager folders create --display-name=departments --organization=1234567890
# Your command here

Hint

Use the gcloud resource-manager folders update command with the folder ID and the --update-labels flag.

3

List projects under the departments folder

Write a gcloud command to list all projects under the folder with ID 9876543210. Use the command gcloud projects list --filter="parent.id=9876543210".

GCP

gcloud resource-manager folders create --display-name=departments --organization=1234567890
gcloud resource-manager folders update 9876543210 --update-labels=env=production
# Your command here

Hint

Use gcloud projects list with the --filter flag to show projects under the folder.

4

Set an IAM policy binding to allow user user:[e-mail] to view projects in the folder

Write a gcloud command to add the IAM policy binding for the folder with ID 9876543210 to grant the role roles/viewer to the user [e-mail]. Use the command gcloud resource-manager folders add-iam-policy-binding 9876543210 --member='user:[e-mail]' --role='roles/viewer'.

GCP

gcloud resource-manager folders create --display-name=departments --organization=1234567890
gcloud resource-manager folders update 9876543210 --update-labels=env=production
gcloud projects list --filter="parent.id=9876543210"
# Your command here

Hint

Use gcloud resource-manager folders add-iam-policy-binding with the folder ID, member, and role flags.

Practice

1. What is the main purpose of using folders in Google Cloud Platform (GCP)?

easy

A. To create user accounts

B. To group projects for better organization and management

C. To run virtual machines

D. To store files and data like a hard drive

Solution

1. Step 1: Understand folder function in GCP

   Folders are used to group projects logically under an organization or other folders.

2. Step 2: Compare folder purpose with other options

   Folders do not store data, run machines, or create users; those are different services.

3. Final Answer:

   To group projects for better organization and management -> Option B

4. Quick Check:

   Folders organize projects = D [OK]

Hint: Folders group projects, not store data or run machines [OK]

Common Mistakes:

• Confusing folders with storage buckets
• Thinking folders create users
• Assuming folders run virtual machines

2. Which gcloud command correctly creates a folder named Finance under an organization with ID 123456789?

easy

A. gcloud resource-manager folders create --name=Finance --parent=123456789

B. gcloud projects create Finance --organization=123456789

C. gcloud resource-manager folders create --display-name=Finance --organization=123456789

D. gcloud folders create --display-name=Finance --org=123456789

Solution

1. Step 1: Identify correct command syntax for folder creation

   The correct command uses gcloud resource-manager folders create with --display-name and --organization flags.

2. Step 2: Check options for correct flags and command structure

   gcloud resource-manager folders create --display-name=Finance --organization=123456789 matches the correct syntax; others use wrong flags or commands.

3. Final Answer:

   gcloud resource-manager folders create --display-name=Finance --organization=123456789 -> Option C

4. Quick Check:

   Correct gcloud folder create syntax = A [OK]

Hint: Use 'resource-manager folders create' with --display-name and --organization [OK]

Common Mistakes:

• Using 'gcloud projects create' instead of folders
• Using incorrect flags like --name or --org
• Omitting the parent organization flag

3. Given this command:
gcloud resource-manager folders create --display-name=Dev --folder=987654321
What is the parent of the new folder named Dev?

medium

A. Folder with ID 987654321

B. Project with ID 987654321

C. Organization with ID 987654321

D. No parent specified

Solution

1. Step 1: Understand the meaning of --folder flag

   The --folder flag specifies the parent folder ID under which the new folder is created.

2. Step 2: Identify the parent type from the flag

   Since --folder=987654321 is used, the parent is a folder with that ID, not an organization or project.

3. Final Answer:

   Folder with ID 987654321 -> Option A

4. Quick Check:

   --folder flag sets parent folder = C [OK]

Hint: --folder flag means parent is a folder, not organization [OK]

Common Mistakes:

• Confusing --folder with --organization
• Assuming parent is a project
• Ignoring the parent flag

4. You run this command:
gcloud resource-manager folders create --display-name=HR --parent=organizations/123456789
But get an error. What is the likely cause?

medium

A. The user lacks permission to create folders under the organization

B. The flag --parent is invalid; use --organization instead

C. The command requires --folder flag, not --parent

D. The organization ID is incorrect format; should be numeric only

Solution

1. Step 1: Check command syntax for folder creation

   The --parent flag is valid and can accept organization or folder resource names.

2. Step 2: Consider permission issues

   If the command syntax is correct but fails, the most common cause is insufficient permissions to create folders under the organization.

3. Final Answer:

   The user lacks permission to create folders under the organization -> Option A

4. Quick Check:

   Permission errors cause folder creation failure = B [OK]

Hint: Check permissions if syntax and IDs are correct [OK]

Common Mistakes:

• Assuming --parent flag is invalid
• Thinking organization ID format is wrong
• Confusing --folder and --parent flags

5. You want to organize projects for two departments, Sales and Engineering, under your organization. You also want to apply different billing accounts and permissions to each department easily. What is the best way to set this up using folders?

hard

A. Create one folder for all projects and use labels to separate Sales and Engineering

B. Create projects named Sales and Engineering directly under the organization without folders

C. Create billing accounts named Sales and Engineering and assign projects to them without folders

D. Create two folders named Sales and Engineering under the organization, then move projects into each folder

Solution

1. Step 1: Understand folder benefits for grouping and management

   Folders allow grouping projects logically and applying permissions and billing at folder level.

2. Step 2: Evaluate options for organizing projects by department

   Creating separate folders for Sales and Engineering under the organization lets you manage billing and permissions easily per department.

3. Step 3: Compare with other options

   Projects without folders or using labels do not provide folder-level permission and billing management. Billing accounts alone do not organize projects.

4. Final Answer:

   Create two folders named Sales and Engineering under the organization, then move projects into each folder -> Option D

5. Quick Check:

   Folders group projects for billing and permissions = A [OK]

Hint: Use folders per department for easy billing and permission control [OK]

Common Mistakes:

• Skipping folders and relying on labels only
• Assigning billing without folder structure
• Creating projects without grouping