The answer is Amazon SQS, because it provides a durable, scalable message buffer that decouples the web tier from fulfilment workers, absorbing traffic spikes without losing requests. When order bursts overwhelm the downstream service, SQS stores each message reliably, allowing workers to poll at their own pace and automatically retry failed messages—eliminating the need for custom operational scripts. On the SAA-C03 exam, this pattern tests your understanding of decoupling and buffering in serverless architectures; a common trap is choosing Amazon Kinesis for real-time streaming when the requirement is simply to absorb bursts and retry, not process data in order. Remember the key distinction: SQS is for asynchronous decoupling and spike absorption, while Kinesis is for real-time data ingestion. Memory tip: think “SQS = Squash the Spike Quietly” to recall its role as a managed buffer that lets downstream services process at their own speed.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: amazon SQS is a fully managed message queuing service.. 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 warehouse integration service receives bursts of orders that sometimes overwhelm a downstream fulfilment service. The architecture must absorb spikes and retry processing without losing requests. Which service should be placed between the web tier and fulfilment workers? The design must avoid adding custom operational scripts.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Amazon SQS queue
Amazon SQS is the correct choice because it acts as a durable, scalable message buffer that decouples the web tier from the fulfilment workers. When order bursts arrive, messages are stored reliably in the queue, and workers can poll at their own pace, retrying failed messages automatically without any custom scripts. This pattern absorbs spikes and ensures no requests are lost, meeting the requirement for a fully managed, serverless integration.
Key principle: Amazon SQS is a fully managed message queuing service.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
AWS WAF
Why it's wrong here
WAF filters web requests but does not buffer application jobs.
✗
Amazon Route 53 weighted routing
Why it's wrong here
Weighted routing distributes DNS responses but does not absorb processing spikes.
✓
Amazon SQS queue
Why this is correct
SQS decouples producers and consumers, buffers bursts, and supports retries through visibility timeout and dead-letter queues.
Related concept
Amazon SQS is a fully managed message queuing service.
✗
Amazon CloudFront
Why it's wrong here
CloudFront caches content but does not queue work for backend processing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse load-balancing or traffic-routing services (like Route 53 or CloudFront) with message queuing, mistakenly thinking they can absorb processing spikes, whereas only a queue like SQS provides durable storage and asynchronous decoupling for request bursts.
Detailed technical explanation
How to think about this question
Amazon SQS uses a distributed, highly available message store with a default retention period of 4 days (configurable up to 14 days) and supports at-least-once delivery, meaning a message can be delivered more than once if the consumer does not delete it after processing. The queue acts as a buffer that decouples producers from consumers, allowing the fulfilment workers to scale independently based on the queue depth (visible in CloudWatch metrics like ApproximateNumberOfMessagesVisible). In a real-world scenario, if the downstream fulfilment service fails or becomes slow, messages remain in the queue and can be retried via a dead-letter queue (DLQ) after a configurable number of receive attempts, preventing any data loss.
KKey Concepts to Remember
Amazon SQS is a fully managed message queuing service.
SQS decouples producers and consumers, improving fault tolerance.
Visibility timeout allows messages to be hidden during processing and retried if processing fails.
Dead-Letter Queues (DLQs) capture messages that fail processing after a specified number of retries.
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 is a fully managed message queuing service.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review amazon SQS is a fully managed message queuing service., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design Resilient Architectures — This question tests Design Resilient Architectures — Amazon SQS is a fully managed message queuing service..
What is the correct answer to this question?
The correct answer is: Amazon SQS queue — Amazon SQS is the correct choice because it acts as a durable, scalable message buffer that decouples the web tier from the fulfilment workers. When order bursts arrive, messages are stored reliably in the queue, and workers can poll at their own pace, retrying failed messages automatically without any custom scripts. This pattern absorbs spikes and ensures no requests are lost, meeting the requirement for a fully managed, serverless integration.
What should I do if I get this SAA-C03 question wrong?
Review amazon SQS is a fully managed message queuing service., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Amazon SQS is a fully managed message queuing service.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A warehouse integration service receives bursts of orders that sometimes overwhelm a downstream fulfilment service. The architecture must absorb spikes and retry processing without losing requests. Which service should be placed between the web tier and fulfilment workers?
medium
A.AWS WAF
B.Amazon Route 53 weighted routing
✓ C.Amazon SQS queue
D.Amazon CloudFront
Why C: Amazon SQS is the correct choice because it acts as a durable, fully managed message queue that decouples the web tier from the fulfilment workers. It can absorb bursts of orders by storing messages durably, and workers can poll the queue at their own pace, with built-in retry logic via visibility timeouts and dead-letter queues to ensure no requests are lost.
Variation 2. A warehouse integration service receives bursts of orders that sometimes overwhelm a downstream fulfilment service. The architecture must absorb spikes and retry processing without losing requests. Which service should be placed between the web tier and fulfilment workers? The architecture review board prefers a managed AWS-native control.
medium
A.AWS WAF
B.Amazon Route 53 weighted routing
✓ C.Amazon SQS queue
D.Amazon CloudFront
Why C: Amazon SQS is the correct choice because it acts as a fully managed message queue that decouples the web tier from the fulfilment workers, buffering incoming order bursts. It provides at-least-once delivery and allows workers to poll messages at their own pace, ensuring no requests are lost even during spikes. SQS also supports retries via a dead-letter queue (DLQ) for messages that fail processing, meeting the requirement for resilient, managed AWS-native control.
Variation 3. A patient portal receives bursts of orders that sometimes overwhelm a downstream fulfilment service. The architecture must absorb spikes and retry processing without losing requests. Which service should be placed between the web tier and fulfilment workers?
medium
A.AWS WAF
B.Amazon CloudFront
✓ C.Amazon SQS queue
D.Amazon Route 53 weighted routing
Why C: Amazon SQS is the correct choice because it acts as a durable, highly available message buffer between the web tier and the fulfilment workers. It decouples the components, allowing the web tier to enqueue requests immediately without waiting for the downstream service, and the workers can poll and process messages at their own pace. SQS automatically retains messages for up to 14 days and supports retries via a dead-letter queue, ensuring no requests are lost even during spikes.
Variation 4. A patient portal receives bursts of orders that sometimes overwhelm a downstream fulfilment service. The architecture must absorb spikes and retry processing without losing requests. Which service should be placed between the web tier and fulfilment workers? The team wants the control to be enforceable during normal operations.
medium
A.AWS WAF
B.Amazon CloudFront
✓ C.Amazon SQS queue
D.Amazon Route 53 weighted routing
Why C: Amazon SQS is the correct choice because it acts as a durable buffer between the web tier and fulfilment workers, decoupling the producers from consumers. When bursts of orders arrive, SQS queues the messages and allows the fulfilment service to poll and process them at its own pace, absorbing spikes without data loss. The queue provides at-least-once delivery and supports retries via a dead-letter queue, ensuring no requests are lost even if processing fails.
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.