- A
The tags are not applied to the root volumes of the EC2 instances.
Why wrong: Incorrect. Tags applied to EC2 instances are sufficient for cost tracking. While EBS volumes can have separate tags, cost allocation tags are based on the resource that generates the cost (in this case, the instance). Root volume tagging is not required for the instance tag to appear in Cost Explorer.
- B
The tags have not been activated as cost allocation tags in the Billing and Cost Management console.
Correct. Tags that you apply to resources are not automatically available for cost tracking. You must activate them as cost allocation tags in the Billing and Cost Management console. After activation, tags appear in Cost Explorer and other cost management tools.
- C
Cost Explorer requires at least 30 days of tag usage data before tags become available.
Why wrong: Incorrect. There is no mandatory 30-day waiting period. Once a tag is activated, it becomes available for filtering and grouping almost immediately for current usage data. Historical data may also be retroactively tagged for the billing period, but the tag will appear in Cost Explorer shortly after activation.
- D
The finance team does not have the iam:ListAccountAliases permission.
Why wrong: Incorrect. The iam:ListAccountAliases permission is used to retrieve the account alias, such as for the IAM sign-in URL. It is not related to displaying cost allocation tags in Cost Explorer.
CLF-C02 Billing, Pricing, and Support Practice Question
This CLF-C02 practice question tests your understanding of billing, pricing, and support. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company tags all Amazon EC2 instances with a 'Project' tag to track costs. The finance team reviews cost data in AWS Cost Explorer but cannot filter or group by the 'Project' tag. The tags are visible in the EC2 console. What is the most likely reason the tags are not appearing in Cost Explorer?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
The tags have not been activated as cost allocation tags in the Billing and Cost Management console.
B is correct because cost allocation tags must be explicitly activated in the Billing and Cost Management console before they appear in AWS Cost Explorer. Even though the 'Project' tag is applied to EC2 instances and visible in the EC2 console, AWS does not automatically treat resource tags as cost allocation tags; activation is a separate, required step. Without activation, Cost Explorer cannot filter or group by that tag.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The tags are not applied to the root volumes of the EC2 instances.
Why it's wrong here
Incorrect. Tags applied to EC2 instances are sufficient for cost tracking. While EBS volumes can have separate tags, cost allocation tags are based on the resource that generates the cost (in this case, the instance). Root volume tagging is not required for the instance tag to appear in Cost Explorer.
When this WOULD be correct
If the question asked why tags on an EC2 instance are not visible in the EC2 console or why a specific volume-level tag is not appearing in a volume list, then not applying tags to root volumes would be a plausible reason.
- ✓
The tags have not been activated as cost allocation tags in the Billing and Cost Management console.
Why this is correct
Correct. Tags that you apply to resources are not automatically available for cost tracking. You must activate them as cost allocation tags in the Billing and Cost Management console. After activation, tags appear in Cost Explorer and other cost management tools.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Cost Explorer requires at least 30 days of tag usage data before tags become available.
Why it's wrong here
Incorrect. There is no mandatory 30-day waiting period. Once a tag is activated, it becomes available for filtering and grouping almost immediately for current usage data. Historical data may also be retroactively tagged for the billing period, but the tag will appear in Cost Explorer shortly after activation.
When this WOULD be correct
This option would be correct if the question asked about the delay for new AWS accounts or services to appear in Cost Explorer reports, where AWS states it may take up to 24 hours for data to be available, but not 30 days specifically for tags.
- ✗
The finance team does not have the iam:ListAccountAliases permission.
Why it's wrong here
Incorrect. The iam:ListAccountAliases permission is used to retrieve the account alias, such as for the IAM sign-in URL. It is not related to displaying cost allocation tags in Cost Explorer.
When this WOULD be correct
This option would be correct if the question asked why a user cannot view the AWS account alias in the Billing console or cannot perform certain IAM-related actions that require listing account aliases.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.
✓The tags have not been activated as cost allocation tags in the Billing and Cost Management console.Correct answer▾
Why this is correct
Correct. Tags that you apply to resources are not automatically available for cost tracking. You must activate them as cost allocation tags in the Billing and Cost Management console. After activation, tags appear in Cost Explorer and other cost management tools.
✗The tags are not applied to the root volumes of the EC2 instances.Wrong answer — click to see why▾
Why this is wrong here
Root volume tags are separate from instance tags; Cost Explorer uses instance tags, not volume tags. The issue is that the tags are not activated as cost allocation tags, not that they are missing from volumes.
★ When this WOULD be the correct answer
If the question asked why tags on an EC2 instance are not visible in the EC2 console or why a specific volume-level tag is not appearing in a volume list, then not applying tags to root volumes would be a plausible reason.
Why candidates choose this
Candidates may confuse instance tags with volume tags, thinking that tags must be applied to all associated resources (like root volumes) to be effective, or they may overthink the tagging hierarchy.
✗Cost Explorer requires at least 30 days of tag usage data before tags become available.Wrong answer — click to see why▾
Why this is wrong here
Cost Explorer can display tag data as soon as tags are activated as cost allocation tags; there is no mandatory 30-day waiting period for tags to appear.
★ When this WOULD be the correct answer
This option would be correct if the question asked about the delay for new AWS accounts or services to appear in Cost Explorer reports, where AWS states it may take up to 24 hours for data to be available, but not 30 days specifically for tags.
Why candidates choose this
Candidates may confuse the general data availability delay in Cost Explorer (up to 24 hours) with a longer period for tags, or they may recall that some AWS services require a waiting period before data is fully reflected.
✗The finance team does not have the iam:ListAccountAliases permission.Wrong answer — click to see why▾
Why this is wrong here
The iam:ListAccountAliases permission is unrelated to tag visibility in Cost Explorer; it controls listing account aliases, not cost allocation tags.
★ When this WOULD be the correct answer
This option would be correct if the question asked why a user cannot view the AWS account alias in the Billing console or cannot perform certain IAM-related actions that require listing account aliases.
Why candidates choose this
Candidates may confuse IAM permissions with the ability to view tags in Cost Explorer, assuming that missing permissions could block tag visibility, even though the specific permission is irrelevant.
Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume that because tags are visible in the EC2 console, they are automatically available for cost tracking in Cost Explorer, but AWS requires an explicit activation step in the Billing console to designate them as cost allocation tags.
Detailed technical explanation
How to think about this question
Cost allocation tags are a billing feature that requires activation via the Billing and Cost Management console under 'Cost Allocation Tags'. Once activated, AWS processes the tags and makes them available in Cost Explorer, Cost and Usage Reports, and the AWS Cost Categories feature. A common nuance is that tags applied before activation are not retroactively available; only tags applied after activation are tracked, so organizations should activate tags before deploying resources to avoid missing cost data.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Billing, Pricing, and Support — study guide chapter
Learn the concepts, then practise the questions
- →
Billing, Pricing, and Support practice questions
Targeted practice on this topic area only
- →
All CLF-C02 questions
1,024 questions across all exam domains
- →
AWS Certified Cloud Practitioner CLF-C02 study guide
Full concept coverage aligned to exam objectives
- →
CLF-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CLF-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Concepts practice questions
Practise CLF-C02 questions linked to Cloud Concepts.
Security and Compliance practice questions
Practise CLF-C02 questions linked to Security and Compliance.
Cloud Technology and Services practice questions
Practise CLF-C02 questions linked to Cloud Technology and Services.
Billing, Pricing, and Support practice questions
Practise CLF-C02 questions linked to Billing, Pricing, and Support.
AWS shared responsibility model practice questions
Practise CLF-C02 questions linked to AWS shared responsibility model.
AWS IAM practice questions
Practise CLF-C02 questions linked to AWS IAM.
AWS pricing practice questions
Practise CLF-C02 questions linked to AWS pricing.
AWS support plans practice questions
Practise CLF-C02 questions linked to AWS support plans.
AWS S3 practice questions
Practise CLF-C02 questions linked to AWS S3.
AWS EC2 practice questions
Practise CLF-C02 questions linked to AWS EC2.
Practice this exam
Start a free CLF-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CLF-C02 question test?
Billing, Pricing, and Support — This question tests Billing, Pricing, and Support — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The tags have not been activated as cost allocation tags in the Billing and Cost Management console. — B is correct because cost allocation tags must be explicitly activated in the Billing and Cost Management console before they appear in AWS Cost Explorer. Even though the 'Project' tag is applied to EC2 instances and visible in the EC2 console, AWS does not automatically treat resource tags as cost allocation tags; activation is a separate, required step. Without activation, Cost Explorer cannot filter or group by that tag.
What should I do if I get this CLF-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More CLF-C02 practice questions
- A company publishes a message each time a new product is added to its catalogue. Three services need to receive this mes…
- A media company stores frequently accessed video thumbnails in Amazon S3. The thumbnails are read multiple times every d…
- A company needs a service to translate domain names (like www.example.com) into IP addresses, check the health of their…
- A startup runs an application on AWS and receives a monthly bill that charges exactly for the number of compute hours us…
- A financial institution runs its core banking application on-premises due to regulatory requirements. It has connected i…
- A company wants to run a MySQL database in AWS without managing database software installation, applying patches, settin…
Last reviewed: Jun 11, 2026
This CLF-C02 practice question is part of Courseiva's free Amazon Web Services 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 CLF-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.