Prepare and test your skills

Prepare and test your skills

Resource grouping for governance and cost management is the practice of organizing Google Cloud resources into a logical hierarchy so access, rules, and spending can be controlled from central points. Resource Manager (opens in a new tab) provides this hierarchy with an organization at the top, optional folders in the middle, and projects at the base that hold service resources. This structure lets administrators apply policies once at a high level, track spending by project and folder, and keep resources owned by the company rather than by individuals.
The resource hierarchy (opens in a new tab) is a file-system-like tree where every resource except the top node has exactly one parent. The hierarchy binds the lifecycle of a resource to its immediate parent and provides attachment points where access control and organization policies flow downward. Because policies and visibility flow from the top down, teams can manage common settings centrally instead of configuring each resource separately.
| Level | Scope in hierarchy | Governance and cost use |
|---|---|---|
| Organization | Root above all folders and projects | Central visibility, ownership continuity, and company-wide access and policy inheritance |
| Folder | Between organization and projects, can nest inside other folders | Group control for a department or environment, delegated administration, and grouped cost reporting |
| Project | Base container directly above service resources | Per-project billing, API enablement, and direct assignment of collaborators and permissions |
The table shows how control gets broader toward the top and more specific toward the bottom, while billing stays attached at the project level.
The organization resource is the root node of the hierarchy and acts as the parent to all folder and project resources. The organization provides centralized ownership, so projects belong to the organization rather than to the employee who created them, which keeps projects active and secure when employees leave. Organization administrators can view and manage all projects in the company from this central point, which prevents shadow projects and rogue administrators.
Access control and organization policies applied at the organization level are inherited by every folder, project, and service resource below it. For example, granting the Network Admin role to the networking team at the organization level lets that team manage networks in all projects without granting the role project by project. A Google Workspace or Cloud Identity account is required to use the organization resource, and managed users in that domain must create projects inside an organization.
Folders are optional containers between the organization and projects that group related projects for governance. Folders can model departments, teams, legal entities, or environments such as production, staging, development, and testing, and folders can contain both projects and other folders for deeper nesting. An organization resource is required to use folders, and all folders and their child projects reside under that organization.
Folders simplify governance by letting administrators apply policies and access controls to a group of projects at once. A department head can receive full ownership of that department's folder, so the permission automatically covers all current and future projects in the folder. Folders can also limit access, so users in one department can only access and create resources within their own folder, which creates a clear isolation boundary between teams.
The project resource is the fundamental organizing entity that is required to create, enable, and use Google Cloud services. Each project enables APIs, manages billing, and holds collaborators and permissions for the service resources inside it, such as virtual machines and storage buckets. Every service resource belongs to exactly one project, and requests to most Google Cloud resources must identify the project by its project ID or project number.
Projects support financial governance because billing is assigned at the project level, so usage and charges can be tracked per project. Each project has a unique project ID, an automatically assigned read-only project number, a mutable display name, labels for filtering, and a lifecycle state such as ACTIVE or DELETE_REQUESTED. Labels and separate projects for teams, applications, or environments make it easier to see which group generated which costs.
Policy inheritance is the mechanism where allow policies, deny policies, and organization policies set on a parent are automatically inherited by all child resources. Identity and Access Management (IAM) defines who can do things, while the Organization Policy Service defines what can be done to resources. For example, IAM can grant a Folder Admin role on a folder so the user automatically has that role on all projects in the folder, while Organization Policy can restrict the physical locations where resources can be created or prevent creation of public IP addresses.
Resource Manager provides the hierarchical structure that the Organization Policy Service relies on to enforce rules, while Organization Policy defines restrictions on how resources in that structure can be configured. IAM allow policies at lower levels are additive to inherited allow policies, but deny policies are evaluated before allow policies and can restrict permissions at the organization, folder, or project level. If the hierarchy changes, the inherited policies change with it, so moving a project into an organization updates the project to inherit that organization's policies.
Exam tip: IAM controls who can act on a resource, while Organization Policy controls what configuration is allowed for a resource.
Cost tracking through grouping works because billing is attached to projects while reporting can aggregate those projects by their place in the hierarchy. Billing reports can analyze costs by project hierarchy to show aggregated spending at the folder level even though charges originate at the project level. This lets finance teams see total spend for production versus development, or for Engineering versus Finance, without managing billing separately for each folder.
Tags, which are key-value pairs attached to resources, extend this grouping for categorization, policy enforcement, and cost allocation within the Resource Manager hierarchy. Cloud Logging aggregated sinks can also collect logs at the folder or organization level, which supports audit and oversight of grouped resources. Together, project-level billing, folder-level aggregation, and Tags give a clear path from a single virtual machine or bucket up to department and company totals.
Policy inheritance in Google Cloud means that access and configuration policies attached to a higher level of the hierarchy automatically apply to the resources below it. The Google Cloud resource hierarchy (opens in a new tab) is a tree with the Organization at the root, optional Folders for grouping, Projects as containers for services, and Resources such as virtual machines and storage buckets at the bottom. Because each resource has exactly one parent except the root, policies flow downward along one clear path, and the effective policy for a resource combines policies set directly on it with policies inherited from its ancestors.
The hierarchy levels are the four places where policies can be attached and from which they are inherited downward. The Organization is the root node representing a company and requires a Google Workspace or Cloud Identity account for central visibility and control. Folders are optional grouping nodes that can model departments, teams, environments, or legal entities, while Projects are the fundamental organizing entity and trust boundary where every service resource belongs to exactly one project. Resources are the fundamental components such as Compute Engine virtual machines, Pub/Sub topics, and Cloud Storage buckets.
| Level | What it represents | Policy inheritance role |
|---|---|---|
| Organization | Root node for a company or domain | Policies applied here are inherited by every folder, project, and resource in the organization |
| Folders | Optional grouping nodes for departments, teams, environments, or legal entities | Policies applied here are inherited by all child folders, projects, and resources below the folder |
| Projects | Base container and trust boundary for services | Policies applied here are inherited by resources within the project |
| Resources | Fundamental components such as VMs, topics, and buckets | Some resources support resource-level policies, which apply only to that resource |
Folder structure has specific limits that affect design:
An organization resource is required to use folders. Projects belong to the organization rather than to the employee who created them, so the organization retains projects if an employee leaves.
Identity and Access Management (IAM) controls access by binding principals to roles through allow policies. Resource Manager (opens in a new tab) provides the hierarchy that IAM and Organization Policy use to organize resources and determine where policies are inherited. A principal can be a Google Account, service account, Google Group, or Google Workspace or Cloud Identity account. A role is a collection of permissions, and an allow policy attaches a set of principals to a role on a resource.
You can set allow policies at the organization, folder, project, and some resource levels. Resources inherit allow policies from their parent, so the effective allow policy for a resource is the union of the allow policy set directly on that resource and the allow policies inherited from its ancestors. Allow policies at lower levels are additive. For example, if project_1 grants the Editor role to Kalani and topic_a grants the Publisher role to Nur, then topic_a effectively gives Kalani the Editor role and Nur the Publisher role.
Granting roles high in the hierarchy reduces manual work. The Network Admin role granted at the organization level lets a networking team manage all networks in all projects, and the Folder Admin role granted on a folder applies to all projects within that folder. If an inherited role already provides all the permissions a principal needs, granting another role with the same or fewer permissions is redundant.
Exam tip: Deny policies are applied before allow policies, so a deny policy can override an allow policy even when the allow policy is inherited from a higher level.
Deny policies and organization policies follow the same hierarchy as allow policies but have different purposes and override behavior. Deny policies restrict permissions and can be set at the project, folder, or organization level, and they are evaluated before allow policies so they can supersede an allow. The Organization Policy Service focuses on what can be done rather than who can do it, such as restricting physical locations where resources can be created or preventing public IP addresses.
Organization policies are inherited by descendants but can be superseded by policies defined at a lower level, which allows organization-wide guidelines with exceptions. This differs from IAM allow inheritance, where lower-level allows add to inherited allows rather than replacing them. The result is two complementary controls: IAM decides which principals get which roles, and Organization Policy decides which configurations are permitted.
A hierarchy change is a move of a resource to a new parent that immediately changes which policies the resource inherits. Policy inheritance follows the current hierarchy, so changing a resource's parent changes which policies it inherits. For example, moving a project into an organization resource updates its allow and deny policies to inherit from the organization's policies.
This makes the hierarchy a living control structure. Ownership binds a resource's lifecycle to its immediate parent, central administrators can view and manage all projects, and delegated administrators can manage only their folder or project. The result is consistent security across the environment because a policy set once at a high level applies automatically to every child resource below it.
Centralized control and delegated administration in Google Cloud are achieved through the resource hierarchy of Organization resource, folders, and projects. The Organization resource (opens in a new tab) sits at the top and gives central administrators one place to see all folders, projects, and resources below it. Folders in the middle group related projects for departments or teams, so local administrators can manage their own area while higher-level controls continue to apply.
The Organization resource is the top node of the hierarchy and the anchor for centralized visibility and control. Central administrators use the Manage resources page in the Google Cloud console to view the full hierarchy as a table, expand the Organization resource to see child folders, and filter by name, ID, or label. From this single view, an administrator can see how departments, teams, and projects are organized without switching between separate accounts.
Control from the Organization resource works because policies set at the top flow downward to everything below:
Because the Organization resource owns this top-down view, central teams can enforce global security standards, track resources, and manage access consistently.
A folder is a container under the Organization resource that groups projects for a department, team, application, or Google Workspace account. Folders can also be nested, so a folder for Engineering can contain separate folders for Development and Testing, each with its own projects. This structure lets a company mirror its real organization while keeping all resources connected to the same central hierarchy.
Delegation happens by granting folder-level administrator roles to specific people. The folder role model supports three main needs:
To give someone that control, an existing administrator must have the Folder IAM Administrator role or the Folder Admin role at the parent level. This model delegates daily work without giving away global control. A department lead can add members, grant project roles, and organize projects inside their folder, but they cannot change controls set above their folder at the organization level.
Inheritance is the rule that policies set on a parent resource automatically apply to all of its descendants. An IAM allow policy is attached to a Google Cloud resource and contains role bindings that connect principals, such as users or service accounts, to IAM roles. Those bindings grant the roles both on the attached resource and on all descendants, so access granted to a folder also grants access to the projects and resources inside that folder.
The same inheritance applies to guardrails. By default, an organization policy enforced on a folder is enforced by Google Cloud on all projects in that folder, and a policy enforced on the organization is enforced on all folders and projects below it. This means a central rule, such as a restriction on specific operations, continues to protect delegated folders even when local administrators manage their own access.
| Hierarchy level | Scope of control | Typical administrative use |
|---|---|---|
| Organization resource | Entire company, including all folders and projects | Enforce global policies, grant company-wide roles, maintain central visibility |
| Folder | One department or team, including its child folders and projects | Delegate administration to team leads while inheriting global policies |
| Project | One workload, including its resources | Manage day-to-day access and services for a specific application |
The table shows why delegation stays safe: scope narrows from organization to project, but higher-level policies still flow down to every delegated area.
Exam tip: Granting a role on a folder grants that role on every project and resource inside the folder, while granting a role on a project affects only that project.
Identity and Access Management (IAM) defines who can do things by binding principals to roles through allow policies, while the Organization Policy Service defines what can be done to resources by restricting configurations such as physical locations where resources can be created or preventing public IP addresses. IAM allow policies set on a parent are inherited additively by all descendants, deny policies are evaluated before allow policies and can supersede an allow, and organization policies are also inherited but can be superseded by policies defined at a lower level.
Folders are optional containers between the organization resource and projects that group related projects for a department, team, legal entity, or environment such as production, staging, development, and testing. Policies and access controls applied to a folder automatically apply to all child folders, projects, and resources below it, so a department head with ownership of the folder covers all current and future projects inside while users in one department can be limited to only their own folder for isolation.
Billing is assigned at the project level while billing reports can analyze costs by project hierarchy to show aggregated spending at the folder level for groups such as production versus development or Engineering versus Finance. The organization resource provides centralized ownership so projects belong to the organization rather than to the employee who created them, which keeps projects active and secure when employees leave and lets administrators view and manage all projects from a central point.
An enterprise structures its Google Cloud environment using the Resource Manager hierarchy, which includes an Organization node at the root, department-specific Folders, application Projects, and individual service Resources (such as Compute Engine virtual machines and Cloud Storage buckets). The security team has the following access control requirements for the Engineering department:
How should the security team apply Identity and Access Management (IAM) allow policies within the resource hierarchy to meet these requirements?
Last updated