Optimizing Costs for Predictable EC2 Workloads
Short answer
C Savings Plans provide the best cost optimization for predictable, long-term compute workloads without compromising availability.
Question
Key Takeaways
Tests the ability to match workload predictability with the correct AWS pricing strategy, highlighting the trap of confusing Spot Instances with long-term commitments.
Determines the optimal pricing model for predictable Amazon EC2 workloads over a three-year period. Establishes that Savings Plans offer the best balance of cost reduction and operational flexibility compared to other options.
Common mistake: Selecting On-Demand Instances because they require no commitment, or Spot Instances due to lower upfront costs, ignoring the stability required for critical workloads.
Expert Analysis
Why the Answer Is Correct
Savings Plans are designed specifically for customers who have predictable usage patterns. By committing to a consistent amount of usage (measured in $/hour) for a 1- or 3-year term, you receive significant discounts compared to On-Demand pricing. Since the question specifies a 'predictable compute workload' lasting '3 years,' this is the ideal scenario for Savings Plans.
Why the Other Options Are Wrong
Spot Instances provide the deepest discounts but come with the risk of interruption when AWS needs capacity back, making them unsuitable for 'critical' workloads where availability is paramount. On-Demand Instances offer maximum flexibility but at the highest price point, failing the 'optimize costs' requirement. Dedicated Hosts are for physical server isolation compliance needs, not general cost optimization for standard compute.
Community Comment Notes
The community consensus strongly supports Savings Plans as the most cost-effective option for long-term, predictable use. One user questioned why On-Demand wasn't chosen, likely overlooking the cost optimization constraint. Another user confirmed the logic by noting that Savings Plans align with the 3-year timeline mentioned in the prompt.
Exam Strategy
Always look for keywords like 'predictable', 'steady-state', or specific timeframes (1 year, 3 years) to trigger the Savings Plan decision tree. If the workload is non-critical and intermittent, consider Spot Instances instead.
Frequently Asked Questions
Why can't I use Spot Instances for a critical workload?
What is the difference between Reserved Instances and Savings Plans?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
ShaiTay 👍 1 Answered CC. Savings Plans - most cost-effective option for predictable, long-term use
-
Meow7 👍 1c is correct please help discussion on 570 ~ 574
-
Naantje 👍 1Why not D?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →