AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A media analytics company runs a large-scale video processing application on AWS. The application uses a fleet of c5.4xlarge EC2 instances within an Auto Scaling group to transcode video files. The workload is stateless and designed to be fault-tolerant; interrupted jobs can be safely restarted. The processing jobs can run at any time but must be completed within a 24-hour window. The company is facing high compute costs and wants to implement a more cost-conscious architecture without compromising the ability to complete the daily batch of jobs. Which strategy provides the MOST significant cost savings while maintaining the required processing capacity?
Purchase a one-year, All Upfront Compute Savings Plan to cover the baseline usage of the c5.4xlarge instances.
Replace the Auto Scaling group with a Spot Fleet that is configured to request only c5.4xlarge Spot Instances.
Analyze CloudWatch metrics to rightsize the instances from c5.4xlarge to a smaller instance type and continue using an On-Demand Auto Scaling group.
Reconfigure the Auto Scaling group to use a mixed instances policy with a launch template that specifies multiple instance types and prioritizes Spot Instances over On-Demand Instances.
The correct answer is to reconfigure the Auto Scaling group to use a mixed instances policy. This approach allows the use of both Spot Instances and On-Demand Instances across various instance types. For a stateless and fault-tolerant workload like video transcoding, Spot Instances are ideal as they offer discounts of up to 90% compared to On-Demand prices. Using a mixed instances policy that is flexible across multiple instance types (e.g., from the C, M, and R families) and Availability Zones increases the likelihood of acquiring Spot capacity and improves resilience against interruptions in any single Spot pool. This strategy provides the greatest cost savings while ensuring the workload can be completed.
Incorrect answers:
Purchasing a Compute Savings Plan provides a good discount but is less cost-effective than Spot Instances for this type of interruptible workload. Savings Plans offer up to 66-72% savings for a commitment, whereas Spot savings can reach 90%. This option is better suited for stable, predictable workloads, not for maximizing savings on a fault-tolerant batch job.
Only rightsizing the instances, while a valid cost-optimization technique, does not leverage the significant discounts available through different purchasing options. The savings from rightsizing alone would be much lower than those achieved by incorporating Spot Instances.
Using a Spot Fleet with a single instance type is a risky strategy. While it uses cost-effective Spot Instances, relying on a single pool (one instance type in one AZ) makes the application vulnerable to interruptions if that specific Spot capacity becomes unavailable. A mixed instances policy is superior because it diversifies the request across multiple capacity pools, increasing availability.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a mixed instances policy in an Auto Scaling group?
Open an interactive chat with Bash
How do Spot Instances offer cost savings, and what are their limitations?
Open an interactive chat with Bash
Why is instance diversification important when using Spot Instances?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Continuous Improvement for Existing Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access