CV0-004 Operations and Support Practice Question
A cloud operations team is implementing a tagging strategy for cost attribution. They need to track costs by environment (dev, test, prod), project, and team. Which approach should they use?
⚠ Common exam trap
Many exam-takers confuse naming conventions or account separation with tagging — candidates often think a well-structured name or separate accounts is sufficient for cost attribution, but only tags provide the queryable metadata needed for billing reports.
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
✓
Apply tags such as Environment, Project, and Team to all resources
Tags are key-value pairs that can be applied to resources and used for cost allocation, filtering, and reporting across environments, projects, and teams. Applying Environment, Project, and Team tags to all resources enables granular cost attribution in billing reports and supports chargeback/showback models.
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 resource groups to organize resources by environment
Why it's wrong here
Resource groups organise lifecycle and access, but a resource belongs to one group only, so environment, project and team cannot be tracked simultaneously across those three axes. They are tempting because grouping by environment is a common organisational pattern, and would be correct if environment were the sole attribution dimension required.
- ✓
Apply tags such as Environment, Project, and Team to all resources
Why this is correct
Applying Environment, Project and Team tags to all resources creates the three attribution dimensions the stem requires, enabling cost reports grouped by deployment stage, initiative and owning group. Consistent tagging across resources is what makes allocation accurate.
- ✗
Use resource naming conventions to encode environment and project
Why it's wrong here
Naming conventions are free-text strings; cost management tools cannot group or filter spend by them, so environment, project and team attribution fails. They are tempting because they cost nothing and enforce human-readable consistency, and would suffice where only manual identification of resources is needed, not automated cost reporting.
- ✗
Create separate cloud accounts for each environment
Why it's wrong here
Creating separate cloud accounts per environment isolates billing but prevents unified cost attribution across the project and team dimensions, as each account generates independent invoices that cannot be natively aggregated by those tags. This approach is tempting because account-level isolation is a standard security boundary for production workloads, and it would be correct if the requirement were strict administrative separation rather than cross-cutting cost tracking by project and team.
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.