Pricing Misconception — AWS Cloud Practitioner (CLF-C02)
The answer assumed a pricing model that doesn't apply. Reserved vs. on-demand, data transfer costs, or tier thresholds tripped you up.
Free, reserved, and cheaper are not synonyms
Candidates read "no upfront cost" and reach for Free Tier. They read "lower cost" and reach for Reserved Instances. The exam tests whether you understand commitment windows, utilization requirements, and what each pricing construct actually guarantees. Cost language is precise on CLF-C02; treating it as interchangeable with "cheaper" is the mechanism of the trap.
The Scenario
A startup wants to reduce costs for a development environment running 8 hours per day, 5 days per week. You recommend Reserved Instances for the 40% savings. But RIs commit you to paying 24/7 whether the instance runs or not. For a workload running 29% of the time, you are paying for 71% idle hours. On-Demand with EC2 Instance Scheduler (stop/start automation) or even Spot Instances for fault-tolerant dev workloads cost less. The trap is applying the "RIs always save money" rule without calculating the break-even utilization point — which for 1-year No Upfront RIs is roughly 40-50% utilization.
How to Spot It
- •When you see "reduce costs," do not default to Reserved Instances. Calculate the actual utilization: hours running / hours in period. RIs only save money when utilization exceeds the break-even point for that commitment type. Dev environments, batch jobs, and seasonal workloads rarely qualify.
- •NAT Gateway data processing charges are $0.045/GB — a 1TB/month workload costs $45/month just in NAT processing, on top of the $0.045/hour fixed cost. Questions that describe high-throughput private subnets accessing the internet are testing whether you know NAT Gateway is not "free" infrastructure.
- •Data transfer across AZs is $0.01/GB each way. A chatty microservices architecture with 100GB/month cross-AZ traffic adds $2/month per direction — invisible until you multiply by dozens of services. The exam tests whether you spot cross-AZ transfer costs in architectures that replicate data between availability zones.
Decision Rules
Select the Cost Optimization pillar's elasticity principle (AWS Auto Scaling) as the governing answer, rather than conflating a purchasing-commitment option (Reserved Instances) or a static right-sizing tool (AWS Compute Optimizer) with the pillar's actual design intent for variable-demand workloads.
Does adopting Lambda's pay-per-invocation pricing model transfer customer-managed KMS key rotation and policy management to AWS, or does the customer retain that accountability regardless of compute abstraction level?
Choose between a durable pull-based queue (SQS) that retains messages until confirmed consumption versus a push-based notification service (SNS) that delivers once and discards, given the dominant constraint of resilient, worker-paced async decoupling.
Which service supports push-based fanout to heterogeneous subscriber types (email, Lambda, HTTPS) in a single publish operation versus an email-only delivery channel?
When the requirement is to isolate per-request latency across distributed service call chains — not aggregate metrics — select AWS X-Ray because it captures trace segments at each service hop; CloudWatch cannot reconstruct request-level call graphs across service boundaries.
When access scope is browser-only with no need for a persistent desktop, WorkSpaces Secure Browser is the correct fit; choosing WorkSpaces imposes full-desktop monthly per-user pricing for a use case that requires only an isolated browser session.
Determine which EC2 purchasing option delivers the greatest cost savings for a predictable, always-on, uninterruptible workload without introducing capacity or availability risk.
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.
Determine whether the security requirement calls for passive best-practice advisory (Trusted Advisor, already included in Business Support) or active continuous threat detection (GuardDuty, separate enablement and cost), where Trusted Advisor's inclusion in the existing support plan creates a pricing-based distractor that fails on the active-detection dimension.
Does the requirement for active DDoS Response Team engagement and financial cost protections require AWS Shield Advanced rather than the automatically-applied, no-cost AWS Shield Standard tier?
Domain Coverage
Difficulty Breakdown
Related Patterns