Cloud Digital Leader How Google Cloud Resources Are Managed Practice Question
An organization wants to tag resources with key-value metadata for cost allocation purposes (e.g., team: marketing, environment: prod). Which feature should be used?
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
✓
Labels
Labels are key-value pairs that can be applied to resources for billing, filtering, and cost attribution. They are visible in billing reports and the cost management dashboard.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Organization policy constraints
Why it's wrong here
Organization policy constraints are governance rules applied at the organizational or folder level to restrict resource usage, such as limiting allowed compute regions or disabling service APIs. They are enforced by Resource Manager and do not attach metadata to individual resources. Rather than describing a resource's purpose or ownership, they define compliance boundaries, making them unsuitable for key-value tagging.
- ✓
Labels
Why this is correct
Labels are the correct mechanism for key-value metadata in Google Cloud. They are explicitly designed to organize and track resources—for example, attaching entries like "cost-center: engineering" or "environment: production" to virtual machines, disks, and storage buckets. Labels integrate directly with billing export and Cloud Monitoring, enabling cost allocation and filtering, which precisely matches the stated requirement.
- ✗
IAM custom roles
Why it's wrong here
IAM custom roles consist of curated permission lists that govern what actions principals (users, groups, or service accounts) can perform on resources. They are access management constructs, not metadata descriptors. Even though they carry names and descriptions, they cannot be attached to resources as key-value tags, and they have no role in cost allocation or resource organization.
- ✗
Tags (network tags)
Why it's wrong here
Network tags in Google Cloud are simple strings attached to VM instances, not key-value pairs. Their primary purpose is to control ingress/egress traffic via firewall rules and enable route configurations. Because they lack the structured key-value format and aren't designed for cost allocation or resource tracking, they cannot serve as the metadata tagging mechanism the organization requires.
Go deeper
Related to this question
Learn chapter
Cloud vs On-Premises Total Cost Analysis
Key term
Metadata
Metadata is data that describes other data, providing context such as when a file was created, who created it, or its size.
Key term
Labels
Labels are descriptive text or tags attached to IT resources to organize, identify, and manage them based on attributes like purpose, environment, or owner.
About these practice questions
This GCDL question is part of Courseiva's 829-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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 GCDL 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 GCDL exam.