Which AWS service handles sudden EC2 demand spikes at lowest cost?
A company deploys its application on Amazon EC2 instances. The application occasionally experiences sudden increases in demand. The company wants to ensure that its application can respond to changes in demand at the lowest possible cost. Which AWS service or concept will meet these requirements?
Community Insight
The question tests the difference between services that automatically provision capacity (elasticity) and services that merely report on or recommend capacity — the trap is picking a cost tool because the phrase "lowest possible cost" appears in the stem.
AWS Auto Scaling is the service that dynamically adds or removes EC2 instances as application demand rises and falls, keeping performance steady while charging only for the capacity actually needed. This page confirms why option A is the correct answer and explains why cost-visibility and advisory tools cannot scale capacity themselves.
Choosing AWS Cost Explorer or AWS Compute Optimizer because the question emphasizes "lowest possible cost"; both only visualize spend or generate rightsizing recommendations and never add or remove EC2 instances in response to live demand.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
AWS Auto Scaling is the only option that actually changes capacity in response to demand: it monitors metrics such as CPU utilization or request count that you attach to a scaling plan, then launches or terminates EC2 instances to match the load. Because capacity is added during spikes and removed once the spike passes, the company pays only for what it needs, which is exactly the combination of responsiveness and lowest cost the stem requires. This elasticity is a core AWS Cloud design principle and applies to EC2 Auto Scaling groups across multiple Availability Zones. As Kaushal1987 explained, Auto Scaling "automatically adjusts the number of Amazon EC2 instances based on application demand," adding instances when demand increases and removing them when it decreases. ShaiTay offered the same reasoning in one line: it "automatically adjusts number of EC2 instances due to demand."Why the Other Options Are Wrong
AWS Compute Optimizer is an advisory service: it analyzes utilization metrics and produces rightsizing recommendations for EC2 instances, EBS volumes, and Lambda functions, but a human or automation pipeline must act on those recommendations — it does not scale anything in real time. AWS Cost Explorer is a billing and cost-visibility tool for exploring spend by service, tag, or time period; it reports cost after the fact and cannot add capacity during a traffic spike. The AWS Well-Architected Framework is a set of architectural best practices and review questions, not a runtime service, so it can guide a design towards elasticity but cannot implement it. All three are useful complements to Auto Scaling, but none satisfies the requirement to respond to demand changes automatically.Community Comment Notes
Both commenters converge on AWS Auto Scaling and frame it in the same way: capacity is added on the upswing and removed on the downswing so that cost tracks actual usage. Kaushal1987 additionally stresses that this "helps maintain performance while minimizing costs by using only the resources needed," which mirrors the two-part requirement in the question stem. ShaiTay's shorter confirmation repeats the demand-driven adjustment of instance count. Notably, neither commenter was distracted by the cost-related wording in the question, which is the most likely source of error for other candidates.Official Reference
Exam Strategy
When a stem asks to handle variable demand while minimizing cost, map the verbs: "respond automatically" points to a scaling service, while "analyze" or "recommend" points to Compute Optimizer or Cost Explorer. Read past cost-flavored keywords so you do not mistake a reporting tool for a control-plane service.
Frequently Asked Questions
Why is AWS Compute Optimizer wrong if it also helps reduce EC2 cost?
Compute Optimizer only produces rightsizing recommendations from utilization data; it never launches or terminates instances during a live demand spike, so it cannot deliver automatic responsiveness.
Why is AWS Cost Explorer not the answer for lowest possible cost?
Cost Explorer is a reporting tool that shows past and forecasted spend. Visibility into cost is not the same as automatically scaling capacity up and down with demand.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →