Projects & the Resource Hierarchy
Google ACE ACE · Setting up a cloud solution environment
Why the resource hierarchy matters
Every resource in Google Cloud — every virtual machine, storage bucket, database, and firewall rule — lives inside a project, and every project sits somewhere in a resource hierarchy. The hierarchy is the skeleton of a Google Cloud environment: it decides who can access what, which policies apply where, and how costs roll up. The exam tests it heavily because getting the hierarchy wrong at the start is expensive to fix later. A well-designed hierarchy makes access control and governance almost automatic; a flat one, with dozens of projects floating loose under an organization, turns every permission change into manual work.
The hierarchy has four levels, from top to bottom: organization, folder, project, and resource. Policies and permissions set at a higher level are inherited by everything below it. That inheritance is the single most important idea in this guide: an IAM role granted on a folder applies to every project inside that folder and every resource inside those projects, and an organization policy set at the organization level constrains every folder and project beneath it. When a question describes a requirement that applies to a whole department or a whole environment, the answer is almost always to act at the folder or organization level, not project by project.
Organization, folders, and projects
An organization is the root of the hierarchy and represents a company. It is created automatically when you set up Google Workspace or Cloud Identity with a verified domain, and a Google Cloud account can have at most one organization. The organization node is where company-wide policies live: organization policies that restrict what any project may do, and IAM roles for central administrators. If there is no organization — for example, a personal Gmail account creating projects directly — those projects have no organization node above them, and organization policies cannot be applied.
Folders sit between the organization and projects and are optional but strongly recommended. They group projects by department, team, environment, or any structure that matches how the company works. A common pattern is folders for environments (production, staging, development) crossed with folders for teams, so that a policy like "no public IP addresses in production" can be applied once to the production folder. Folders can be nested up to ten levels deep, though in practice two or three levels is plenty. A project can belong to only one folder (or directly to the organization), and moving a project between folders changes which inherited policies and permissions apply to it — the exam sometimes tests whether you know that moving a project can change its effective permissions.
A project is the fundamental unit of organization in Google Cloud. It is the boundary for several things at once: billing (a project is linked to one billing account), API enablement (APIs are enabled per project), quotas (most quotas are per project), and IAM (roles can be granted at project level). Resources in different projects are isolated from each other by default — a VM in one project cannot see a bucket in another unless access is explicitly granted. Best practice is one project per application or per environment of an application, so that access, billing, and quotas stay cleanly separated. Project IDs must be globally unique across all of Google Cloud and cannot be changed after creation, while project names can be changed and need not be unique. Every project also has a project number, assigned by Google, which never changes.
Organization policies
Organization policies (the Organization Policy Service) let administrators set guardrails on what resources are allowed to do. Unlike IAM, which controls who can act, organization policies control what is allowed at all — even an organization administrator cannot override them by granting an IAM role. Common examples include restricting which regions resources can be created in, requiring OS Login on VMs, disabling the creation of external IP addresses, and requiring uniform bucket-level access on Cloud Storage buckets. Policies are defined by constraints (such as "allowed values" lists or boolean on/off settings) and are attached to the organization, a folder, or a project; a policy set at a higher level is inherited downward, and a policy set at a lower level can refine it but cannot widen it. The exam often tests the distinction: if the requirement is "no one in the company may create resources outside europe-west2", that is an organization policy, not an IAM role.
Cloud Identity and user management
Cloud Identity is Google's identity service for organizations that do not use Google Workspace. It provides managed user accounts and groups under the company's domain, so that employees sign in with their work email and administrators can manage them centrally. Users can be created manually in the Admin console, or automatically through directory synchronization from an existing identity provider such as Microsoft Active Directory (using Google Cloud Directory Sync) or through federation. Groups are the key management tool: grant IAM roles to a group, and everyone in the group inherits them — when someone joins or leaves a team, you change the group membership, not dozens of IAM bindings. The exam expects you to prefer groups over individual user grants whenever a question involves a team.
Enabling APIs and assessing quotas
Before a project can use a Google Cloud service, that service's API must be enabled in the project — Compute Engine API for VMs, Cloud SQL Admin API for databases, and so on. Enabling an API is a per-project action done in the console or with the command gcloud services enable. A classic exam scenario is a deployment that fails with an error about an API not being enabled; the fix is to enable the API, not to change permissions. Some APIs also require billing to be enabled on the project before they can be used.
Quotas limit how much of a resource a project can use — the number of VM instances, CPUs, IP addresses, or API requests per minute. Quotas exist to protect both Google and the customer from runaway usage. When a deployment fails because a quota is exhausted, the answer is to check the quota in the console (IAM & Admin → Quotas) and request an increase, which Google reviews; increases are not automatic or instant. Quotas are per project and per region for most resources, so a quota problem in one region may not exist in another. The exam sometimes pairs quotas with billing: a quota increase request for a project without billing enabled will not help, because many quotas are higher — or only increasable — once billing is attached.
Setting up operations tooling
Part of setting up a cloud environment is provisioning the products in Google Cloud's operations suite — Cloud Monitoring, Cloud Logging, and related tools — so that the environment is observable from the start. In practice this means creating a Monitoring workspace scoped to your projects, deciding how logs will be routed and retained, and making sure the metrics and logs you will need during an incident are actually being collected. The exam guide lists this under environment setup, and the monitoring and logging guide later in this package covers the details. For this section, remember the principle: observability is set up when the environment is created, not bolted on after the first outage.
Exam traps to watch for
- Applying permissions or policies project by project when a folder or organization-level setting would cover them all — inheritance is the point of the hierarchy.
- Confusing organization policies with IAM: org policies restrict what is allowed at all, even for admins; IAM controls who can act.
- Forgetting that APIs must be enabled per project before the service can be used — a failed deployment is often an API enablement problem, not a permissions problem.
- Treating project IDs as changeable: the project ID is globally unique and permanent, while the display name can be changed.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company has 40 projects organized under folders for each department. The security team wants every project in the Engineering folder to require OS Login on all Compute Engine VMs. What is the most efficient way to achieve this?
Explanation: An organization policy set on the Engineering folder is inherited by every project inside it, so a single policy covers all current and future projects in that folder. Enabling OS Login VM by VM would work but is manual and error-prone, and it would not cover new VMs. Granting an IAM role controls who can log in, not whether OS Login is enforced on the VMs. Moving all VMs into one project would break the existing project structure and is unnecessary.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — applying organizational policies to the resource hierarchy
Q2.A developer tries to create a Cloud SQL instance in a new project and receives an error saying the Cloud SQL Admin API is not enabled. What should the developer do?
Explanation: APIs are enabled per project, and a service cannot be used until its API is enabled in that project — the error message names the exact fix. A quota increase addresses resource limits, not API enablement. An IAM role would not help because the failure is not a permission denial. Changing the billing account is unrelated to API enablement.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — enabling APIs within projects
Q3.Which statement about the Google Cloud resource hierarchy is correct?
Explanation: Permissions and policies flow downward through the hierarchy: a role granted on a folder applies to every project inside it and every resource inside those projects. A project belongs to exactly one parent — one folder or the organization directly. Organization policies attach to the organization, folders, or projects, not to individual VMs. A Google Cloud account has at most one organization node.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — creating a resource hierarchy
Q4.A startup is setting up Google Cloud for the first time. They want employees to sign in with their company email addresses and be managed centrally, but they do not use Google Workspace. Which service should they use?
Explanation: Cloud Identity provides managed user accounts and groups for organizations without Google Workspace, and supports automated provisioning through directory sync. Cloud DNS manages DNS records and does not create user accounts. Identity-Aware Proxy controls access to applications based on identity; it does not manage the identities themselves. Cloud KMS manages cryptographic keys, not user accounts.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — managing users and groups in Cloud Identity
Q5.An administrator moves a project from the Development folder to the Production folder. What is a likely consequence of this move?
Explanation: Moving a project changes its position in the hierarchy, so it inherits the permissions and policies of its new parent folder — which is exactly why the move must be planned carefully. The project ID is permanent and does not change. Resources are not deleted by a move, and the billing link is unaffected.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — creating a resource hierarchy
Q6.A company wants to guarantee that no one — including project owners — can create Compute Engine VMs with external IP addresses anywhere in the organization. Which mechanism enforces this?
Explanation: Organization policies restrict what is allowed at all, even for administrators — an org policy disabling external IPs at the organization level is inherited by every folder and project and cannot be worked around with IAM roles. Removing a role only affects who can act, and owners could still create VMs with external IPs through other means. A firewall rule filters traffic but does not prevent the IP from being assigned. A billing budget only alerts on spending; it does not block resource creation.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — applying organizational policies to the resource hierarchy
Q7.A team is deploying a large batch of VMs in us-central1, but the deployment fails partway through with a quota error, even though the same deployment succeeded last month in the same project. What is the most likely cause, and what should they do?
Explanation: Quotas are per project and per region, and they are consumed by running resources — growth since last month can exhaust a CPU or instance quota that was fine before. The fix is to check the quota in the console and request an increase. A disabled API would produce an API error, not a quota error. An unlinked billing account would block all billable operations, not produce a quota message. Zones within the same region share the regional quota, so switching zones would not help.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — assessing quotas and requesting increases
Q8.A new employee joins the data engineering team. The team manages 12 projects, and every team member needs the same set of permissions in all of them. What is the best way to give the new employee access?
Explanation: Granting roles to a group and managing membership is the scalable pattern: one group change gives the employee the right access in all 12 projects, and removing them later is a single step. Granting roles individually in 12 projects is slow and easy to get wrong or leave behind. Ownership of one project does not propagate to other projects. A service account is for applications, not for a human employee, and sharing its key is a security failure.
Exam objective: ACE exam guide 1.1: Setting up cloud projects and accounts — granting members IAM roles within a project