Study guide

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects

Google Cloud Associate Cloud Engineer ACE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan

2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups

3 Chapter 3: APIs, Quotas & Billing Configuration

3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts

4 Chapter 4: Planning Compute & Storage Resources

4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types

5 Chapter 5: Planning Network Resources

5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard

6 Chapter 6: Deploying Compute Engine Workloads

6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration

7 Chapter 7: Deploying Google Kubernetes Engine Workloads

7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE

8 Chapter 8: Deploying Serverless & Event-Driven Applications

8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc

9 Chapter 9: Deploying Data Solutions

9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud

10 Chapter 10: Deploying Networking Resources & Infrastructure as Code

10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm

11 Chapter 11: Managing Compute Engine & GKE in Production

11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE

12 Chapter 12: Managing Cloud Run, Storage & Database Operations

12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)

13 Chapter 13: Networking Operations, Monitoring & Logging

13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

14 Chapter 14: IAM Policies & Role Types

14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles

15 Chapter 15: Service Accounts & Security Configuration

15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials

16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy

16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects

Key Takeaways Explain This Topic AI

Google Cloud resources form a strict hierarchy: Organization (optional) -> Folders (optional) -> Projects (required) -> Resources

Folders can nest up to 10 levels deep, and a single parent folder can hold a maximum of 300 direct child folders

A project has three distinct identifiers: the mutable Project Name, the permanent text Project ID (6-30 chars, never reused even after deletion), and the permanent system-assigned numeric Project Number

An organization node is auto-created only when the project creator has a Cloud Identity or Google Workspace account; otherwise the project exists standalone with no organization

Deleted projects get a 30-day restore window, but Cloud Storage data inside them can be purged as early as 7 days after shutdown

Last updated: July 2026

Why the Resource Hierarchy Comes First

Every other topic on the Associate Cloud Engineer (ACE) exam attaches to a node in the resource hierarchy — billing accounts link to projects, IAM roles bind to organizations/folders/projects, and organization policies cascade down from the top. The official exam guide's very first bullet under "Setting up a cloud solution environment" is "Creating a resource hierarchy," and scenario questions routinely test whether you know where in the hierarchy to attach a control, not just what the control does.

Quick Answer: Google Cloud resources form a tree: Organization (root, optional but common for real companies) → Folders (optional, unlimited-purpose grouping) → Projects (the billing and IAM unit that actually contains resources) → Resources (VMs, buckets, GKE clusters, and so on). Permissions and organization policies set on a node are inherited by everything beneath it.

The Four Levels

Level Required? What Lives Here Typical Owner

Organization No (auto-created if you have Cloud Identity/Workspace) The company itself; root of all folders and projects Google Workspace Super Admin → delegates Organization Administrator

  • Folder No Departments, environments (prod/non-prod), business units Folder Admins per team
  • Project Yes Every resource, all billing, all API enablement Project owners/editors

Resource Yes Compute Engine VMs, Cloud Storage buckets, GKE clusters, Cloud SQL instances Resource-level IAM (rare)

The Organization Node

An organization resource is automatically provisioned the first time someone with a Cloud Identity or Google Workspace account creates a Google Cloud project — this is why Domain 1's Cloud Identity bullet (covered fully in section 2.3) is a prerequisite for a "real" organization node, not an optional add-on. The org node has a unique numeric organization ID , a display name derived from your verified primary domain, and it acts as the parent to every folder and project your company owns. The Google Workspace Super Admin automatically gets IAM authority over the new organization and should immediately delegate the Organization Administrator role ( roles/resourcemanager.organizationAdmin ) to a smaller group of cloud admins rather than operating everything from the Workspace super-admin account.

Without Cloud Identity/Workspace, a project simply has no organization — it floats as a standalone project owned by the individual who created it. This matters on the exam: a scenario describing projects that "don't roll up under any company-wide policy" is describing exactly this no-organization state.

Folders: Grouping Without Losing Inheritance

Folders sit between the organization and projects and exist purely to group resources for delegation and policy scoping — they model "different legal entities, departments, and teams within a company," and they nest, so a Marketing folder can contain Marketing/APAC and Marketing/EMEA subfolders.

Two hard limits the exam guide's blueprint expects you to know precisely:

Maximum folder nesting depth: 10 levels below the organization.

Maximum direct child folders per parent: 300 (this limit is on direct children only — a folder can still have unlimited descendants across all 10 levels).

A common real-world pattern is two top-level folders directly under the organization — Production and Non-Production (or Prod / Sandbox ) — each with its own IAM bindings and organization policies, so every project a team creates automatically inherits the right guardrails just by being placed in the correct folder. This is far more scalable than tagging or labeling projects and hoping engineers remember to apply the right IAM bindings manually to each one.

Projects: ID, Number, and Name

A project is the actual container for resources, APIs, and billing — it's the smallest unit you can attach a Cloud Billing account to. Every project has three distinct identifiers that the exam loves to test candidates on confusing:

  • Attribute Mutable? Format Example
  • Project Name Yes, anytime Free-text display label "Retail Analytics Prod"

Project ID No — permanent once set 6–30 characters; lowercase letters, digits, hyphens; must start with a letter; cannot end in a hyphen; globally unique across all of Google Cloud, forever retail-analytics-prod-42

Project Number No — system-assigned Auto-generated numeric value at creation 847213950284

The Project ID is what you reference in most gcloud commands and API calls, and it can never be reused — even after the project is permanently deleted, its ID is retired forever. The Project Number is the truly immutable, Google-internal numeric key some APIs and Cloud Audit Log entries expose instead of the ID.

Project Lifecycle: Shutdown and Deletion

When a project is deleted ("shut down"), it doesn't disappear immediately — it enters a 30-day recovery window in a DELETE_REQUESTED state, during which an Owner can restore it. During this window most resources are recoverable, but Cloud Storage objects may be purged as early as 7 days after shutdown and are not guaranteed to survive the full 30 days. The associated Cloud Billing account is disconnected immediately on shutdown and must be manually re-linked after a restore. After the 30-day window closes, the project and all its resources are permanently and irrecoverably deleted , and — consistent with the ID rule above — its project ID can never be issued to a new project again.

Exam Scenario

A retail company has one Google Cloud organization. Their platform team wants every project created by the marketing analytics group to automatically inherit a stricter data-residency policy than projects created by the internal tools group, without engineers having to remember to configure anything per-project. The correct move is to create two folders under the organization — one for each group — attach the residency-related organization policy (see section 2.2) to the marketing analytics folder, and require new projects for that group to be created inside it. Any project dropped into that folder inherits the policy automatically; a label or naming convention would not enforce anything.

Takeaways for the Exam

Know the exact order: Organization → Folder(s) → Project(s) → Resources , and that folders and the organization node are both optional (a project can exist standalone).

Memorize the two folder limits: 10 levels of nesting , 300 direct child folders per parent .

Never confuse Project ID (permanent, text, never reused), Project Name (mutable display label), and Project Number (permanent, system-assigned numeric).

A deleted project has a 30-day restore window, but Cloud Storage data may be gone after just 7 days — don't assume the full 30 days applies to every resource type.

Loading diagram... Sample Resource Hierarchy: Organization, Folders, Projects, and Resources