GCP Associate Cloud Engineer Practice Question 71: Labels Cost Attribution
Google Cloud Associate Cloud Engineer · Test 8 · question 1 of 10
A company runs workloads for three internal teams inside a single GCP project. Finance wants a monthly breakdown of spend per team in the billing reports, without splitting the workloads into separate projects. What should you do to enable this breakdown with the least administrative overhead?
Show answer and explanation
Answer:
Labels are key value pairs you attach to resources, and Cloud Billing reports can be filtered and grouped by label, giving a per team cost breakdown without touching the project or folder structure. This is the standard lightweight way to attribute shared-project spend to internal groups.
Option A works but a billing account is a much heavier construct meant for payment and legal entities, not for internal reporting, and moving resources between billing accounts is disruptive. Option C describes audit logging, which records who did what and does not aggregate cost data. Option D changes the resource hierarchy, which affects IAM inheritance and other policies project wide; it does not itself produce a per team billing breakdown, and the question specifies the workloads must stay in a single project.
Reference: Labels overview