CV0-004 Operations and Support Practice Question
A company wants to implement a tagging strategy for their cloud resources to track costs by department and project. Tags must be applied to resources such as virtual machines and storage buckets. Which of the following is a best practice for cost attribution using tags?
⚠ Common exam trap
CV0-004 often tests the misconception that flexible or post-hoc tagging is acceptable, when the exam expects recognition that standardized, mandatory tags applied at creation are the only reliable basis for cost attribution.
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
✓
Define a set of mandatory tag keys such as CostCenter, Project, and Environment with standardized values.
Standardized, mandatory tag keys with controlled values (e.g., CostCenter, Project, Environment) ensure consistent cost allocation across all resources and prevent drift. This enables reliable grouping in billing reports and enforces governance via policies like AWS Tag Policies or Azure Policy. Without a defined schema, cost attribution becomes unreliable and reports fragment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Apply tags to resources only after creation to avoid governance issues.
Why it's wrong here
Post-creation tagging leaves resources untagged during their billing lifetime, so costs incurred before tagging cannot be attributed to department or project. Tags applied at provisioning, enforced by policy, capture spend from the first billing hour. Retrospective tagging suits auditing existing estates, not ongoing cost attribution.
- ✓
Define a set of mandatory tag keys such as CostCenter, Project, and Environment with standardized values.
Why this is correct
Mandatory, standardised tag keys with controlled values ensure every resource is attributable to a department and project, preventing untagged or inconsistently labelled resources from skewing cost reports. This enforces consistent cost attribution across the estate.
- ✗
Use a single tag key 'Environment' with values 'Production' or 'Development'.
Why it's wrong here
A single Environment key cannot attribute cost by both department and project, which the stem requires. Cost attribution needs separate keys per dimension so reports can group and filter independently. Environment tagging suits distinguishing production from development spend, not multi-dimensional chargeback.
- ✗
Use free-form text for tag values to allow flexibility.
Why it's wrong here
Free-form values prevent grouping: 'Finance', 'finance' and 'Fin' become separate cost buckets, so departmental reporting breaks. Controlled vocabularies or a tag policy enforce consistency. Free-form text suits informal metadata, not chargeback attribution where aggregation across thousands of resources must reconcile exactly.
Go deeper
Related to this question
About these practice questions
This CV0-004 question is part of Courseiva's 834-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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.