Billing Basics — CLF-C02 practice questions
Practice questions for this topic, with explained answers.
Domain: Billing, Pricing, and Support ·100 questions · 30 easy · 40 intermediate · 30 hard · page 5 of 7
Question 61 clf-billing-basics-061
Intermediate · Choose one
A company activates a new user-defined cost allocation tag but does not see it in Cost Explorer immediately. What should it expect?
- a Tags can take up to 24 hours to appear in the AWS Billing and Cost Management console
- b Tags appear only after the next monthly invoice is generated
- c Tags appear within a few seconds, so a delay indicates the tag was applied incorrectly
- d Tags appear only after an AWS Cost and Usage Report has been configured
Show answer & explanation
Answer: A
Why A is correct
AWS documents that all tags can take up to 24 hours to appear in the Billing and Cost Management console after activation. Knowing this prevents a common mistake, which is re-tagging resources or reconfiguring reports in response to a delay that is simply normal processing time. It also reinforces why tagging should be established as resources are created rather than retrofitted when a report is due.
Why the others are wrong
- B — Cost allocation tags surface in Cost Explorer and cost allocation reports during the current billing period, not only after invoicing.
- C — Billing data processing is not instantaneous. A delay of a few hours is expected behavior rather than a sign of misconfiguration.
- D — A Cost and Usage Report is one place tags appear, but activation is not conditional on having configured one.
Last verified: 2026-09-01
Question 62 clf-billing-basics-062
Intermediate · Choose one
Which account can activate cost allocation tags for an organization in the AWS Billing and Cost Management console?
- a Any member account, for its own resources
- b Any account that has the AWS Business Support+ plan
- c Only an account that has enabled AWS Cost and Usage Reports
- d Only the management account of the organization
Show answer & explanation
Answer: D
Why D is correct
AWS states that only the management account in an organization, along with standalone accounts that are not organization members, has access to the cost allocation tags manager in the Billing console. Centralizing activation is what keeps the organization's cost taxonomy consistent, since a tag key activated once becomes a reporting dimension across every account in the organization.
Why the others are wrong
- A — Member accounts can apply tags to their own resources, but they cannot activate a tag key as a cost allocation dimension. That control sits with the management account.
- B — AWS Support plans govern support entitlements such as case severity and Trusted Advisor coverage. They do not determine who can activate cost allocation tags.
- C — Enabling a Cost and Usage Report is unrelated to the permission to activate tags.
Last verified: 2026-09-01
Question 63 clf-billing-basics-063
Intermediate · Choose one
A company is preparing a business case for migrating its on-premises data center to AWS and needs an estimate of the cost savings based on its existing server inventory and utilization. Which AWS service is designed for this?
- a AWS Budgets
- b AWS Compute Optimizer
- c Migration Evaluator
- d AWS Cost Explorer
Show answer & explanation
Answer: C
Why C is correct
Migration Evaluator builds a data-driven business case for migration. It collects inventory and utilization data from the existing on-premises environment and produces a directional cost projection for running those workloads on AWS, including the effect of licensing choices. It is the right tool at the point where an organization has not yet migrated and needs to justify the move financially.
Why the others are wrong
- A — AWS Budgets tracks and alerts on spend in an AWS account that already exists. It cannot model an on-premises estate.
- B — AWS Compute Optimizer rightsizes resources already running in AWS using CloudWatch metrics. It does not analyze on-premises servers for a migration business case.
- D — Cost Explorer analyzes AWS costs that have already been incurred, so it has nothing to report before the migration happens.
Last verified: 2026-09-01
Question 64 clf-billing-basics-064
Intermediate · Select 2 answers
Which TWO statements about AWS Organizations are correct? (Choose TWO.)
- a Joining an organization merges all member accounts into a single AWS account
- b Each member account receives its own invoice from AWS
- c Reserved Instance discounts apply only within the account that purchased them and can never be shared
- d Consolidated billing is provided at no additional charge
- e Service control policies define the maximum available permissions for accounts in the organization
Show answer & explanation
Answer: D and E
Why D and E are correct
AWS Organizations serves governance and finance at the same time. On the governance side, service control policies set the ceiling on what principals in member accounts are permitted to do, acting as a guardrail rather than a grant of permissions. On the finance side, consolidated billing costs nothing extra: AWS provides one bill, pooled usage for volume tiering, and shared commitment discounts as part of the service.
Why the others are wrong
- A — Accounts remain distinct security and resource boundaries after joining an organization. Organizations groups accounts; it does not merge them.
- B — The management account receives the bill for the organization. Member accounts can view their own costs but are not invoiced separately.
- C — Reserved Instance and Savings Plans discounts are shared across the organization by default when discount sharing is enabled, applying to the owning account first and then to other accounts.
Last verified: 2026-09-01
Question 65 clf-billing-basics-065
Intermediate · Select 2 answers
Which TWO benefits does a well-implemented resource tagging strategy provide? (Choose TWO.)
- a Tags automatically prevent resources from exceeding a defined monthly budget
- b Tagged resources automatically receive a discount on their hourly rate
- c Resources can be identified and filtered for automation, access control, and operational tasks
- d Costs can be attributed to specific departments, projects, or environments in Cost Explorer and the AWS Cost and Usage Report
- e Tags encrypt the resources they are applied to
Show answer & explanation
Answer: C and D
Why C and D are correct
Tags are metadata that serve two distinct purposes at once. Financially, activated cost allocation tags become dimensions in Cost Explorer and the Cost and Usage Report, which is what turns an undifferentiated bill into departmental accountability. Operationally, the same tags let teams select resources for automation, apply attribute-based access control in IAM, and drive patching and backup policies. Both benefits depend on tagging being applied consistently as resources are created.
Why the others are wrong
- A — Tags do not enforce spending limits. AWS Budgets, optionally scoped by tag and combined with Budgets actions, is what enforces a threshold.
- B — Tags are descriptive metadata and have no effect on price. Discounts come from commitment mechanisms such as Savings Plans and Reserved Instances.
- E — Encryption is provided by services such as AWS KMS and by service-level encryption settings. A tag has no effect on the confidentiality of data.
Last verified: 2026-09-01
Question 66 clf-billing-basics-066
Hard · Choose one
A member account in an AWS Organizations organization purchased a Savings Plan. Its own usage does not consume the full hourly commitment. What happens to the unused portion?
- a It is refunded to the management account as a billing credit at the end of the month
- b It is automatically converted into an On-Demand Capacity Reservation in the purchasing account
- c It is applied to matching usage in other accounts in the organization, provided discount sharing is enabled
- d It is forfeited, because a Savings Plan applies only to the account that purchased it
Show answer & explanation
Answer: C
Why C is correct
Commitment benefits are applied to the owning account first, and any remaining benefit is then made available to matching usage elsewhere in the organization. This is the mechanism that makes central commitment purchasing efficient, because a single plan can absorb usage across many accounts rather than stranding unused commitment. The management account controls whether Reserved Instance and Savings Plans discount sharing is enabled, and both the purchasing and the receiving account must have sharing active.
Why the others are wrong
- A — AWS does not refund unused commitment. The commitment is charged whether or not matching usage exists.
- B — Savings Plans and capacity reservations are unrelated constructs, and no automatic conversion occurs. Savings Plans never reserve capacity.
- D — Restricting a plan to its purchasing account is what happens only when discount sharing is deliberately turned off. AWS warns that doing so can raise the organization's total bill.
Last verified: 2026-09-01
Question 67 clf-billing-basics-067
Hard · Choose one
A company activates a cost allocation tag in June and wants June's costs, along with the previous three months, to be broken down by that tag. Which statement is correct?
- a Activating a tag automatically applies it to all historical billing data from the account's creation date
- b Activating a tag makes it available as a cost allocation dimension going forward, and AWS provides a separate backfill capability to apply it to earlier periods
- c Activating a tag applies only to resources created after activation, and there is no way to report on earlier periods by tag
- d Historical tag breakdowns require the tag to have been activated in the AWS Pricing Calculator before the resources were launched
Show answer & explanation
Answer: B
Why B is correct
Tag activation is forward-looking by default: once a tag key is activated it becomes available as a dimension in Cost Explorer and the Cost and Usage Report for subsequent billing data. For earlier periods, AWS provides a separate cost allocation tag backfill capability that applies the activated tag to historical data. Understanding the default behavior matters because it is the reason organizations are advised to establish and activate their tagging taxonomy early rather than when the first chargeback report is requested.
Why the others are wrong
- A — Activation alone does not rewrite historical billing data. That is what makes backfill a distinct, deliberate operation.
- C — Reporting on earlier periods is possible through backfill, so this overstates the limitation. It is also wrong that only newly created resources are covered; the tag applies to the resources that carry it.
- D — AWS Pricing Calculator plays no part in tagging or in billing data. It is a forward-looking estimation tool.
Last verified: 2026-09-01
Question 68 clf-billing-basics-068
Hard · Choose one
A company operates 40 AWS accounts under one organization. Its finance team wants each business unit to see and be accountable for its own costs, while the company continues to receive a single bill and keep its pooled discounts. Which approach meets this?
- a Create a separate AWS Organizations organization for each business unit, each with its own management account
- b Remove each business unit's accounts from the organization so that AWS invoices them separately
- c Ask AWS Support to split the monthly invoice into one invoice per business unit
- d Keep consolidated billing in place and use cost allocation tags and linked-account grouping in AWS Cost Explorer and the AWS Cost and Usage Report to attribute costs to each business unit
Show answer & explanation
Answer: D
Why D is correct
Consolidated billing and per-unit accountability are not in conflict. The organization keeps one bill and pooled volume and commitment discounts, while Cost Explorer and the Cost and Usage Report break the same data down by linked account and by activated cost allocation tag. This is the standard showback pattern: allocate visibility without fragmenting the billing relationship that produces the discounts.
Why the others are wrong
- A — Multiple organizations fragment usage across separate billing families, which loses the same pooled discounts and multiplies governance overhead.
- B — Removing accounts from the organization would give each unit its own bill, but it would also break up the pooled usage that earns volume tiering and shared commitment discounts, raising total cost.
- C — AWS issues one bill to the management account of an organization. Internal allocation is done with AWS cost management tools, not by requesting split invoices from Support.
Last verified: 2026-09-01
Question 69 clf-billing-basics-069
Hard · Choose one
A company deactivates Reserved Instance and Savings Plans discount sharing for several accounts in its organization, expecting to make each account's costs more predictable. What financial effect should it anticipate?
- a The organization's total monthly bill will fall, because each account is charged only for the commitment it purchased
- b The organization's total monthly bill is likely to rise, because unused commitment in one account can no longer offset matching usage in another
- c The total bill will be unchanged, because discount sharing affects only how costs are reported rather than what is charged
- d The commitments will be cancelled automatically and refunded on a pro rata basis
Show answer & explanation
Answer: B
Why B is correct
Discount sharing is what allows a commitment to find matching usage anywhere in the organization. When it is turned off, commitment that the owning account does not consume is simply wasted, while other accounts pay On-Demand rates for usage that the commitment could have covered. AWS warns explicitly that deactivating sharing can result in higher monthly bills. Per-account predictability is a real governance benefit, but it is bought with money, and the trade-off should be made deliberately.
Why the others are wrong
- A — Each account being charged in isolation is precisely what produces the increase, because commitments and usage can no longer be matched across accounts.
- C — Discount sharing changes which usage receives a discounted rate, so it changes the amount charged and not only the presentation.
- D — Turning off sharing does not cancel commitments. The purchasing account remains liable for the full term.
Last verified: 2026-09-01
Question 70 clf-billing-basics-070
Hard · Choose one
Which statement accurately describes what happens to cost data when a member account leaves an AWS Organizations organization?
- a Historical cost data is automatically transferred to the departing account's new organization
- b All historical cost data for that account is permanently deleted from both accounts
- c The departing account keeps all historical cost data, and the management account loses visibility of that account's past costs
- d The departing account loses access to the historical AWS Cost Explorer data from the period when it was a member, while the management account retains it
Show answer & explanation
Answer: D
Why D is correct
While an account is a member of an organization, its costs form part of the management account's consolidated billing data, and that record belongs to the management account. When the account leaves, it loses access to the Cost Explorer history covering its membership period, and the management account keeps it. Teams planning a divestiture or account migration should export the data they will need before the account is removed, because the departing account cannot see that history again unless it rejoins the same organization.
Why the others are wrong
- A — There is no transfer of historical billing data between organizations when an account moves.
- B — The data is not deleted. It remains available to the management account.
- C — This reverses the outcome. Retention sits with the management account, which owned the consolidated billing relationship.
Last verified: 2026-09-01
Question 71 clf-billing-basics-071
Easy · Choose one
Which AWS Support plan is included for every AWS customer at no additional charge?
- a AWS Unified Operations
- b Basic Support
- c AWS Business Support+
- d AWS Enterprise Support
Show answer & explanation
Answer: B
Why B is correct
Basic Support is included with every AWS account at no cost. It provides 24x7 access to customer service for account and billing questions, service limit increase requests, the AWS documentation, whitepapers and best practice guides, community support forums, and service health checks. It is the floor of the support model, which is why every paid plan is described in terms of what it adds on top of it.
Why the others are wrong
- A — AWS Unified Operations is a paid plan aimed at customers who need managed incident response, with the highest minimum commitment of all.
- C — AWS Business Support+ is a paid plan with a documented minimum monthly charge and tiered pricing based on AWS usage.
- D — AWS Enterprise Support is a paid plan with a minimum charge of USD 5,000 per month that adds a designated Technical Account Manager.
Last verified: 2026-09-01
Question 72 clf-billing-basics-072
Easy · Choose one
Which type of support case can a customer on the Basic Support plan NOT open with AWS Support?
- a Service limit increase requests
- b Technical support cases
- c Account and billing cases
- d Requests to close an AWS account
Show answer & explanation
Answer: B
Why B is correct
AWS documentation states plainly that a customer with Basic Support cannot create a technical support case. Basic Support covers account and billing questions and service limit increase requests, which are available to all customers, but any case about how a service behaves or why an application is failing requires a paid support plan. This is the single most reliable discriminator between Basic and every paid plan.
Why the others are wrong
- A — Service limit increase requests are one of the case types explicitly available to every customer regardless of support plan.
- C — Account and billing support is available to all AWS customers, including those on Basic Support, on a 24x7 basis.
- D — Account administration requests such as closing an account fall under account support, which Basic Support customers can access.
Last verified: 2026-09-01
Question 73 clf-billing-basics-073
Easy · Choose one
Which AWS service inspects a customer's AWS environment and provides recommendations across categories including cost optimization, performance, security, fault tolerance, service limits, and operational excellence?
- a AWS Config
- b AWS Trusted Advisor
- c Amazon Inspector
- d AWS CloudTrail
Show answer & explanation
Answer: B
Why B is correct
AWS Trusted Advisor runs automated checks against an AWS account and reports findings in six categories: cost optimization, performance, security, fault tolerance, service limits, and operational excellence. Because the cost optimization checks identify things like idle and underutilized resources and low reservation utilization, Trusted Advisor is frequently the first place a team looks when asked to reduce spend without a detailed analysis project.
Why the others are wrong
- A — AWS Config records resource configurations and evaluates them against rules for compliance and change auditing. It does not produce cost optimization or service limit recommendations.
- C — Amazon Inspector performs automated vulnerability scanning of workloads such as Amazon EC2 instances and container images. Its scope is security findings only.
- D — AWS CloudTrail records API activity for governance, compliance, and operational auditing. It answers who did what, not whether the environment follows best practices.
Last verified: 2026-09-01
Question 74 clf-billing-basics-074
Easy · Choose one
Which AWS resource shows a customer the health of AWS services and any events that specifically affect the resources in their own account?
- a Amazon CloudWatch dashboards
- b AWS Trusted Advisor
- c AWS Systems Manager OpsCenter
- d AWS Health Dashboard
Show answer & explanation
Answer: D
Why D is correct
The AWS Health Dashboard provides both a general view of AWS service availability and an account-specific view of events affecting the customer's own resources, including scheduled maintenance and changes that require action. It is available to all AWS customers at no additional cost and requires no setup, which makes it the first place to look when deciding whether a problem is on the AWS side or in the customer's own workload.
Why the others are wrong
- A — Amazon CloudWatch dashboards visualize metrics and logs from the customer's own resources and applications. They do not report on AWS service health.
- B — AWS Trusted Advisor evaluates an account against best practices. It reports on configuration and optimization, not on live AWS service events.
- C — Systems Manager OpsCenter aggregates and helps resolve operational issues that the customer's own tooling raises. It is not a source of AWS service health information.
Last verified: 2026-09-01
Question 75 clf-billing-basics-075
Easy · Choose one
Which AWS Support plan adds a designated Technical Account Manager?
- a No AWS Support plan includes a Technical Account Manager
- b Basic Support
- c AWS Business Support+
- d AWS Enterprise Support
Show answer & explanation
Answer: D
Why D is correct
A designated Technical Account Manager is the defining benefit of AWS Enterprise Support, and it also forms part of AWS Unified Operations. The TAM is a named AWS technical contact who provides strategic guidance, leads Well-Architected Reviews, and coordinates AWS resources around the customer's environment. Because the relationship is proactive and ongoing rather than case-driven, it is what distinguishes the top plans from plans that respond only when a case is opened.
Why the others are wrong
- A — AWS does provide designated Technical Account Managers, at the AWS Enterprise Support and AWS Unified Operations levels.
- B — Basic Support includes no technical support cases at all, let alone a named technical contact.
- C — AWS Business Support+ provides 24x7 access to Cloud Support Engineers by phone, web, and chat, plus full Trusted Advisor checks and the AWS Support API, but it does not include a designated TAM.
Last verified: 2026-09-01