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?
⚠ Common exam trap
GCDL often tests the distinction between resource hierarchy components and policy tools, confusing candidates into selecting labels or billing accounts for organizational purposes when folders and organization policies are the correct structural and policy enforcement mechanisms.
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 (B) are the correct resource for modeling the hierarchy: you can nest folders under the organization to represent environments (prod, non-prod) and teams (engineering, data science), and IAM policies and Organization Policies inherit down through the folder tree to all contained projects. Organization policies (C) are the mechanism to apply common constraints (e.g., restrict VM external IPs, allowed locations) that inherit to every project under the prod folder, satisfying the requirement to enforce common policies across all prod projects. Billing accounts (A) only link projects to a payment method and do not model environment/team separation or policy inheritance. Labels (D) are metadata for filtering, reporting, and billing attribution, not a policy or hierarchy boundary. Projects (E) are the leaf resources that hold workloads; they cannot themselves group other projects or enforce inherited common policies across a set.
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.
Go deeper
Related to this question
Learn chapter
Data Security: Encryption and Access Controls
Key term
Data
Data is raw, unprocessed information, like numbers, words, or measurements, that can be stored, processed, and analyzed by computers.
Key term
Project
A project is a temporary endeavor with a defined beginning and end, undertaken to create a unique product, service, or result, managed through specific processes in IT environments.
About these practice questions
One of 848 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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
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.