- A
Increase the Lambda function timeout to 60 seconds and memory to 1024 MB. Set the batch size to 100 records and enable parallelization factor of 10.
This combination increases processing capacity and prevents timeouts.
- B
Increase the number of shards in the Kinesis data stream to 20 and keep the Lambda configuration unchanged.
Why wrong: More shards increase parallelism but Lambda may still timeout with current settings.
- C
Replace the Lambda function with a Kinesis Data Firehose delivery stream that writes directly to DynamoDB using a Lambda transformation.
Why wrong: Firehose does not support DynamoDB as a direct destination; it uses Lambda for transformation, which still has the same issue.
- D
Increase the Lambda function timeout to 60 seconds and memory to 1024 MB. Set the batch size to 100 records.
Why wrong: This alone does not increase concurrency; may still fall behind.
Quick Answer
The correct answer is to increase the Lambda timeout to 60 seconds and memory to 1024 MB, set the batch size to 100 records, and enable a parallelization factor of 10. This works because the parallelization factor allows each Kinesis shard to process up to 10 concurrent batches, so with a batch size of 100, a single shard can handle 1,000 records per second—matching the stream’s ingestion rate—while the increased timeout and memory prevent processing failures. On the AWS Certified Data Engineer Associate DEA-C01 exam, this scenario tests your understanding of Lambda-Kinesis integration tuning, specifically how batch size and parallelization factor interact to scale throughput without exceeding concurrency limits. A common trap is thinking only memory or timeout needs adjustment, but the real bottleneck is often the sequential per-shard processing. Remember the mnemonic “10x100 = 1000” to recall that a parallelization factor of 10 with a batch size of 100 yields 1,000 records per second per shard.
DEA-C01 Data Ingestion and Transformation Practice Question
This DEA-C01 practice question tests your understanding of data ingestion and transformation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 financial services company ingests real-time stock trade data from multiple exchanges into Amazon Kinesis Data Streams. Each trade record is a JSON object containing fields: trade_id, symbol, price, quantity, and timestamp. The data is consumed by an AWS Lambda function that performs data validation and enrichment, then writes the processed records to an Amazon DynamoDB table for low-latency querying. Recently, the Lambda function has been timing out and failing to process all records. The Lambda function is configured with a 5-second timeout and 128 MB memory. The average record size is 2 KB, and the stream receives about 1000 records per second. The Lambda function's concurrency limit is 1000. Which set of actions should the data engineer take to resolve the issue without losing data?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Increase the Lambda function timeout to 60 seconds and memory to 1024 MB. Set the batch size to 100 records and enable parallelization factor of 10.
Option A is correct because increasing the Lambda timeout and memory addresses the processing bottleneck, while setting the batch size to 100 and enabling a parallelization factor of 10 allows each shard to process up to 10 concurrent batches, dramatically increasing throughput to handle 1000 records/sec (each shard can process 10 batches of 100 records concurrently, yielding 1000 records/sec per shard if the stream has at least 1 shard). This combination ensures no data loss by keeping up with the ingestion rate without exceeding the Lambda concurrency limit of 1000.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Increase the Lambda function timeout to 60 seconds and memory to 1024 MB. Set the batch size to 100 records and enable parallelization factor of 10.
Why this is correct
This combination increases processing capacity and prevents timeouts.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Increase the number of shards in the Kinesis data stream to 20 and keep the Lambda configuration unchanged.
Why it's wrong here
More shards increase parallelism but Lambda may still timeout with current settings.
- ✗
Replace the Lambda function with a Kinesis Data Firehose delivery stream that writes directly to DynamoDB using a Lambda transformation.
Why it's wrong here
Firehose does not support DynamoDB as a direct destination; it uses Lambda for transformation, which still has the same issue.
- ✗
Increase the Lambda function timeout to 60 seconds and memory to 1024 MB. Set the batch size to 100 records.
Why it's wrong here
This alone does not increase concurrency; may still fall behind.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often overlook the parallelization factor setting, assuming that increasing batch size and Lambda resources alone will suffice, but without parallelization, each shard can only process one batch at a time, creating a throughput bottleneck that leads to data loss.
Detailed technical explanation
How to think about this question
The parallelization factor in Lambda-Kinesis integration allows a single shard to process up to 10 concurrent batches, each with its own Lambda invocation, effectively multiplying throughput per shard. Under the hood, Lambda uses the Kinesis Client Library (KCL) to manage shard iterators and checkpointing; enabling parallelization factor creates multiple iterators per shard, each tracking its own sequence number, ensuring exactly-once processing semantics. In real-world scenarios, this is critical for high-throughput streams where a single Lambda invocation per shard would be throttled by the 6-minute Lambda timeout or memory limits.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Data Ingestion and Transformation — study guide chapter
Learn the concepts, then practise the questions
- →
Data Ingestion and Transformation practice questions
Targeted practice on this topic area only
- →
All DEA-C01 questions
1,786 questions across all exam domains
- →
AWS Certified Data Engineer Associate DEA-C01 study guide
Full concept coverage aligned to exam objectives
- →
DEA-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DEA-C01 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Data Ingestion and Transformation practice questions
Practise DEA-C01 questions linked to Data Ingestion and Transformation.
Data Operations and Support practice questions
Practise DEA-C01 questions linked to Data Operations and Support.
Data Security and Governance practice questions
Practise DEA-C01 questions linked to Data Security and Governance.
Data Store Management practice questions
Practise DEA-C01 questions linked to Data Store Management.
DEA-C01 fundamentals practice questions
Practise DEA-C01 questions linked to DEA-C01 fundamentals.
DEA-C01 scenario practice questions
Practise DEA-C01 questions linked to DEA-C01 scenario.
DEA-C01 troubleshooting practice questions
Practise DEA-C01 questions linked to DEA-C01 troubleshooting.
Practice this exam
Start a free DEA-C01 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DEA-C01 question test?
Data Ingestion and Transformation — This question tests Data Ingestion and Transformation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Increase the Lambda function timeout to 60 seconds and memory to 1024 MB. Set the batch size to 100 records and enable parallelization factor of 10. — Option A is correct because increasing the Lambda timeout and memory addresses the processing bottleneck, while setting the batch size to 100 and enabling a parallelization factor of 10 allows each shard to process up to 10 concurrent batches, dramatically increasing throughput to handle 1000 records/sec (each shard can process 10 batches of 100 records concurrently, yielding 1000 records/sec per shard if the stream has at least 1 shard). This combination ensures no data loss by keeping up with the ingestion rate without exceeding the Lambda concurrency limit of 1000.
What should I do if I get this DEA-C01 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Keep practising
More DEA-C01 practice questions
- A data pipeline uses Kinesis Data Firehose to deliver streaming data to an S3 bucket. The data volume spikes occasionall…
- An e-commerce company uses AWS Glue to run ETL jobs that transform clickstream data from Amazon S3. The job reads Parque…
- A data engineering team uses Amazon Kinesis Data Analytics for Apache Flink to process streaming data. They notice that…
- A company uses AWS Glue to process streaming data from Amazon Kinesis Data Streams. The job reads JSON records and write…
- A data engineer is designing a serverless data ingestion pipeline that uses Amazon Kinesis Data Firehose to deliver data…
- A company runs a nightly AWS Glue ETL job that reads from a JDBC source (PostgreSQL) and writes to S3 in Parquet format.…
Last reviewed: Jun 11, 2026
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.