Task 1.2: Managing billing configuration.

• ABilling Account User on the billing account and Owner on the projects

  Incorrect

  This pair can link projects, but Owner also grants full control of every resource in the projects, which the lead must not have.

• BBilling Account User on the billing account and Project Billing Manager on the projects

  Correct

  Together these let a user attach and detach projects on that billing account, without rights over resources or the billing account's settings.

• CBilling Account Administrator on the billing account and Viewer on the projects

  Incorrect

  Billing Account Administrator also manages payment methods and the billing account's users, which the lead must not do.

• DBilling Account Costs Manager on the billing account and Project Billing Manager on the projects

  Incorrect

  Billing Account Costs Manager covers budgets and cost exports and does not allow linking or unlinking projects.

Linking a project needs a permission on both sides: on the billing account (Billing Account User) and on the project (Project Billing Manager, which Owner includes). Choosing the narrow project role keeps resource access out of the grant.

• AEnable the Detailed usage cost export of the billing account to a BigQuery dataset

  Correct

  The detailed export adds resource-level cost data, such as an individual VM or disk, to everything in the standard export.

• BCreate a BigQuery dataset in a project set aside for billing data

  Correct

  The billing export writes into a BigQuery dataset that you create beforehand in a project you choose.

• CDownload the cost table report as a CSV file each month and load it into Cloud SQL

  Incorrect

  A manual monthly download is not an ongoing export, and the cost table does not replace the resource-level export for this analysis.

• DEnable only the Standard usage cost export of the billing account to a BigQuery dataset

  Incorrect

  The standard export is good for trends by project and service but does not carry the resource-level rows finance needs.

• EEnable the Pricing export of the billing account to a BigQuery dataset

  Incorrect

  The pricing export holds the account's prices for SKUs, not what each resource cost.

Cloud Billing export to BigQuery runs automatically through the day once enabled. Pick the export by the question you need answered: standard for trends, detailed for resource-level cost, pricing for list and contract prices.

• ASet the budget amount to last month's spend instead of a fixed amount

  Incorrect

  Basing the amount on last month changes the target, not when alerts are sent; alerts still wait for actual spend.

• BChange the budget period from monthly to quarterly

  Incorrect

  A longer period spreads the budget over more time and makes an early-month overrun even harder to notice.

• CAdd a threshold rule on forecasted spend at 100% of the budget

  Correct

  Forecasted threshold rules alert when the cost projected to the end of the period is set to exceed the threshold, before actual spend gets there.

• DLower the actual-spend thresholds to 10%, 20% and 30% of the budget

  Incorrect

  Low actual-spend alerts fire every month as normal spend accrues, so they say little about whether the month will overrun.

Actual-spend thresholds report what has already happened. A forecasted threshold estimates the end-of-period cost and warns as soon as the trend points past the budget.

• AOne Cloud Billing account, with a folder per subsidiary and a budget scoped to each folder

  Incorrect

  Folder-scoped budgets track each subsidiary's spend, but they do not create separate invoices or payment methods.

• BTwo Google Cloud organizations, one per subsidiary, sharing the existing Cloud Billing account

  Incorrect

  Splitting the organization adds identity and policy work and still leaves one billing account, one invoice and one payer.

• COne Cloud Billing account, with labels on every resource naming the subsidiary that owns and pays for it

  Incorrect

  Labels split costs in reports and exports, but one account still produces one invoice paid from one payments profile.

• DOne Cloud Billing account per subsidiary, each with its own payments profile and projects

  Correct

  A Cloud Billing account carries a payments profile and produces its own invoice, so one account per subsidiary separates both.

Invoices and payment methods belong to the Cloud Billing account, not to projects or folders. When two parties must pay separately, give each its own billing account and link projects accordingly.

• ABilling Account User

  Incorrect

  This role does not cover budgets or cost exports.

• BBilling Account Administrator

  Incorrect

  This role also manages payment settings and users, which the analyst must not do.

• CBilling Account Costs Manager

  Correct

  This role manages budgets and cost exports and views cost data, without linking projects or managing the account.

• DProject Billing Manager

  Incorrect

  This project-level role does not cover budgets or cost exports.

Billing roles separate cost management from account administration. The costs manager role fits FinOps work.

• AEnter a fixed amount and update it by hand each month

  Incorrect

  Manual updates are what the team wants to avoid.

• BCreate a new budget at the start of each month

  Incorrect

  Recreating budgets adds work without following history automatically.

• CUse the last period's spend as the budget amount

  Correct

  Budgets can base the amount on the previous calendar period's spend.

• DLeave the budget amount empty

  Incorrect

  A budget needs an amount to compare spend against.

A last-period budget compares this period with the previous one, which highlights growth without anyone maintaining the target.

• AThe Cloud Asset Inventory export

  Incorrect

  This exports resource metadata, not prices.

• BThe Pricing data export to BigQuery

  Correct

  The pricing export contains the billing account's pricing data for each SKU.

• CA monthly CSV download of the invoice

  Incorrect

  An invoice lists charges, not prices per SKU, and is not in BigQuery.

• DThe Standard usage cost export only

  Incorrect

  This contains costs, not the account's price list.

Billing exports serve different questions: usage cost exports for what you spent, the pricing export for what each SKU costs your account.

• AApply a team label to their VMs, disks and buckets

  Correct

  Resource labels appear in billing data, so costs can be grouped by team.

• BCreate a separate billing account for each team

  Incorrect

  Projects link to one billing account each, so this cannot split shared projects.

• CPut each team's resources in a different region

  Incorrect

  Regions are not a reliable or intended way to attribute costs.

• DUse different machine types for each team

  Incorrect

  Machine types do not identify owners in billing data.

Labels are the standard way to attribute shared costs. Agree on label keys early and apply them consistently.

• AThe Cloud Monitoring dashboard for the project

  Incorrect

  Monitoring dashboards show operational metrics, not invoice costs.

• BThe Cloud Asset Inventory search page

  Incorrect

  Asset search lists resources, not invoice costs.

• CThe Budgets page

  Incorrect

  Budgets compare spend with targets; they are not a reconciliation view.

• DThe Cost table report for that invoice month

  Correct

  The cost table shows detailed costs for an invoice or statement, with totals that match it, and can be downloaded.

Use the cost table when numbers must tie out to an invoice, and the billing export when you need custom analysis.