The answer is to replace the self-managed RabbitMQ with Amazon SQS Standard. This is the best cost-optimization move because SQS Standard provides durable at-least-once delivery without requiring AMQP-specific features like exchanges or routing keys, which the application does not need. By eliminating the RabbitMQ cluster on EC2, you remove the operational overhead of managing instances and the fixed cost of running servers 24/7, switching to SQS’s pay-per-request pricing that scales with actual usage. On the SAA-C03 exam, this scenario tests your ability to match service features to application requirements—specifically, recognizing when a fully managed, simpler service can replace a self-managed one for cost savings. A common trap is assuming you must keep RabbitMQ for any async messaging, but the key is that SQS Standard handles durable, at-least-once delivery natively. Memory tip: If you don’t need AMQP’s routing or exchanges, “SQS saves servers and cash.”
SAA-C03 Design Cost-Optimized Architectures Practice Question
This SAA-C03 practice question tests your understanding of design cost-optimized architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.
Exhibit
Architecture inventory:
3 EC2 instances for RabbitMQ
2 EC2 instances for application workers
Average broker CPU: 8%-12%
Average broker memory: 18%-22%
Monthly ops time spent on broker patching, backups, and failover testing: 14 hours
Message requirements:
Durable queueing
At-least-once delivery acceptable
No need for broker-managed topics or complex routing
Failure note:
A node reboot caused a 9-minute enqueue outage last month
Based on the exhibit, the company runs a self-managed RabbitMQ cluster on EC2 for asynchronous work. The queue only needs durable at-least-once delivery, and the application does not require AMQP-specific features such as exchanges, routing keys, or broker plugins. Which change is the best cost-optimization move?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Clue: "least"
Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
Architecture inventory:
3 EC2 instances for RabbitMQ
2 EC2 instances for application workers
Average broker CPU: 8%-12%
Average broker memory: 18%-22%
Monthly ops time spent on broker patching, backups, and failover testing: 14 hours
Message requirements:
Durable queueing
At-least-once delivery acceptable
No need for broker-managed topics or complex routing
Failure note:
A node reboot caused a 9-minute enqueue outage last month
A
Replace RabbitMQ with Amazon SQS Standard and keep the workers unchanged except for the queue client library.
Amazon SQS is a fully managed queue that satisfies durable, at-least-once messaging without requiring broker administration. It removes the EC2 broker fleet, patching, backups, and failover testing, and it reduces outage risk from broker maintenance. Because the workload does not need AMQP-specific features such as exchanges or routing keys, SQS is the most cost-effective and operationally simple replacement.
B
Replace RabbitMQ with Amazon MQ for RabbitMQ to keep the same protocol and reduce costs.
Why wrong: Amazon MQ reduces some administration effort, but it is still a broker service with broker-related costs. For a workload that does not need AMQP-specific features, SQS is typically cheaper and simpler because it removes the broker layer entirely.
C
Increase the RabbitMQ instance size and add a fourth node for higher availability.
Why wrong: The exhibit shows very low CPU and memory utilization, so scaling the cluster up would raise cost without addressing the underlying self-managed broker overhead. It also does not eliminate the patching, backup, and failover-testing burden.
D
Move the queue to Amazon DynamoDB and use scans for consumers to detect new messages.
Why wrong: DynamoDB is not a queue service, and scanning it for work items is inefficient and expensive at scale. This would add complexity and would not provide the same messaging semantics as a real queue.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Replace RabbitMQ with Amazon SQS Standard and keep the workers unchanged except for the queue client library.
Option A is correct because Amazon SQS Standard provides at-least-once delivery and durable message storage without requiring AMQP-specific features like exchanges or routing keys. Replacing RabbitMQ with SQS eliminates the operational overhead of managing EC2 instances and RabbitMQ clusters, while SQS's pay-per-request pricing is more cost-effective than running EC2 instances 24/7 for a self-managed queue.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Replace RabbitMQ with Amazon SQS Standard and keep the workers unchanged except for the queue client library.
Why this is correct
Amazon SQS is a fully managed queue that satisfies durable, at-least-once messaging without requiring broker administration. It removes the EC2 broker fleet, patching, backups, and failover testing, and it reduces outage risk from broker maintenance. Because the workload does not need AMQP-specific features such as exchanges or routing keys, SQS is the most cost-effective and operationally simple replacement.
Clue confirmation
The clue words "best", "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Replace RabbitMQ with Amazon MQ for RabbitMQ to keep the same protocol and reduce costs.
Why it's wrong here
Amazon MQ reduces some administration effort, but it is still a broker service with broker-related costs. For a workload that does not need AMQP-specific features, SQS is typically cheaper and simpler because it removes the broker layer entirely.
✗
Increase the RabbitMQ instance size and add a fourth node for higher availability.
Why it's wrong here
The exhibit shows very low CPU and memory utilization, so scaling the cluster up would raise cost without addressing the underlying self-managed broker overhead. It also does not eliminate the patching, backup, and failover-testing burden.
✗
Move the queue to Amazon DynamoDB and use scans for consumers to detect new messages.
Why it's wrong here
DynamoDB is not a queue service, and scanning it for work items is inefficient and expensive at scale. This would add complexity and would not provide the same messaging semantics as a real queue.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume Amazon MQ for RabbitMQ is always the cheapest managed option, but SQS is more cost-effective when AMQP-specific features are not required, as it eliminates per-instance costs and leverages a serverless pricing model.
Trap categories for this question
Command / output trap
The exhibit shows very low CPU and memory utilization, so scaling the cluster up would raise cost without addressing the underlying self-managed broker overhead. It also does not eliminate the patching, backup, and failover-testing burden.
Detailed technical explanation
How to think about this question
Amazon SQS Standard uses a distributed, eventually consistent backend that guarantees at-least-once delivery, with a 256 KB message size limit and 14-day retention. Unlike RabbitMQ's AMQP protocol, SQS uses a simple HTTP API (Query/JSON), so the application only needs to swap the client library (e.g., from Pika to boto3) and can remove all RabbitMQ-specific logic for exchanges, bindings, and routing keys. In a real-world scenario, a company processing background jobs (e.g., image resizing) would benefit from SQS's auto-scaling and no idle costs, whereas RabbitMQ on EC2 requires provisioning for peak load and paying for unused capacity.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design Cost-Optimized Architectures — This question tests Design Cost-Optimized Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Replace RabbitMQ with Amazon SQS Standard and keep the workers unchanged except for the queue client library. — Option A is correct because Amazon SQS Standard provides at-least-once delivery and durable message storage without requiring AMQP-specific features like exchanges or routing keys. Replacing RabbitMQ with SQS eliminates the operational overhead of managing EC2 instances and RabbitMQ clusters, while SQS's pay-per-request pricing is more cost-effective than running EC2 instances 24/7 for a self-managed queue.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best", "least". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
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.