CLF-C02 Billing, Pricing, and Support Practice Question
A company's AWS bill has increased significantly. The finance team wants to implement cost governance best practices. Which action represents a foundational cost governance control?
⚠ Common exam trap
Watch out — candidates often confuse cost-saving mechanisms (like Spot Instances or deleting resources) with cost governance controls, which are about establishing policies and visibility (like tagging and enforcement) rather than immediate cost reduction actions.
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
✓
Implement a tagging strategy and enforce tags with AWS Config rules
Implementing a tagging strategy and enforcing tags with AWS Config rules is a foundational cost governance control because it enables cost allocation, tracking, and accountability. Tags allow the finance team to categorize resources by project, environment, or cost center, and AWS Config rules can automatically enforce tag compliance, preventing untagged resources from being launched. This directly supports cost governance by providing visibility and control over spending, which is the first step in optimizing costs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delete all non-production resources immediately
Why it's wrong here
Immediately deleting all non-production resources is a risky, heavy-handed reaction that ignores the need for cost attribution and ownership. Without first tagging resources and analyzing usage via AWS Cost Explorer, you may destroy development or test environments that are actively needed, and you forfeit the ability to make informed trade-offs. Proper governance begins with organizing resources through tags and cost allocation, then using lifecycle policies or scheduled shutdowns for idle workloads, not indiscriminate deletion.
- ✓
Implement a tagging strategy and enforce tags with AWS Config rules
Why this is correct
A tagging strategy, enforced through AWS Config rules, creates the foundational cost-attribution model for governance. For example, applying tags such as CostCenter, Environment, and Owner lets AWS Cost Explorer and cost allocation reports break down spending by team or project, while AWS Config rules like required-tags detect any untagged resource. With remediation actions, you can automatically apply tags, ensuring every resource is traceable to a business owner and cost decisions are data-driven.
- ✗
Switch all resources to Spot Instances
Why it's wrong here
Spot Instances offer significant discounts but are interruptible with as little as two minutes of warning before EC2 reclaims the capacity, making them unsuitable for stateful or production-critical workloads. Universal adoption would risk sudden termination of customer-facing systems, and many AWS services do not even support Spot pricing. A sound cost strategy reserves Spot for fault-tolerant, stateless tasks like batch processing or CI/CD workers, while using Savings Plans or Reserved Instances for steady-state demand.
- ✗
Enable all AWS services to trigger CloudWatch alarms
Why it's wrong here
CloudWatch alarms monitor operational metrics and trigger notifications based on thresholds, not cost attribution or resource governance. Enabling alarms for every service would generate excessive noise and add per-alarm charges without revealing which team or project owns the spend, and it does nothing to enforce tagging. Cost visibility requires tagging, AWS Budgets, and Cost Anomaly Detection, not simply turning on monitors across all resources.
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.