easymultiple choiceObjective-mapped

A worker consumes messages from an Amazon SQS queue. Some messages consistently fail validation and are retried until the worker can no longer process them. What is the most appropriate AWS mechanism to handle these poison messages while keeping the queue usable?

Question 1easymultiple choice
Full question →

A worker consumes messages from an Amazon SQS queue. Some messages consistently fail validation and are retried until the worker can no longer process them. What is the most appropriate AWS mechanism to handle these poison messages while keeping the queue usable?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Enable SQS long polling and increase the maximum message size for the queue.

Long polling reduces empty receives, and message size changes allow larger payloads. Neither addresses messages that repeatedly fail processing, so poison messages could still repeatedly be delivered and waste consumer capacity.

B

Best answer

Send failing messages to an SQS dead-letter queue (DLQ) using a redrive policy based on receive count.

A DLQ with a redrive policy isolates poison messages. After a message is received and fails processing more than the configured maxReceiveCount, SQS moves it to the DLQ, preventing it from continually blocking retries in the source queue.

C

Distractor review

Change the queue to a FIFO queue and handle duplicates in the worker code without DLQs.

FIFO queues help with ordering and deduplication, but they do not automatically quarantine messages that repeatedly fail validation. Without a DLQ, poison messages would still be retried indefinitely (or until operational limits are reached).

D

Distractor review

Delete the queue and recreate it hourly to clear out any problematic messages.

Recreating queues is disruptive, can lead to loss of unprocessed messages, and is not a targeted mechanism. It also requires manual operational intervention instead of automatically isolating only the failing messages.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Send failing messages to an SQS dead-letter queue (DLQ) using a redrive policy based on receive count. — Use an SQS dead-letter queue (DLQ) with a redrive policy. Configure the source queue to send messages to a DLQ after they have been received and failed processing a specified number of times (maxReceiveCount). This keeps the main queue usable by stopping repeated delivery of poison messages and provides a separate place to inspect, alert on, and optionally replay after fixing the validation problem. Long polling and message-size adjustments do not stop repeated failures. Switching to FIFO without a DLQ does not quarantine messages that cannot be processed. Deleting/recreating the queue is an unsafe and non-granular approach that can disrupt consumers and does not isolate just the poison messages.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.