mediumMultiple ChoiceObjective-mapped
Google ACE Practice Question: Tag all Compute Engine VMs in your organization…
You need to tag all Compute Engine VMs in your organization with a `cost-center` tag for billing allocation reports. The tag values must be controlled centrally — only predefined values should be allowed. Which GCP feature enables this?
⚠ Common exam trap
Google Cloud often tests the distinction between labels (free-form, no value restriction) and Resource Manager Tags (centrally controlled, predefined values), leading candidates to mistakenly choose labels because they are more commonly used for metadata.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create Resource Manager Tag keys and values at the org level, then attach tags to VMs.
Resource Manager Tags (formerly 'tags' in the Resource Manager API) allow you to create tag keys and predefined tag values at the organization level, then attach those tags to resources like Compute Engine VMs. This ensures that only centrally controlled values can be used, meeting the requirement for controlled billing allocation. Labels, by contrast, are free-form key-value pairs and cannot have their values restricted natively by an org policy.
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 Compute Engine labels — configure label keys and restrict values using an org policy.
Why it's wrong here
Compute Engine labels are free-form key-value pairs and Google Cloud does not provide an org policy constraint that restricts allowed label values or keys. While org policies can restrict resource locations, domains, or custom constraints on certain resource types, label values are not a valid constraint subject and cannot be centrally enumerated. Labels also cannot be attached in the resource hierarchy, so an org-level label value does not exist; each project or VM defines its own key-value pairs without governance.
- ✓
Create Resource Manager Tag keys and values at the org level, then attach tags to VMs.
Why this is correct
Resource Manager Tags are the intended mechanism for centrally governed, hierarchical cost attribution. Creating tag keys and enumerated values at the organization level allows an administrator to control both the schema (via the tagAdmin role) and which VMs receive the tags (via the tagUser role), ensuring out-of-band creation cannot introduce ad-hoc values. These tags are visible in the Cloud Billing cost breakdown report, satisfying the requirement to track spend by VM team. Unlike labels or network tags, resource tags have IAM and hierarchy support built in.
- ✗
Use network tags on VMs and enforce allowed values via a custom org policy constraint.
Why it's wrong here
Network tags are plain string attributes used to apply firewall rules and routing policies, not to identify cost ownership or enable billing allocation. They have no key-value structure, no enumerable values, and no IAM layer for who can create new values, so they cannot represent a controlled value set for teams. Google Cloud also does not support a custom org policy constraint that restricts network tag values; the only way to use network tags for spending would be to build a third-party audit, which does not meet the central enforcement requirement.
- ✗
Require teams to apply specific label values using a Terraform module, and enforce this via code review.
Why it's wrong here
A Terraform module plus mandatory code review enforces a desired label schema only for resources that are managed through that pipeline. It does nothing for VMs created directly via the Console, gcloud, or through other tools that bypass the module, and labels themselves are unstructured key-value pairs with no central registry. This is a procedural control, not an enforceable Google Cloud policy, so it cannot guarantee every VM carries a valid value as the original requirement asks for.
Go deeper
Related to this question
Learn chapter
Google Compute Engine
Key term
Compute Engine
Compute Engine is Google Cloud's Infrastructure-as-a-Service (IaaS) offering that lets you create and run virtual machines on Google's infrastructure.
Key term
Organization
An Organization is a top-level container in Google Cloud that represents your company or entities and serves as the root node for all your cloud resources, policies, and access control.
About these practice questions
Courseiva writes every ACE question from scratch — 769 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.