CLF-C02 Billing, Pricing, and Support Practice Question
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?
⚠ Common exam trap
Watch out — candidates often 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.
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.
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.
- ✗
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
The iam:ListAccountAliases permission is specific to the IAM ReadOnly access level and is used to retrieve an account's alias, such as for the IAM sign-in URL. Cost Explorer's ability to display cost allocation tags depends on whether the tags have been activated as cost allocation tags in the Billing and Cost Management console, not on this IAM action. Moreover, accessing Cost Explorer requires permissions like aws-portal:ViewUsage or cur:GetUsage, not iam:ListAccountAliases, so this is an incorrect reason for the tags being absent.
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?”
Go deeper
Related to this question
About these practice questions
Courseiva writes every CLF-C02 question from scratch — 988 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 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.