easymultiple choiceObjective-mapped

An internal worker consumes messages from an Amazon SQS queue. Occasionally, a message fails validation in the worker (for example, missing required fields). Reprocessing the same bad message repeatedly wastes processing time and delays healthy messages. What is the best AWS approach to handle these poison messages without blocking the rest of the queue?

Question 1easymultiple choice
Full question →

An internal worker consumes messages from an Amazon SQS queue. Occasionally, a message fails validation in the worker (for example, missing required fields). Reprocessing the same bad message repeatedly wastes processing time and delays healthy messages. What is the best AWS approach to handle these poison messages without blocking the rest of the queue?

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

Best answer

Configure an SQS dead-letter queue (DLQ) using a redrive policy with a maxReceiveCount.

With a redrive policy, SQS continues delivering the message to consumers until it has been received unsuccessfully maxReceiveCount times. After that threshold, SQS moves the poison message to a DLQ, isolating it from the main processing flow so healthy messages can continue being processed.

B

Distractor review

Delete the SQS queue and recreate it daily to clear invalid messages.

Recreating the queue is not a targeted remediation strategy. It can cause downtime, disrupt consumers, and provides no controlled way to isolate only the invalid payloads. It also risks losing visibility into the problematic messages.

C

Distractor review

Increase the consumer timeout/processing time so validation failures take longer to occur.

Timeout changes how long the worker runs, but it does not prevent SQS from redelivering the same invalid message when it is not successfully processed and deleted. The same poison message will still be retried and continue to consume worker capacity.

D

Distractor review

Use SNS fan-out without any DLQ and rely only on application retries.

SNS fan-out does not inherently solve poison-message handling. Without an explicit DLQ/redrive mechanism on the underlying delivery path, the system will continue retrying the same failing payload pattern, harming overall throughput.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Configure an SQS dead-letter queue (DLQ) using a redrive policy with a maxReceiveCount. — The most effective mechanism is an SQS dead-letter queue (DLQ) configured with a redrive policy (maxReceiveCount). This implements poison-message isolation: SQS retries delivery up to a controlled limit, then redirects the repeatedly failing message to the DLQ. Valid messages continue to flow normally, while invalid payloads can be inspected and remediated separately (for example, by replaying from the DLQ after a fix). Option B is disruptive and does not isolate specific failing messages. Option C delays the failure but does not stop repeated redelivery of the same invalid message. Option D lacks a DLQ/redrive pattern, so poison messages can keep causing repeated failures and retries, reducing processing throughput.

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.