The correct answer is to configure an on-failure destination on the Kinesis event source mapping to send records to an SQS queue. This works because Kinesis Data Streams uses synchronous polling-based invocations for Lambda, not asynchronous invocations, so the dead-letter queue must be defined directly on the event source mapping rather than on the function itself. When processing fails after the default retries (which can be up to 24 hours for stream-based invocations), the record is sent to the configured SQS queue, allowing you to set a maximum retry count of three via the event source mapping’s bisect-on-error and retry-attempts settings. On the SAP-C02 exam, this distinction between Lambda destinations (for async invocations) and event source mapping on-failure destinations (for stream-based sources) is a frequent trap—many candidates mistakenly apply async DLQ concepts to Kinesis. Remember the mnemonic: “Streams map the DLQ; Async invokes the DLQ.”
SAP-C02 Design for New Solutions Practice Question
This SAP-C02 practice question tests your understanding of design for new solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 company is designing a new serverless data processing pipeline. The pipeline uses AWS Lambda to process records from an Amazon Kinesis Data Stream. The company wants to ensure that failed records are automatically retried and sent to a dead-letter queue after three failed attempts. Which configuration should the company use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure an on-failure destination on the Kinesis event source mapping to send records to an SQS queue.
Option B is correct because Kinesis Data Streams as a Lambda event source supports on-failure destinations for DLQ. Option A is wrong because Lambda destinations are for async invocations, not streams. Option C is wrong because DLQ is not a property of Lambda function configuration. Option D is wrong because SQS standard queue does not support retry settings like Lambda.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Configure the Kinesis stream to send failed records to an SQS standard queue.
Why it's wrong here
Kinesis does not directly send failed records to SQS; the Lambda event source mapping handles retries.
✓
Configure an on-failure destination on the Kinesis event source mapping to send records to an SQS queue.
Why this is correct
The event source mapping for Kinesis supports an on-failure destination for DLQ.
Related concept
Static NAT maps one inside address to one outside address.
✗
Configure the Lambda function's dead-letter queue property with an SQS queue.
Why it's wrong here
The DLQ property is for async invocations, not for stream-based event sources.
✗
Configure a Lambda destination on the function to send events to an SQS queue.
Why it's wrong here
Lambda destinations are for async invocation results, not for Kinesis event source mapping.
Common exam traps
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.
Detailed technical explanation
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.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. 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.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SAP-C02 NAT questions on configuration and troubleshooting.
Design for New Solutions — This question tests Design for New Solutions — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Configure an on-failure destination on the Kinesis event source mapping to send records to an SQS queue. — Option B is correct because Kinesis Data Streams as a Lambda event source supports on-failure destinations for DLQ. Option A is wrong because Lambda destinations are for async invocations, not streams. Option C is wrong because DLQ is not a property of Lambda function configuration. Option D is wrong because SQS standard queue does not support retry settings like Lambda.
What should I do if I get this SAP-C02 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SAP-C02 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
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 SAP-C02 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 SAP-C02 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.