The answer is to use AWS Lambda Destinations with a failure destination pointing to an SQS queue. This is correct because Lambda Destinations natively capture the full invocation record—including the input payload—for failed asynchronous invocations and route it to SQS, SNS, Lambda, or EventBridge without requiring any code changes to the function. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your ability to distinguish between Destinations and Dead Letter Queues (DLQs), a common trap: DLQs only work for functions invoked asynchronously by SNS or SQS, not directly by S3 events, whereas Destinations handle all asynchronous triggers. A key memory tip is “Destinations for direct triggers, DLQs for queued sources”—if the trigger is an S3 event, think Destinations first.
DOP-C02 Incident and Event Response Practice Question
This DOP-C02 practice question tests your understanding of incident and event response. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 uses AWS Lambda functions to process S3 events. After a recent deployment, some functions fail with timeout errors. The engineer needs to implement a solution that automatically captures and stores the function's input payload for all failed invocations without modifying the Lambda code. Which approach meets these requirements?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use AWS Lambda Destinations with a failure destination pointing to an SQS queue.
Option D is correct because Lambda Destinations allow sending invocation records (including input payload) to SQS, SNS, Lambda, or EventBridge for failed events, without code changes. Option A is wrong because DLQs only capture messages for Lambda functions invoked asynchronously by SNS or SQS, not directly by S3 events. Option B is wrong because CloudWatch Logs does not capture payload by default; it only logs if the function writes to logs. Option C is wrong because CloudWatch Events (EventBridge) can capture Lambda invocations but not the payload without custom code.
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.
✗
Enable CloudWatch Logs Insights on the Lambda function's log group.
Why it's wrong here
Logs do not capture input payload unless the function logs it.
✗
Use CloudWatch Events to capture Lambda invocation errors.
Why it's wrong here
CloudWatch Events does not capture the payload.
✗
Configure a dead-letter queue (DLQ) for the Lambda function.
Why it's wrong here
DLQs are for asynchronous invocations and capture messages, not payload from S3 events.
✓
Use AWS Lambda Destinations with a failure destination pointing to an SQS queue.
Why this is correct
Lambda Destinations send invocation records with payload for failed async invocations.
Related concept
Static NAT maps one inside address to one outside address.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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 DOP-C02 NAT questions on configuration and troubleshooting.
Incident and Event Response — This question tests Incident and Event Response — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use AWS Lambda Destinations with a failure destination pointing to an SQS queue. — Option D is correct because Lambda Destinations allow sending invocation records (including input payload) to SQS, SNS, Lambda, or EventBridge for failed events, without code changes. Option A is wrong because DLQs only capture messages for Lambda functions invoked asynchronously by SNS or SQS, not directly by S3 events. Option B is wrong because CloudWatch Logs does not capture payload by default; it only logs if the function writes to logs. Option C is wrong because CloudWatch Events (EventBridge) can capture Lambda invocations but not the payload without custom code.
What should I do if I get this DOP-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 DOP-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 DOP-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 DOP-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.