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.

• ✓

  View billing reports filtered by label

  Why this is correct

  Billing reports in Cloud Console support filtering by resource labels, which can be applied at project or resource level. By assigning a label like 'department=marketing' to resources, you can view cost breakdowns per department directly in the billing reports. This is the intended lightweight method for cost allocation without additional data processing.

• ✗

  Export billing to Cloud Storage and analyze

  Why it's wrong here

  Exporting billing data to Cloud Storage is possible but requires converting the exported files (typically JSON or CSV) and analyzing them with external tools; native querying isn't available. To analyze at scale, Google recommends exporting to BigQuery, which provides SQL querying and integration with Looker Studio. Simply exporting to Cloud Storage doesn't provide a built-in label filter breakdown like billing reports do.

• ✗

  Create a billing account budget

  Why it's wrong here

  Budgets are designed to track spend against a threshold and send alerts to prevent overspending; they do not provide a per-label breakdown of costs. Budgets can filter by labels and projects, but their purpose is monitoring and alerting, not a historical cost reporting view. They don't replace the need to view billing reports filtered by label for department-level cost analysis.

• ✗

  Use the Cost Table in Cloud Console

  Why it's wrong here

  There is no feature called 'Cost Table' in the Cloud Console. The billing console provides 'Reports' and 'Cost breakdown' views, but not a 'Cost Table.' Google Cloud does not offer a predefined cost table; instead, billing reports allow you to group by label, and Cost Management tools like the Cloud Billing catalog. Hence this option is invalid.

Go deeper

Related to this question