Why GCP? Resource Hierarchy & Global Infrastructure

GCP Fundamentals

Chapter 1 · Why GCP? Resource Hierarchy & Global Infrastructure

This is the third and final course in the site's own Cloud Platform Specifics split, deliberately kept structurally parallel to AWS Fundamentals and Azure Fundamentals chapter-for-chapter. GCP's own real chronology holds a genuine surprise: it isn't the youngest of the three.

GCP's Real Origin

In April 2008, Google announced App Engine — a real platform for developing and hosting web applications in Google-managed data centers, and Google's own real first cloud computing service. That real date matters for a genuinely interesting reason: AWS Fundamentals Chapter 1 placed AWS's own real launch in March 2006, and Azure Fundamentals Chapter 1 placed Azure's own real origin in October 2008 (announced) / February 2010 (launched as Windows Azure). GCP's own real April 2008 debut sits chronologically between the two — genuinely predating Azure's own public launch, even though GCP is commonly perceived as the youngest of the three major providers today.

Real Global Infrastructure

As of Q1 2024, GCP operates in 40 real regions and 121 real zones. A region is a specific geographical location; a zone is a real, isolated deployment area within a region — genuinely the failure domain, the same conceptual role an AWS AZ or (where supported) an Azure AZ plays. Google's own real documentation states that most regions have three zones.

A Genuinely More Uniform Real Model
Unlike Azure, where Azure Fundamentals Chapter 1 flagged a real, important gotcha — not every Azure region supports Availability Zones at all — GCP's own real model is more consistently uniform: the large majority of GCP regions have real zones (typically three) available. This doesn't mean every single GCP region is guaranteed identical zone support, but the real, common case is far less of a minefield to check than Azure's own split.

The Real GCP Resource Hierarchy

GCP organizes everything into a real, four-level hierarchy:

  • Organization — the real root, representing a company or entity; created automatically when a Google Workspace or Cloud Identity account holder creates their first project. Acts as the parent to every folder and project.
  • Folder (optional) — a real, intermediate grouping container between the Organization and Projects, modeling departments, teams, or legal entities, and providing isolation boundaries for delegated administration.
  • Project — the real, fundamental organizing unit. Every real GCP resource — a Compute Engine VM, a storage bucket — belongs to exactly one Project, no exceptions.
  • Resource — the individual real services and components living inside a Project.

Real IAM policies applied at any level cascade downward automatically — a role granted at the Organization level applies to every child Folder and Project beneath it, with no need to configure permissions individually at each one.

A Real, Distinctive Organizational Principle
Google's own real documentation states this plainly: resources don't belong to the individual employee who created them — they belong to the Organization. This real design choice directly ensures continuity when personnel changes occur, since a Project's own real ownership was never actually tied to any one person's account in the first place.

Three Real Hierarchy Models, Compared

LevelAWSAzureGCP
BroadestOrganization (Chapter 2's scope, not covered in depth in this course)Management GroupOrganization
Intermediate groupingOrganizational Unit (OU)(Management Groups can nest)Folder (optional)
Billing/access boundaryAccountSubscriptionProject
Mandatory local groupingNone (tags-based)Resource Group (every resource belongs to one)Project (every resource belongs to exactly one)
Real Q1 2023 market share~31%~25%~11%

A genuinely useful real observation: AWS Fundamentals never covered a formal multi-account hierarchy (that course scoped a single AWS account throughout); Azure's Resource Group and GCP's Project both play the same real role as the mandatory, per-resource grouping unit — just under different names, at a different real level of the overall hierarchy.

Hands-On Exercises

Exercise 1

A company grants a specific IAM role at the Organization level. Explain, in your own words, what real effect this has on a brand-new Project created inside a Folder underneath that Organization, without any additional role assignment being made.

📄 View solution
Exercise 2

An employee who created several GCP Projects leaves the company. Explain, in your own words, why this real, documented organizational principle means those Projects and their resources are not automatically at risk of being lost or orphaned.

📄 View solution
Exercise 3

A team with prior Azure experience assumes GCP's own regions will have the exact same "check per-region before assuming zone support" gotcha Azure has. Explain, in your own words, why this concern, while not completely baseless, is less critical in GCP's own real, more uniform model.

📄 View solution

Chapter 1 Quick Reference

  • GCP's real origin — App Engine, announced April 2008 — genuinely predates Azure's own October 2008 announcement / February 2010 launch
  • Real current scale — 40 regions, 121 zones (Q1 2024); most regions have three zones
  • Real hierarchy — Organization (root) → Folder (optional) → Project (every resource belongs to exactly one) → Resource
  • Real IAM inheritance — a role granted at a higher level cascades automatically to everything beneath it
  • Real principle: resources belong to the Organization, not the individual who created them
  • Real market position — GCP ~11%, behind AWS's ~31% and Azure's ~25% (Synergy Research, Q1 2023)