mediummultiple choiceObjective-mapped

An internal worker consumes messages from an Amazon SQS Standard queue. Recently, some messages fail validation in the worker (for example, missing required fields), causing the worker to crash before it can successfully process those messages. Those messages keep getting retried repeatedly, slowing down processing of valid messages. The team wants a resilient mechanism to quarantine bad messages after a limited number of receive attempts. What should they implement?

Question 1mediummultiple choice
Full question →

An internal worker consumes messages from an Amazon SQS Standard queue. Recently, some messages fail validation in the worker (for example, missing required fields), causing the worker to crash before it can successfully process those messages. Those messages keep getting retried repeatedly, slowing down processing of valid messages. The team wants a resilient mechanism to quarantine bad messages after a limited number of receive attempts. What should they implement?

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

Increase the SQS visibility timeout to several hours so the worker does not retry too quickly.

A longer visibility timeout only delays retries. Poison messages can still reappear after the timeout and continue consuming processing capacity over time; it does not quarantine messages after a defined number of failures.

B

Best answer

Configure a redrive policy with a Dead-Letter Queue (DLQ) and set maxReceiveCount so poison messages are moved to the DLQ after repeated failures.

An SQS DLQ with a redrive policy is specifically designed for poison-message handling. When a message exceeds maxReceiveCount without successful processing (for example, the worker crashes before deletion), SQS moves the message to the DLQ. This quarantines bad messages and protects throughput for valid messages.

C

Distractor review

Switch the queue to an SNS topic and subscribe the worker directly, eliminating message retries.

SNS-to-SQS delivery still needs application-level failure handling, and SNS does not provide the same poison-message quarantine mechanism as SQS DLQs with maxReceiveCount. The underlying issue (failed processing and retry/redelivery) would still need a strategy to isolate bad messages.

D

Distractor review

Enable KMS encryption with a new CMK to ensure validation errors stop occurring.

KMS encryption affects data at rest and access control. It does not change message contents or the worker’s validation logic, so it cannot stop validation failures or worker crash/retry loops.

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 a redrive policy with a Dead-Letter Queue (DLQ) and set maxReceiveCount so poison messages are moved to the DLQ after repeated failures. — For SQS Standard queues, message delivery is at-least-once. If processing fails (for example, the worker crashes before DeleteMessage), the message becomes visible again after the visibility timeout and can be retried indefinitely. A DLQ with a redrive policy and maxReceiveCount provides a resilience mechanism to quarantine poison messages: once the message has been received more than the threshold without successful processing, SQS moves it to the DLQ. Valid messages continue to be processed normally, and the team can inspect and remediate quarantined messages separately. Visibility timeout changes the retry timing but does not prevent repeated deliveries. Switching to SNS does not remove the need for poison-message handling and does not provide the maxReceiveCount-based quarantine behavior of SQS DLQs. KMS encryption does not address message validity or processing semantics that cause repeated retries.

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.