2.2. Managing Billing Configuration

💡 First Principle: Billing in Google Cloud is deliberately decoupled from the resource hierarchy — a billing account is its own top-level entity that projects link to, rather than something that lives inside a Folder or Organization — because cost allocation and organizational structure don't always follow the same lines (a single company might want three cost centers spanning projects that also belong to five different departments).

Getting billing configuration wrong doesn't cause an outage the way a networking mistake would — it causes a surprise invoice, or worse, an unexpected mid-month service suspension when nobody was watching spend closely enough to catch it climbing. Because the failure mode is financial rather than immediately technical, it's easy to under-prioritize during initial setup, which is exactly why the exam holds it accountable as its own tested subsection.

Think of a billing account like a single credit card that can be handed to multiple departments (projects) to charge against — the card itself is independent of the org chart, but someone still needs to set spending alerts so nobody discovers the limit was hit only when the statement arrives.

⚠️ Common Misconception: Deleting a project immediately stops all associated charges. In reality, some resources continue billing during the shutdown window, and costs already incurred still appear in the billing account's history regardless of whether the project that generated them still exists.