Study guide

3.3 Billing Accounts, Project Linking & Billing Exports

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

3.3 Billing Accounts, Project Linking & Billing Exports

Key Takeaways Explain This Topic AI

A billing account can be linked to many projects, but a project can be linked to only one billing account at a time.

Self-serve billing accounts are postpay via card/ACH; invoiced accounts accrue costs and receive one monthly invoice paid by check or bank transfer.

Only a Billing Account Administrator can contact Cloud Billing Support; Billing Account User plus a project-level role (or Project Billing Manager) is what actually links a new project.

Billing export to BigQuery is configured only in the Cloud Billing console, never via gcloud, and offers Standard usage cost, Detailed usage cost (resource-level), and Pricing data tables.

Choosing a multi-region BigQuery dataset back-fills billing export data retroactively to the start of the prior month; a single-region dataset only captures data from the day export was enabled.

Last updated: July 2026

Billing Accounts, Project Linking & Billing Exports

Quick Answer: A Cloud Billing account is the payment container that pays for one or more Google Cloud projects. The ACE exam guide's Section 1.2 names three specific skills here — creating billing accounts , linking projects to a billing account , and setting up billing exports — and each has concrete rules the exam tests directly (one project ↔ one billing account; billing exports are console-only, not gcloud).

Why This Matters on the Exam

Billing questions on the ACE exam are rarely about pricing math — they're about structure and process : who can link what to what, which role does which job, and where a given billing task is actually performed. Getting the cardinality rule (many projects to one billing account, but one billing account per project) and the console-vs-CLI distinction wrong is one of the most common practice-test mistakes.

Two Billing Account Types

Type How you pay Typical use

Self-serve (online) Postpay via credit/debit card or ACH direct debit, charged automatically each billing cycle Individuals, startups, most new accounts

Invoiced Costs accrue, then one monthly invoice is issued; paid by check or bank transfer Larger enterprises with an approved agreement, typically requiring minimum spend

Every new user can start a Free Trial billing account preloaded with $300 in Welcome credit valid for 90 days — no usage is charged against a real payment method until the trial is explicitly upgraded to a paid self-serve account.

The Cardinality Rule (Frequently Tested)

One billing account can be linked to many projects — this is how organizations centralize payment while keeping engineering isolation between projects.

One project can be linked to only one billing account at a time. Unlinking and relinking is possible, but a project never pays from two accounts simultaneously.

If a billing account is closed, suspended, or unlinked from a project, running resources (like Compute Engine VMs) are stopped, not deleted — you cannot create new resources or new projects tied to that account until billing is resolved, but existing data isn't destroyed.

Billing IAM Roles

Role What it can do

Billing Account Administrator Full owner of the billing account: manage payment instruments, configure exports, view costs, link/unlink projects, manage other users' access. Only Administrators can contact Cloud Billing Support. The account creator is an Administrator by default.

Billing Account User Grants the ability to attach a new project to this billing account, but must be paired with a project-level role (like Project Billing Manager or Owner) to actually complete the link.

Billing Account Costs Manager Cost governance and budget visibility without payment-instrument or account-management access.

Billing Account Viewer Read-only visibility into cost and transaction data.

Project Billing Manager Granted at the project level; lets someone link/unlink that specific project's billing without granting any other project resource permissions. The built-in Project Owner role is a superset of this.

To link a new project to a billing account, a user typically needs either Billing Account User (on the account) or Project Billing Manager (on the project) — the exam has directly tested this "either/or" framing.

Billing Exports to BigQuery

Cost data export is configured entirely in the Cloud Billing console (Billing → Billing export) — there is no gcloud command for setting this up, which is a deliberate ACE distractor (a common wrong option is gcloud billing export bigquery or similar, which does not exist). Three tables can be produced:

Export type BigQuery table name pattern Granularity

Standard usage cost gcp_billing_export_v1_<BILLING_ACCOUNT_ID> Aggregated by service/SKU — good for monthly reporting

Detailed usage cost gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID> Everything in Standard, plus resource-level identifiers (e.g., a specific VM or disk) — needed for per-resource chargeback

Pricing data cloud_pricing_export List pricing/SKU rates, independent of your actual usage

A subtlety worth remembering: if the destination BigQuery dataset is in a multi-region location (US or EU), Cloud Billing back-fills data retroactively from the start of the previous month . If the dataset is in a single supported region , data is only available starting from the day export was enabled — nothing is back-filled. Choosing the dataset location has a real, testable consequence.

Exam Scenario

A finance team wants to build a chargeback report that shows the exact daily cost of each individual Compute Engine VM and Persistent Disk, broken down by resource, not just by service. The correct configuration is the Detailed usage cost export to BigQuery (not Standard, which only aggregates to the service/SKU level) — configured through the Cloud Billing console, since no CLI path exists for enabling export.

Common Traps

Assuming a project can be linked to more than one billing account "for redundancy" — it cannot; only one at a time.

Trying to script billing export setup with gcloud — export configuration lives only in the console/API, not the CLI surface tested elsewhere in ACE.

Confusing Billing Account User (an account-level grant) with Project Billing Manager (a project-level grant) — they solve the same linking problem from two different scopes.

Picking Standard usage export when a scenario explicitly asks for per-resource cost detail — that requires Detailed usage cost export.