What's changed: Created Associate Cloud Engineer Chapter 1 (Domain 1 "Setting up the environment": resource hierarchy and IAM = org/folder/project/policy inheritance/Cloud Identity/Cloud IAM (member/role/resource, basic/predefined/custom, least privilege); managing billing, APIs, quotas = billing account and linking/budgets and alerts/billing export/enabling APIs/quotas).
1.2Managing billing, APIs, and quotas
Understand the configuration tasks that make a cloud environment operational: linking billing accounts to projects, budgets and alerts and billing exports, enabling APIs in a project, and assessing and requesting increases to quotas.
A project alone cannot use resources. You must enable billing, enable the needed APIs, and operate within quotas. You also set up safeguards against runaway cost here.
1.2.1Billing accounts and budgets
Costs are paid against a Billing Account, and each project is linked to one (a billing account can have many projects). To prevent runaway cost, set budgets and alerts that notify at thresholds (e.g., 50%/90%/100%). Crucially, budget alerts notify; they do not automatically stop spending. For detailed analysis, export billing data to BigQuery.
1.2.2Enabling APIs and quotas
Before using a Google Cloud service, you must enable its API in the project (e.g., Compute Engine API, BigQuery API). Each service has quotas, which are limits guarding against overuse, runaway usage, and cost incidents. Quotas include rate limits (API calls per time unit) and allocation limits (e.g., concurrent resources). When you hit a limit and cannot add resources, request a quota increase from the Cloud Console. A common reflex: "cannot create a resource → suspect a quota limit."
| Task | Key point |
|---|---|
| Link billing account | Tie a project to a billing account |
| Budgets and alerts | Notify at thresholds (no auto-stop) |
| Billing export | Export to BigQuery for analysis |
| Enable API | Enable per service to use |
| Quotas | Limits; request increases when short |
Common: situation → action. E.g., "incur cost in a project" = link a billing account; "notify on budget overrun (not stop)" = budgets and alerts; "analyze cost in detail" = export billing to BigQuery; "start using a service" = enable its API; "cannot create resources at a limit" = request a quota increase.
Watch the mix-ups: (1) budget alerts only notify; they do not auto-stop spending. (2) You must enable the API before using a service (operations fail otherwise). (3) "cannot create a resource" is either insufficient permissions or insufficient quota—check both.
1.2.3Section summary
- Link projects to a billing account; budgets/alerts only notify (no auto-stop); analyze via BigQuery billing export
- Enable a service’s API before using it
- Quotas are limits; if you cannot create resources, also suspect a quota and request an increase
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. Which correctly describes how budgets and alerts behave?
Q2. You try to start using Compute Engine but operations fail. What should you check first?
Q3. Which is appropriate for analyzing cost breakdowns in detail?
Q4. When you hit a limit and cannot create more resources, what is the appropriate action?
Q5. What is required so a project can incur cost and use resources?
Q6. Which best describes the main purpose of quotas?