Cloud Digital Leader How Google Cloud Resources Are Managed 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.

• ✗

  Create a folder for each environment and assign projects to the folders

  Why it's wrong here

  Folders in Google Cloud manage resource hierarchy and let you apply IAM policies and organization policies to a group of projects, but they are not a billing dimension. The BigQuery billing export includes project labels, not folder membership, so assigning projects to environment folders won't allow cost breakdown by environment directly in reports or queries. You would instead have to join folder metadata with project-level billing data, which is indirect and unsupported natively in Cloud Billing.

• ✓

  Add a label like 'environment:dev' or 'environment:prod' to each project

  Why this is correct

  Labeling each project with a key-value pair like `environment:dev` or `environment:prod` is the native Google Cloud approach for cost allocation. These labels are exported with every usage record in the Cloud Billing BigQuery export, enabling you to filter, group, and aggregate costs by environment in SQL queries or through cost reports. Labels are also on other resources, so you can even drill down to service-level or resource-level costs by environment, and you can attach budgets and alerts based on label filters.

• ✗

  Use separate billing accounts for each environment

  Why it's wrong here

  Creating separate billing accounts for development and production scatters cost data across different invoices, payment methods, and budget policies, making a unified view of total cloud spend an extra manual effort. Each billing account incurs administrative overhead for IAM management, payment configuration, and monthly reconciliation, and you cannot natively query across billing accounts in one BigQuery dataset unless you set up custom integration. Google recommends using a single billing account with labels to categorize environments, and to reserve multiple billing accounts for distinct legal entities or government compliance requirements.

• ✗

  Create a separate organization for each environment

  Why it's wrong here

  Maintaining separate Google Cloud organizations for each environment fragments the resource hierarchy, directory, IAM policies, and policy inheritance, so you lose centralized governance over both development and production. Billing data is not automatically consolidated across organizations, and there is no straightforward way to move projects between organizations, so this approach significantly increases operational complexity without adding any cost-tracking capability that labels don't already provide. An organization should remain the single root for your entire enterprise, with folders and labels used for environment separation.

Go deeper

Related to this question