Amazon CLF-C02: Billing, Pricing & Support — Study Guide

By Laurynas Brazys · 28 July 2026 · #amazon #clf-c02 #certification #exam-prep #study-guide

Part of the AWS Cloud Practitioner CLF-C02 — Study Guide. Practice with verified answers in the Amazon exam hub, or take timed practice tests on ExamRoll.io.

Pricing models and compute cost optimization

AWS offers several purchasing models that let you balance cost, flexibility, and commitment for compute and other services. On-Demand pricing provides the most flexibility and no long-term commitment, making it appropriate for unpredictable workloads or development environments. Reserved Instances (RIs) and Savings Plans reward committed usage with lower hourly rates; RIs are tied to instance families or sizes (with Standard vs Convertible options), while Savings Plans offer broader coverage (Compute Savings Plans apply across instance families and regions, EC2 Instance Savings Plans are narrower). Spot Instances give the deepest discounts for interruptible, fault-tolerant workloads. Payment options—All Upfront, Partial Upfront, and No Upfront—affect effective hourly costs and accounting treatment. A frequent practitioner trap is selecting a long-term commitment without accurate utilization baselines, or confusing Savings Plans’ and RIs’ flexibility: RIs can be regional and instance-family–specific, while Savings Plans trade some of that specificity for simplicity. Use historical utilization from Cost Explorer and Compute Optimizer recommendations to decide whether to reserve capacity, buy a Savings Plan, or rely on Spot for batch jobs. Always factor in data transfer and storage costs, and plan breaks in commitments for architectural migrations where workload shape may change.

On‑Demand: no commitment, highest hourly cost
Reserved Instances (Standard/Convertible): commit 1–3 years, lower cost, varying flexibility
Savings Plans (Compute / EC2 Instance): commit $/hour for discounts across usage types
Spot Instances: deepest discounts for interruptible workloads

Cost visibility, forecasting and tooling

Visibility is the cornerstone of cost control. AWS Cost Explorer provides interactive cost and usage analytics, letting you filter by service, account, region, and tag to spot trends. The Cost and Usage Report (CUR) exports detailed line-item billing to Amazon S3 for downstream analytics, and the AWS Pricing Calculator helps estimate monthly costs before deployment. AWS Budgets lets you set cost, usage, and reservation purchase alerts and can trigger automated actions; Cost Anomaly Detection in AWS Cost Management uses machine learning to surface unexpected spikes. A common oversight is failing to enable the CUR or to apply standardized cost allocation tags; without these, reports and automated alerts lose fidelity. Combine Cost Explorer with Compute Optimizer and CloudWatch metrics to correlate spend with performance (for example, CPU utilization for EC2) to inform rightsizing. Forecasts should incorporate seasonal patterns and business growth; rely on Budgets with alert hooks to Slack or SNS for operational accountability. Finally, enable consolidated billing via AWS Organizations to aggregate discounts and simplify invoicing.

Key tools: AWS Cost Explorer, Cost and Usage Report (CUR), AWS Budgets, Cost Anomaly Detection, AWS Pricing Calculator

Governance, allocation and accountability

Cost governance blends policy, automation, and organization. AWS Organizations centralizes multiple accounts and provides consolidated billing, while Service Control Policies (SCPs) enforce guardrails at the account level. Tagging standards and automated tag policies ensure resources are tracked for chargeback and showback; enforcement through AWS Config rules and AWS CloudFormation templates reduces manual drift. Infrastructure as Code (IaC) with AWS CloudFormation or Terraform enables repeatable deployments that meet internal compliance controls, and integrating change controls with AWS Config and CloudTrail provides auditability. A typical practitioner mistake is treating governance as a one-time setup: policies, SCPs, and tag enforcement must evolve with business needs. Use AWS Budgets Actions to automate cost controls (for example, deny new instance launches when a budget threshold is crossed) and enable Cost Allocation Tags and Cost Categories for financial reporting. For accountability, map AWS accounts to business units and require budget ownership; this makes anomaly investigation faster and aligns incentives for optimization.

Governance elements: AWS Organizations, SCPs, Cost Allocation Tags, AWS Config, CloudFormation, Budgets Actions

Support, Trusted Advisor, security and compliance

Support and proactive security monitoring are essential ingredients of reliable operations. AWS Support tiers range from Basic to Enterprise; Business tier is the lowest-cost option that includes the full set of AWS Trusted Advisor checks, while Enterprise adds a Technical Account Manager and concierge billing. Trusted Advisor provides best-practice checks for cost optimization, security, fault tolerance, and performance; Security Hub, Amazon GuardDuty, and Amazon Inspector provide continuous threat detection and vulnerability assessment across accounts and workloads. For compliance needs such as write-once-read-many retention, Amazon S3 Object Lock (compliance mode) implements WORM behavior, and AWS Secrets Manager is the recommended managed service for storing and rotating application credentials securely. Network-level protections include Network ACLs (subnet-level stateless firewall) and Security Groups (instance-level stateful firewall); Route 53 provides DNS resolution globally. Common traps include underestimating the value of Business/Enterprise support for production SLAs, not enabling Trusted Advisor checks, and attempting to store secrets in plain configuration files instead of Secrets Manager or Parameter Store.

Support tiers (selected): Basic: billing & documentation; Developer: guidance for development; Business: full Trusted Advisor checks; Enterprise: TAM and privileged access

Practical Problem: Use-Case Scenario

Scenario: AcmeRetail runs a multi-account AWS environment with ecommerce web tiers on EC2, RDS for transactional data, and S3 for assets; costs have risen 40% year-over-year and finance lacks clear allocation across teams.
Challenge: Identify cost drivers, enforce cost governance, and reduce monthly spend without disrupting customer-facing services.

Recommended Approach:

Enable AWS Organizations with consolidated billing and activate the Cost and Usage Report to deliver detailed billing to an S3 bucket for analysis.
Use AWS Cost Explorer and Cost Anomaly Detection to identify top spend drivers and set AWS Budgets with SNS alerts for each account and workload.
Run Compute Optimizer and CloudWatch metrics to build rightsizing recommendations, then apply Savings Plans or RIs for steady-state compute and use Spot for batch jobs.
Implement tag policies, AWS Config rules, and Service Control Policies to enforce tagging and block noncompliant resource types; automate remediation for orphaned EBS snapshots and unattached ENIs.

Rationale: Consolidated visibility plus automated alerts and enforcement creates accountability and prevents cost drift; combining rightsizing with committed pricing options reduces spend while preserving availability for customer-facing systems.

← Security · All domains · Cloud Architecture →

Practice these questions → · Timed practice on ExamRoll.io →