GCP-ACE - Setting up a cloud solution environment (20% of the exam) - Section 1.2
Manage billing configuration, including creating billing accounts, linking projects to a billing account, establishing billing budgets and alerts, and setting up billing exports.
Create one or more billing accounts and link projects to them, then control spend by setting budgets with threshold alerts and exporting detailed billing data to BigQuery for analysis. Distinguish a budget alert, which only notifies, from a hard control, and know which roles are needed to associate a project with a billing account.
Billing accountsBudgets and alertsBilling export to BigQuery
Practice question for this objective
lock_openFree sampleSetting up a cloud solution environmenteasy
A finance analyst holds the Billing Account User role on the company billing account but no roles on a newly created project. They try to link that project to the billing account and are denied. Which single grant lets them complete the link with least privilege?
AGrant the analyst the Project Owner role on the target project so they hold full control over its resources.
BGrant the analyst the Billing Account Administrator role so they can manage payment settings on the account.
CGrant the analyst the Project Viewer role on the target project so they can see its configuration and billing state.
DGrant the analyst the Project Billing Manager role on the target project to pair with their existing billing account access.check_circle Correct
Associating a project with a billing account needs Billing Account User on the account plus Project Billing Manager on the project. Linking spans two resources, so it needs a permission on each: the account side is covered by Billing Account User, and the project side by Project Billing Manager, whose permission authorises creating the billing association. Neither alone completes the link.
Why A is wrong: Owner is broad and does include the ability to change a project's billing, which makes it tempting, but it grants far more than needed and violates least privilege for a task that only requires the billing-manager permission.
Why B is wrong: Billing Account Administrator manages the account itself and can assign it, but the analyst already has account-side access; the missing piece is a project-side role, so this adds account power without fixing the denial.
Why C is wrong: Viewer confers read-only access, which feels adequate for a settings change, but it carries no permission to modify the project's billing link, so the association still fails.
Why D is correct: Linking a project needs the permission to associate it, held by Project Billing Manager on the project, combined with Billing Account User on the account, which the analyst already has; together these are the least-privilege pairing.
Exam traps in Setting up a cloud solution environment
Answers that look right on this material and are not. Each one is a distractor from a different question in the GCP-ACE bank for this domain.
Each project must have its own dedicated billing account that pays only for that project.
errorWhy it is wrong: This mirrors the one-to-one intuition many beginners hold, but it is wrong; one billing account routinely funds several projects together.
Create a separate budget in each of the four projects and set matching thresholds so their individual alerts add up to the group total.
errorWhy it is wrong: Per-project budgets are valid, but each one only measures its own project, so their alerts never represent the combined figure; you cannot infer the group total by adding independent threshold events.
In BigQuery, by creating a billing export dataset that automatically attaches the account to the project.
errorWhy it is wrong: Billing export produces cost reporting data and has no role in association; creating a dataset never links a project to a billing account, so paid APIs would still fail.