SAA-C03 Design Cost-Optimized Architectures Practice Question
A company processes product-image uploads in bursts. Each transform takes up to ten minutes, and every job can be retried safely from the beginning. The current EC2 worker fleet is idle most of the day. Which two changes most reduce cost and idle capacity? Select two.
⚠ Common exam trap
Many candidates think a fixed fleet or Reserved Instances are cheaper for predictable workloads, but they overlook that bursty, idle-heavy patterns require elastic scaling and spot pricing to truly minimize cost.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Buffer jobs in Amazon SQS and let workers scale from queue depth.
Amazon SQS decouples the bursty upload workload from the worker fleet. By using SQS queue depth as the metric for an Auto Scaling policy, workers scale up only when jobs are waiting and scale down to zero during idle periods, eliminating wasted capacity. This directly reduces cost by matching compute resources to actual demand.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Buffer jobs in Amazon SQS and let workers scale from queue depth.
Why this is correct
Correct. SQS decouples uploads from processing and smooths bursty demand. Queue depth is a practical scaling signal, so the company avoids paying for idle workers while still absorbing traffic spikes.
- ✓
Run the workers on AWS Fargate Spot, since interruptions are acceptable.
Why this is correct
Correct. Fargate Spot lowers container compute cost when the workload can tolerate interruption and retry. For retry-safe image processing, the cost savings are significant compared with always-on EC2 workers.
- ✗
Keep a fixed fleet of m6i.large instances in an Auto Scaling group with a higher minimum.
Why it's wrong here
Incorrect. A higher minimum keeps capacity running even when the queue is empty, so idle cost remains high. It also does not provide the burst efficiency that queued, event-driven processing gives you.
When this WOULD be correct
For a steady-state workload with predictable demand that requires consistent compute capacity, such as a 24/7 web server farm, a fixed fleet with a higher minimum in an Auto Scaling group ensures availability and performance.
- ✗
Use Reserved Instances for the workers even though demand is highly bursty.
Why it's wrong here
Incorrect. Reserved Instances work best for stable, predictable utilization. Bursty workers would leave committed capacity unused much of the time, which wastes money.
When this WOULD be correct
A question where workers run a steady, predictable workload 24/7 (e.g., a real-time video transcoding pipeline with constant throughput). Reserved Instances would then provide significant cost savings over On-Demand.
- ✗
Process uploads only during a nightly window so the fleet looks busier.
Why it's wrong here
Incorrect. Batch scheduling may reduce perceived complexity, but it increases latency and does not inherently reduce compute cost if the same amount of work must still be done.
When this WOULD be correct
This option would be correct if the question required meeting a compliance or business rule that all processing must occur during off-peak hours (e.g., to avoid interfering with other systems), and cost reduction was not the primary goal.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Buffer jobs in Amazon SQS and let workers scale from queue depth.Correct answer▾
Why this is correct
Correct. SQS decouples uploads from processing and smooths bursty demand. Queue depth is a practical scaling signal, so the company avoids paying for idle workers while still absorbing traffic spikes.
✗Keep a fixed fleet of m6i.large instances in an Auto Scaling group with a higher minimum.Wrong answer — click to see why▾
Why this is wrong here
Keeping a fixed fleet with a higher minimum increases idle capacity and cost, as workers are idle most of the day. The goal is to reduce idle capacity, not increase it.
★ When this WOULD be the correct answer
For a steady-state workload with predictable demand that requires consistent compute capacity, such as a 24/7 web server farm, a fixed fleet with a higher minimum in an Auto Scaling group ensures availability and performance.
Why candidates choose this
Candidates may think a fixed fleet simplifies management and ensures capacity, overlooking the bursty nature of the workload and the cost of idle resources.
✗Use Reserved Instances for the workers even though demand is highly bursty.Wrong answer — click to see why▾
Why this is wrong here
Reserved Instances require a 1- or 3-year commitment and are cost-effective only for steady-state workloads. The bursty, idle-most-day pattern means RIs would be wasted during idle periods, increasing cost without reducing idle capacity.
★ When this WOULD be the correct answer
A question where workers run a steady, predictable workload 24/7 (e.g., a real-time video transcoding pipeline with constant throughput). Reserved Instances would then provide significant cost savings over On-Demand.
Why candidates choose this
Candidates know Reserved Instances reduce costs and may assume any cost-saving measure applies, overlooking that RIs are ill-suited for variable or bursty demand.
✗Process uploads only during a nightly window so the fleet looks busier.Wrong answer — click to see why▾
Why this is wrong here
Processing uploads only during a nightly window does not reduce cost or idle capacity; it simply shifts the workload to a specific time, leaving the fleet idle for the rest of the day and potentially requiring larger capacity to handle the burst.
★ When this WOULD be the correct answer
This option would be correct if the question required meeting a compliance or business rule that all processing must occur during off-peak hours (e.g., to avoid interfering with other systems), and cost reduction was not the primary goal.
Why candidates choose this
Candidates may think that batching work into a fixed window increases utilization and reduces idle time, but it actually concentrates demand, requiring more resources to handle the peak and leaving resources idle outside the window.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
One of 302 original SAA-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.