The correct answer is to enable Amazon CloudWatch Logs for Kinesis Data Firehose to capture delivery errors and configure a Lambda function as a data transformation and error handler. This combination works because CloudWatch Logs provides real-time monitoring of failed S3 deliveries by recording the specific error codes and record details, while the Lambda function acts as a custom error handler that can intercept, log, and optionally reprocess or redirect failed records before they are permanently lost. On the AWS Certified Data Engineer Associate DEA-C01 exam, this question tests your understanding of Kinesis Data Firehose error handling for failed S3 deliveries, a common scenario where you must distinguish between Firehose’s native error logging and external processing via Lambda. A frequent trap is confusing Kinesis Data Streams or Data Analytics with Firehose’s error handling—remember that Firehose itself cannot reprocess failed records; it only logs them. Memory tip: “Log it with CloudWatch, fix it with Lambda” to recall the two complementary actions for failed record handling.
DEA-C01 Data Ingestion and Transformation Practice Question
This DEA-C01 practice question tests your understanding of data ingestion and transformation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 streaming IoT sensor data from thousands of devices into Amazon Kinesis Data Firehose. The data is then delivered to Amazon S3 for long-term storage. Occasionally, some records fail to be delivered to S3. The company must capture and analyze these failed records. Which TWO actions should be taken? (Choose two.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure an AWS Lambda function as a pre-processing step to catch and log failed records.
A is correct because enabling Kinesis Data Firehose error logging to CloudWatch allows monitoring of delivery failures. C is correct because configuring a Lambda function as a data transformation and error handler can process and log failed records. B is wrong because S3 is the destination, not the source for reprocessing. D is wrong because Kinesis Data Streams is a different service and does not directly capture Firehose failures. E is wrong because Kinesis Data Analytics is for real-time analytics, not for handling delivery failures.
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 an AWS Lambda function as a pre-processing step to catch and log failed records.
Why this is correct
Lambda can handle errors during transformation and log them.
Related concept
Static NAT maps one inside address to one outside address.
✗
Use Amazon Kinesis Data Analytics to analyze the failed records in real time.
Why it's wrong here
Kinesis Data Analytics is for streaming analytics, not error handling.
✗
Send failed records to an Amazon Kinesis Data Stream for reprocessing.
Why it's wrong here
Firehose does not automatically route failures to a stream.
✓
Enable Amazon CloudWatch Logs for Kinesis Data Firehose to capture delivery errors.
Why this is correct
CloudWatch Logs captures error logs from Firehose.
Related concept
Static NAT maps one inside address to one outside address.
✗
Set up an S3 event notification to trigger a Lambda function to reprocess failed records.
Why it's wrong here
Failed records are not in S3; they are not delivered.
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 DEA-C01 NAT questions on configuration and troubleshooting.
Data Ingestion and Transformation — This question tests Data Ingestion and Transformation — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Configure an AWS Lambda function as a pre-processing step to catch and log failed records. — A is correct because enabling Kinesis Data Firehose error logging to CloudWatch allows monitoring of delivery failures. C is correct because configuring a Lambda function as a data transformation and error handler can process and log failed records. B is wrong because S3 is the destination, not the source for reprocessing. D is wrong because Kinesis Data Streams is a different service and does not directly capture Firehose failures. E is wrong because Kinesis Data Analytics is for real-time analytics, not for handling delivery failures.
What should I do if I get this DEA-C01 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 DEA-C01 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 DEA-C01 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 DEA-C01 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.