Why resource hierarchy matters in GCP - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the parent resource when creating a new project in GCP.

GCP

gcloud projects create my-project --[1]=123456789012

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

Aorganization

Bparent

Cfolder

Dbilling-account

Attempts:

3 left

💡 Hint

Common Mistakes

Using --folder instead of --organization

Omitting the parent resource flag

Using --billing-account which is unrelated to hierarchy

The --organization flag sets the parent organization for the new project, placing it correctly in the resource hierarchy.

2fill in blank

medium

Complete the code to list all projects under a specific folder in GCP.

GCP

gcloud projects list --filter='parent.type:folder AND parent.id:[1]'

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

Amy-folder

Bfolders/123456789012

C123456789012

Dorganizations/123456789012

Attempts:

3 left

💡 Hint

Common Mistakes

Including 'folders/' prefix in the ID

Using organization ID instead of folder ID

Using folder name instead of ID

The filter requires the folder ID only, not the full resource name.

3fill in blank

hard

Fix the error in the command to set IAM policy on a folder resource.

GCP

gcloud resource-manager folders set-iam-policy [1] policy.yaml

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

Afolders/123456789012

Bmy-folder

C123456789012

Dorganizations/123456789012

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the numeric ID without prefix

Using organization prefix instead of folder

Using folder name instead of ID

The folder ID must be prefixed with 'folders/' to specify the resource correctly.

4fill in blank

hard

Fill both blanks to create a folder under an organization with the correct parent and display name.

GCP

gcloud resource-manager folders create --[1]=[2] --display-name="My Folder"

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

Aparent

Borganization

Corganizations/123456789012

Dfolders/123456789012

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'organization' as the flag name instead of 'parent'

Using numeric ID without prefix as parent value

Using folder prefix as parent value

The --parent flag requires the full resource name of the organization to create a folder under it.

5fill in blank

hard

Fill all three blanks to assign a project to a folder.

GCP

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

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

Amy-project-123

Bfolder

Cbilling-account

D987654321098

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--billing-account' which is for billing, not hierarchy

Including 'folders/' prefix in the folder ID

Using full resource name instead of numeric ID

The --folder flag with the numeric folder ID is used with gcloud projects move to assign the project to the folder in the resource hierarchy.

Practice

1. Why is the resource hierarchy important in Google Cloud Platform?

easy

A. It encrypts all data stored in the cloud.

B. It speeds up the network traffic between resources.

C. It automatically scales resources based on usage.

D. It helps organize resources and manage access and billing efficiently.

Solution

1. Step 1: Understand resource hierarchy purpose

   The resource hierarchy organizes resources from organization to projects and resources, helping manage them better.

2. Step 2: Identify benefits of hierarchy

   This structure allows centralized control of access, security policies, and billing, making management efficient.

3. Final Answer:

   It helps organize resources and manage access and billing efficiently. -> Option D

4. Quick Check:

   Resource hierarchy = organization and management [OK]

Hint: Resource hierarchy = organize + manage access/billing [OK]

Common Mistakes:

• Confusing hierarchy with network speed
• Thinking it automatically scales resources
• Assuming it encrypts data by default

2. Which of the following is the correct order of resource hierarchy from top to bottom in GCP?

easy

A. Resource > Project > Folder > Organization

B. Organization > Folder > Project > Resource

C. Folder > Organization > Project > Resource

D. Project > Organization > Folder > Resource

Solution

1. Step 1: Recall GCP resource hierarchy levels

   The hierarchy starts with Organization at the top, then Folder, then Project, and finally individual Resources.

2. Step 2: Match the correct order

   Organization > Folder > Project > Resource correctly lists the order from highest to lowest level.

3. Final Answer:

   Organization > Folder > Project > Resource -> Option B

4. Quick Check:

   Hierarchy order = Org > Folder > Project > Resource [OK]

Hint: Remember: Org is top, then Folder, then Project [OK]

Common Mistakes:

• Mixing up Project and Folder order
• Placing Resource above Project
• Starting hierarchy with Project

3. Given this hierarchy: Organization > Folder A > Project X > VM Instance, if a policy is applied at Folder A, which resources does it affect?

medium

A. Folder A, Project X, and VM Instance

B. Only VM Instance

C. Only Project X

D. Only Organization

Solution

1. Step 1: Understand policy inheritance in hierarchy

   Policies set at a folder apply to that folder and all resources below it in the hierarchy.

2. Step 2: Identify affected resources

   Folder A's policy affects Folder A itself, Project X inside it, and the VM Instance inside Project X.

3. Final Answer:

   Folder A, Project X, and VM Instance -> Option A

4. Quick Check:

   Folder policy affects all below it [OK]

Hint: Policies apply downward in hierarchy [OK]

Common Mistakes:

• Thinking policy affects only immediate child
• Assuming policy affects only VM Instance
• Confusing policy scope with Organization level

4. You applied a security policy at the Organization level, but a project under a folder is not enforcing it. What is the likely cause?

medium

A. The policy was applied only to the folder, not the organization.

B. The project is not part of the organization hierarchy.

C. The project has an overriding policy that blocks inheritance.

D. Policies cannot be applied at the organization level.

Solution

1. Step 1: Understand policy inheritance and overrides

   Policies set higher in the hierarchy apply downward unless overridden by a deny or blocking policy lower down.

2. Step 2: Identify why project ignores organization policy

   If the project has a policy that blocks or overrides the organization policy, it will not enforce it.

3. Final Answer:

   The project has an overriding policy that blocks inheritance. -> Option C

4. Quick Check:

   Overrides block higher policies [OK]

Hint: Lower-level overrides block higher policies [OK]

Common Mistakes:

• Assuming policy was applied only to folder
• Thinking project is outside organization
• Believing organization policies can't be applied

5. You want to apply a billing account to multiple projects grouped by department. How does using folders in the resource hierarchy help achieve this?

hard

A. Folders group projects so billing policies can be applied once to all projects inside.

B. Folders automatically assign billing accounts to projects without manual setup.

C. Folders encrypt billing data for each project separately.

D. Folders replace projects and directly hold billing accounts.

Solution

1. Step 1: Understand folder role in resource hierarchy

   Folders group projects logically, such as by department, to organize resources.

2. Step 2: Apply billing policies using folders

   Applying billing or access policies at the folder level affects all projects inside, simplifying management.

3. Final Answer:

   Folders group projects so billing policies can be applied once to all projects inside. -> Option A

4. Quick Check:

   Folders group projects for policy application [OK]

Hint: Use folders to group projects for shared billing [OK]

Common Mistakes:

• Thinking folders assign billing automatically
• Confusing folders with projects
• Believing folders hold billing accounts directly