Pricing And Support Basics — AWS Cloud Practitioner (CLF-C02)
Support plans have hard capability boundaries
Candidates conflate cost visibility tools with billing controls, and support tiers with service limits. AWS Budgets sets spend thresholds and alerts; Cost Explorer analyzes historical and projected costs. Savings Plans and Reserved Instances reduce compute costs through commitment — but apply to different service scopes. CLF-C02 tests whether you can match the tool to the requirement, not whether you know pricing tiers by dollar amount.
What This Pattern Tests
The exam tests billing mechanics beyond service names. AWS Free Tier includes 12-month offers (750 hours/month t2.micro EC2, 5GB S3), always-free offers (1 million Lambda invocations/month, 25GB DynamoDB), and short-term trials (Amazon Redshift, Amazon Inspector). The trap is assuming Lambda is free forever (it is, up to 1M requests) while assuming EC2 t2.micro is always free (it expires after 12 months). Support plan differences matter: Basic gives no technical support, Developer gives business-hours email, Business gives 24/7 phone with <1hr response for production down, Enterprise adds a TAM and <15min response for business-critical.
Decision Axis
Free tier type (permanent vs. expiring vs. trial) and support tier (response time SLA vs. cost) are the tested distinctions.
Associated Traps
More Top Traps on This Exam
Decision Rules
Determine which EC2 purchasing option delivers the greatest cost savings for a predictable, always-on, uninterruptible workload without introducing capacity or availability risk.
Distinguish whether the requirement is for proactive threshold alerting (AWS Budgets) versus historical cost analysis and trend forecasting (AWS Cost Explorer).
Does centralized third-party software procurement with AWS-unified billing route through AWS Marketplace or through upgrading the AWS Support plan?
Whether commitment-based EC2 savings should be achieved through Compute Savings Plans (flexible $/hr commitment across instance families and Regions) or Standard Reserved Instances (deeper per-instance discount but locked to a specific type and AZ), given a workload that will change instance families during the commitment window.
Does consolidated billing through AWS Organizations automatically share Reserved Instance and Savings Plan discounts across linked accounts without requiring cross-account IAM permissions or any additional billing configuration?
Which is the minimum AWS Support tier that provides a designated (dedicated, named) TAM, as opposed to Enterprise On-Ramp which provides only access to a shared pool of TAMs?
Does the combination of continuous predictable usage and an anticipated instance-family change favor Compute Savings Plans (hourly-spend commitment, cross-family flexibility) over Standard Reserved Instances (deeper nominal discount but locked to a specific instance type and AZ)?
Whether a workload's non-interruptible, stateful, fixed-duration characteristics disqualify Spot Instances as the cost-reduction mechanism and mandate a commitment-based purchasing model (Reserved Instances) instead.
Domain Coverage
Difficulty Breakdown