CLF-C02 Billing, Pricing, and Support Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  AWS Budgets with budget alerts only

  Why it's wrong here

  While AWS Budgets can send email or SNS alerts when actual or forecasted spending crosses a threshold, budget alerts by themselves are informational and require manual follow-up or a separate automation to affect resources. Without AWS Budgets Actions attached to a threshold, the alert simply notifies you—no EC2/RDS instance is stopped, no IAM policy is applied, and usage continues to accrue cost. Therefore, alerts alone are an insufficient mechanism for automatically stopping cost overruns.

• ✓

  AWS Budgets Actions

  Why this is correct

  AWS Budgets Actions are the correct answer because they enable automated responses to budget threshold breaches, directly controlling spending. You can configure an action to apply an IAM policy that denies further resource access, stop EC2 or RDS instances, or invoke a Lambda function for custom remediation. These actions trigger automatically when the budget exceeds the defined threshold, eliminating the need for human intervention. This is precisely the mechanism that both alerts and automatically enforce cost limits.

• ✗

  AWS Cost Explorer spending forecasts

  Why it's wrong here

  AWS Cost Explorer spending forecasts project future costs using historical usage patterns, but the service is purely analytical—it produces charts and reports and offers no controls to modify cloud resources. Forecasts help you anticipate cost trends, yet they cannot stop an instance, apply restrictions, or execute any remediation when a predicted cost threshold is approached. Because Cost Explorer has no native automation endpoints, it cannot satisfy a requirement to automatically stop or reduce resource usage based on cost thresholds.

• ✗

  AWS Service Quotas

  Why it's wrong here

  AWS Service Quotas manage the maximum number of resources you can provision, such as vCPU limits per region or concurrent Lambda executions, but these limits are unrelated to monetary spending. Your account could easily exceed a cost budget while staying far below every service quota, so quotas provide no cost-triggered mechanism. Also, Service Quotas are static limits that you can request increases for; they cannot be configured to react to budget thresholds or stop resources. Thus, they are not an appropriate tool for automatic cost control.

Go deeper

Related to this question