Folders for grouping projects in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a folder under an organization in GCP.

GCP

gcloud resource-manager folders create --display-name=[1] --organization=123456789

Drag options to blanks, or click blank then click option'

A"My Folder"

BMyFolder

CMy Folder

D'MyFolder'

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes around the folder name

Using spaces without quotes

The display name must be a string enclosed in quotes to handle spaces or special characters.

2fill in blank

medium

Complete the code to list all folders under an organization.

GCP

gcloud resource-manager folders list --organization=[1]

Drag options to blanks, or click blank then click option'

A123456789

Bfolder-id

Cmy-org

Dproject-id

Attempts:

3 left

💡 Hint

Common Mistakes

Using organization name instead of ID

Using project ID instead of organization ID

The organization flag requires the numeric organization ID, not names or project IDs.

3fill in blank

hard

Fix the error in the command to move a project to a folder.

GCP

gcloud projects move [1] --folder=[2]

Drag options to blanks, or click blank then click option'

A123456789

Bmy-project-123

Cfolders/987654321

D987654321

Attempts:

3 left

💡 Hint

Common Mistakes

Using folder name instead of project ID

Including 'folders/' prefix in folder ID

The project ID is the first argument; the folder flag requires only the folder numeric ID without 'folders/' prefix.

4fill in blank

hard

Fill both blanks to correctly move a project to a folder.

GCP

gcloud projects move [1] --folder=[2]

Drag options to blanks, or click blank then click option'

Amy-project-123

B987654321

Cfolders/987654321

D123456789

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'folders/' prefix in folder ID

Swapping project ID and folder ID

The project ID is 'my-project-123' and the folder ID is the numeric ID without 'folders/' prefix.

5fill in blank

hard

Fill all three blanks to create a folder, list folders, and move a project.

GCP

gcloud resource-manager folders create --display-name=[1] --organization=[2]
gcloud resource-manager folders list --organization=[2]
gcloud projects move [3] --folder=[4]

Drag options to blanks, or click blank then click option'

A"Finance"

B123456789

Cmy-project-123

D987654321

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting folder name

Using wrong IDs

Mixing project and folder IDs

Use 'Finance' as folder name with quotes, organization ID 123456789, project ID 'my-project-123', and folder ID 987654321.

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