- A
Buffer jobs in Amazon SQS and let workers scale from queue depth.
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.
- B
Run the workers on AWS Fargate Spot, since interruptions are acceptable.
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.
- C
Keep a fixed fleet of m6i.large instances in an Auto Scaling group with a higher minimum.
Why wrong: 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.
- D
Use Reserved Instances for the workers even though demand is highly bursty.
Why wrong: Incorrect. Reserved Instances work best for stable, predictable utilization. Bursty workers would leave committed capacity unused much of the time, which wastes money.
- E
Process uploads only during a nightly window so the fleet looks busier.
Why wrong: 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.
SAA-C03 Design Cost-Optimized Architectures Practice Question
This SAA-C03 practice question tests your understanding of design cost-optimized architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: amazon SQS decouples components, buffering messages between producers and consumers.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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.
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.
Option A is correct because Amazon SQS can decouple the upload bursts from the worker fleet, allowing the workers to scale based on the ApproximateNumberOfMessagesVisible metric via a target tracking scaling policy. This eliminates idle capacity by keeping workers at zero when no jobs are queued and scaling up only when bursts arrive. Option B is correct because AWS Fargate Spot provides up to a 70% discount over On-Demand, and since each transform can be retried safely from the beginning, interruptions are acceptable without data loss.
Key principle: Amazon SQS decouples components, buffering messages between producers and consumers.
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.
Related concept
Amazon SQS decouples components, buffering messages between producers and consumers.
- ✓
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.
Related concept
Amazon SQS decouples components, buffering messages between producers and consumers.
- ✗
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.
- ✗
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.
- ✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose Reserved Instances for any cost reduction scenario, forgetting that bursty workloads with idle periods are better served by spot instances and serverless scaling, not commitment-based discounts.
Detailed technical explanation
How to think about this question
SQS integrates with Auto Scaling via the SQS queue depth metric, which is more responsive than CPU utilization for decoupled workloads. Fargate Spot tasks run on spare AWS capacity and can be reclaimed with a two-minute warning, but since each job is idempotent and retriable, the interruption is handled gracefully by re-queuing the message. Under the hood, SQS uses a short poll or long poll mechanism; long poll (WaitTimeSeconds up to 20) reduces empty responses and costs by minimizing API calls.
KKey Concepts to Remember
- Amazon SQS decouples components, buffering messages between producers and consumers.
- SQS queue depth can be used as a metric to trigger Auto Scaling group adjustments.
- Decoupling with SQS helps smooth bursty workloads and prevent worker overload.
- Scaling based on SQS queue depth optimizes costs by matching compute to demand.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Amazon SQS decouples components, buffering messages between producers and consumers.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Review amazon SQS decouples components, buffering messages between producers and consumers., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
Design Cost-Optimized Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Cost-Optimized Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Cost-Optimized Architectures — This question tests Design Cost-Optimized Architectures — Amazon SQS decouples components, buffering messages between producers and consumers..
What is the correct answer to this question?
The correct answer is: Buffer jobs in Amazon SQS and let workers scale from queue depth. — Option A is correct because Amazon SQS can decouple the upload bursts from the worker fleet, allowing the workers to scale based on the ApproximateNumberOfMessagesVisible metric via a target tracking scaling policy. This eliminates idle capacity by keeping workers at zero when no jobs are queued and scaling up only when bursts arrive. Option B is correct because AWS Fargate Spot provides up to a 70% discount over On-Demand, and since each transform can be retried safely from the beginning, interruptions are acceptable without data loss.
What should I do if I get this SAA-C03 question wrong?
Review amazon SQS decouples components, buffering messages between producers and consumers., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Amazon SQS decouples components, buffering messages between producers and consumers.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.