Courseiva
How Google Cloud Resources Are ManagedmediumMultiple SelectObjective-mapped

Cloud Digital Leader How Google Cloud Resources Are Managed Practice Question

A company is planning their resource hierarchy in Google Cloud. They need to separate environments (prod, non-prod) and teams (engineering, data science). They also need to apply common policies to all prod projects. Which TWO resources should they use?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Folders

Folders allow hierarchical grouping of projects. Organization policies can be applied at the folder level to enforce common policies. Projects are the unit of resource management. Labels are for metadata, not hierarchy. Billing accounts are separate from hierarchy.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Billing accounts

    Why it's wrong here

    Billing accounts are financial constructs that aggregate costs across linked projects, but they do not define any hierarchy for IAM or policy inheritance. They exist at a level above projects but only determine the payer for usage, not how resources are organized or governed. Therefore, they cannot be used to group projects for applying common policies or permissions.

  • Folders

    Why this is correct

    Folders are the correct hierarchical grouping node within Google Cloud's resource hierarchy, sitting between the organization node and projects. They allow you to organize projects into environments (e.g., dev, prod) or business units, and they propagate policies (IAM, Organization Policies) downward to all projects and resources inside them. This inheritance enables centralized governance and access control across multiple projects.

  • Organization policies

    Why this is correct

    Organization policies are configuration constrains that you define at the Organization or Folder level to enforce compliance and guardrails across all child resources. They control what services can be used, where resources can be deployed, and can disable specific services, but they do not group projects by themselves. Because they are applied to a folder or organization node, they rely on the folder structure to scale across multiple projects.

  • Labels

    Why it's wrong here

    Labels are metadata key-value pairs that you attach to resources for cost accounting, monitoring, and lifecycle management. They do not create any hierarchy, grant permissions, or enforce policies; they are simply attributes for querying and reporting. Labels cannot be used to group projects or apply inheritance, so they are irrelevant to resource hierarchy planning.

  • Projects

    Why it's wrong here

    Projects are the outermost container for resources like VMs, Cloud Storage buckets, and BigQuery datasets, providing isolation and a separate trust boundary. However, a project alone cannot group multiple projects together; grouping is done by placing projects under folders. While projects are part of the hierarchy, they are the leaf node (or immediate parent of resources) and not a method for applying policies across a set of projects.

About these practice questions

One of 829 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.