2.2.1. Billing Accounts and Project Linking
💡 First Principle: A billing account and a project have a many-to-one relationship in one direction only — many projects can link to a single billing account, but a project can only ever be actively linked to one billing account at a time.
Creating a billing account requires a valid payment method and establishes the entity that will actually be charged; it exists independently of any project and can persist even if every project linked to it is later deleted. Linking a project to a billing account is what turns on the ability to actually use paid services in that project — an unlinked project can still exist and hold free-tier-eligible resources in some cases, but most services simply refuse to provision without an active billing link. Organizations frequently maintain multiple billing accounts — for example, separating a production billing account from a sandbox/development one, so runaway experimental costs never touch the account funding customer-facing infrastructure.
⚠️ Exam Trap: A billing account can only ever be linked to one project at a time — that's a common but incorrect assumption. A single billing account can be linked to many projects simultaneously, which is precisely what makes centralized cost consolidation across an entire company possible in the first place.
Reflection Question: Why might a company deliberately maintain two separate billing accounts — one for production and one for development — rather than a single billing account for everything, given that either approach technically works?
