Google ACE Setting Up a Cloud Solution Environment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use Billing Export to BigQuery and create custom alerts using Cloud Monitoring.

  Why it's wrong here

  Exporting billing data to BigQuery and creating custom alerts with Cloud Monitoring does not leverage the native budget alert functionality directly within the billing account, which the scenario requires for efficiency. This approach is instead designed for highly granular, custom cost analysis, complex reporting, and creating alerts based on intricate logic or aggregated data beyond simple budget thresholds. It is ideal for advanced financial oversight requiring bespoke dashboards and deep analytical capabilities, rather than straightforward project budget notifications.

• ✓

  Create one budget per project by selecting the project in the 'Scoped to' field.

  Why this is correct

  Creating one budget per project and setting the 'Scoped to' field to that project is the correct, efficient approach. In the Google Cloud console, budgets are created at the billing account level but can be scoped to a specific project, which allows the budget amount and alert thresholds to apply exclusively to that project's costs. This directly enables per-department tracking if each department maps to a project, and it provides native budget alert notifications, exactly as required.

• ✗

  Create a budget for each project by manually enabling billing for each project.

  Why it's wrong here

  Manually enabling billing for each project simply links a project to a billing account; it does not create any budget or cost-tracking mechanism. Even if you enable billing for every project, you still have to separately configure budgets, and doing this manually for many projects is inefficient and error-prone. This option misunderstands the purpose of billing enablement and fails to satisfy the requirement for per-project cost tracking with alerts.

• ✗

  Create a single budget for the entire billing account and rely on labels.

  Why it's wrong here

  Creating a single budget for the entire billing account and relying on labels does not give you per-project, budget-threshold alerts. A billing-account-scoped budget aggregates all costs across every project; while you could use labels to filter cost reports, labels are not automatically applied and can be missing or misconfigured, and the budget alert itself is triggered by total account spend, not by an individual project's spend. This approach cannot reliably track costs per department on a per-project basis.

Go deeper

Related to this question