Folders for grouping projects in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Folders in GCP Resource Hierarchy

What is the main purpose of using folders in Google Cloud Platform's resource hierarchy?

A To store data files for projects

B To replace projects as the main billing unit

C To host virtual machines directly

D To group projects for applying common policies and permissions

💡 Hint

Think about how folders help organize and manage multiple projects.

Folders in GCP are used to group projects so that you can apply policies and permissions to all projects inside the folder at once. They do not store data or replace projects.

❓ Architecture

intermediate

Correct Folder Structure for Multiple Departments

You have three departments: Sales, Engineering, and Marketing. Each has multiple projects. Which folder structure best supports applying department-specific policies?

A Create one folder per department and place their projects inside

B Place all projects directly under the organization without folders

C Create one folder for all projects regardless of department

D Create folders for each project individually

💡 Hint

Consider how to apply policies easily to all projects in a department.

Creating one folder per department allows you to apply policies to all projects in that department easily. Other options do not group projects by department effectively.

❓ security

advanced

Applying IAM Policies at Folder Level

If you assign an IAM role to a folder, what happens to the projects inside that folder?

A The IAM role is inherited by all projects inside the folder

B The IAM role applies only to the folder and not to projects

C The IAM role overrides all project-level roles

D The IAM role applies only to new projects created after assignment

💡 Hint

Think about how permissions flow down in GCP resource hierarchy.

IAM roles assigned to a folder are inherited by all projects inside it, allowing centralized permission management.

❓ service_behavior

advanced

Effect of Deleting a Folder on Projects

What happens to projects inside a folder if the folder is deleted in GCP?

A Projects become inaccessible until reassigned

B Projects are deleted along with the folder

C Projects move up one level to the organization

D Projects are archived automatically

💡 Hint

Consider how GCP handles resource hierarchy changes.

When a folder is deleted, its projects do not get deleted. Instead, they move up one level in the resource hierarchy, usually directly under the organization.

✅ Best Practice

expert

Designing Folder Structure for Billing and Access Control

You want to separate billing and access control for multiple teams working on different projects. Which folder design best supports this?

A Create one folder for all projects and assign billing accounts at folder level

B Create folders per team and link billing accounts to projects inside those folders

C Assign billing accounts directly to folders without projects

D Do not use folders; assign billing and access at project level only

💡 Hint

Think about how folders help organize projects for both billing and access control.

Folders per team allow you to manage access control easily and assign billing accounts at the project level inside those folders, supporting separation of billing and permissions.

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