← SAA-C03·Amazon Web Services

Question 400 of 1,040

Design Resilient Architectures →mediumMultiple SelectObjective-mapped

Quick Answer

The answer is to insert an SQS queue between API Gateway and Lambda while making the database write idempotent using a unique request token or order ID. This combination works because SQS buffers incoming requests during traffic spikes, decoupling the ingestion rate from the database write rate and preventing throttling, while idempotency ensures that Lambda’s built-in retry logic—triggered by SQS visibility timeouts—does not create duplicate order records even when the same message is processed multiple times. On the SAA-C03 exam, this scenario tests your understanding of how to handle write-heavy serverless workloads under load, often appearing as a two-part answer where you must pair a buffering mechanism with a deduplication strategy. A common trap is choosing only a database scaling solution like RDS read replicas, which do not help with write throttling or duplicate prevention. Memory tip: think “SQS soaks the spike, idempotency kills the duplicate.”

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. 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.

A serverless order-ingestion API writes directly to a database. During traffic spikes, the database occasionally throttles, Lambda retries create duplicate order records, and some requests time out. Which two changes best improve buffering and safe retry behavior? Select two.

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.

Question 1mediummulti select

Full question →

A
Increase the Lambda timeout and keep writing directly to the database.
Why wrong: A longer timeout may hide transient failures, but it does not add buffering or prevent duplicate writes.
B
Put an Amazon SQS queue between the API and the database-processing function.
SQS buffers bursts and decouples producers from consumers, so the database can be processed at a steadier rate.
C
Replace SQS with SNS so every request is delivered immediately to all subscribers.
Why wrong: SNS fanout is useful for notifications, but it does not provide durable work queue buffering for a throttled consumer.
D
Make the database write idempotent by using a unique request token or order ID.
Idempotency ensures repeated deliveries or retries do not create duplicate orders when the same request is processed again.
E
Disable retries so failed writes are never duplicated.
Why wrong: Disabling retries reduces duplicates, but it also turns transient failures into permanent lost orders.

Full breakdown with real-world context →

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

✓

Put an Amazon SQS queue between the API and the database-processing function.

Option B is correct because inserting an SQS queue between the API Gateway and the Lambda function decouples the ingestion from the database write. During traffic spikes, SQS buffers the requests, allowing the Lambda function to poll at a controlled rate, which prevents database throttling. Additionally, SQS provides built-in retry logic with a visibility timeout, so failed messages are automatically retried without creating duplicate order records.

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.

✗
Increase the Lambda timeout and keep writing directly to the database.
Why it's wrong here
A longer timeout may hide transient failures, but it does not add buffering or prevent duplicate writes.
✓
Put an Amazon SQS queue between the API and the database-processing function.
Why this is correct
SQS buffers bursts and decouples producers from consumers, so the database can be processed at a steadier rate.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Replace SQS with SNS so every request is delivered immediately to all subscribers.
Why it's wrong here
SNS fanout is useful for notifications, but it does not provide durable work queue buffering for a throttled consumer.
✓
Make the database write idempotent by using a unique request token or order ID.
Why this is correct
Idempotency ensures repeated deliveries or retries do not create duplicate orders when the same request is processed again.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Disable retries so failed writes are never duplicated.
Why it's wrong here
Disabling retries reduces duplicates, but it also turns transient failures into permanent lost orders.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often think SNS (Option C) is a suitable replacement for SQS because both are messaging services, but SNS lacks buffering and retry mechanics, making it inappropriate for smoothing traffic spikes and handling failures gracefully.

Detailed technical explanation

How to think about this question

SQS uses a visibility timeout to hide a message after it is polled; if the Lambda function fails to process the message within that timeout, the message becomes visible again for another consumer, enabling automatic retries. To prevent duplicates from these retries, option D (idempotent writes) is essential—using a unique request token (e.g., order ID) as a primary key or conditional write ensures that retries simply overwrite or are ignored, rather than creating duplicate records. In a real-world scenario, combining SQS with idempotent writes is a common pattern for building resilient, exactly-once processing pipelines.

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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

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.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

SAA-C03 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Design Resilient Architectures — This question tests Design Resilient Architectures — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Put an Amazon SQS queue between the API and the database-processing function. — Option B is correct because inserting an SQS queue between the API Gateway and the Lambda function decouples the ingestion from the database write. During traffic spikes, SQS buffers the requests, allowing the Lambda function to poll at a controlled rate, which prevents database throttling. Additionally, SQS provides built-in retry logic with a visibility timeout, so failed messages are automatically retried without creating duplicate order records.

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". 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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on SAA-C03

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 serverless order-ingestion API writes directly to a database. During traffic spikes, the database occasionally throttles, Lambda retries create duplicate order records, and some requests time out. Which two changes best improve buffering and safe retry behavior? Select two.

medium

A.Increase the Lambda timeout and keep writing directly to the database.
✓ B.Put an Amazon SQS queue between the API and the database-processing function.
C.Replace SQS with SNS so every request is delivered immediately to all subscribers.
✓ D.Make the database write idempotent by using a unique request token or order ID.
E.Disable retries so failed writes are never duplicated.

Why B: Option B is correct because inserting an SQS queue between the API Gateway and the Lambda function decouples the ingestion from the database write. During traffic spikes, SQS acts as a buffer, absorbing bursts and allowing the Lambda function to poll messages at a controlled rate, which prevents database throttling. Combined with a dead-letter queue, failed messages can be retried safely without overwhelming the database or creating duplicate records.

Keep practising

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.

Loading comments…

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.