MLS-C01 Data Engineering Practice Question
A company is streaming clickstream data from a website to Amazon Kinesis Data Streams. The data is consumed by a Lambda function that enriches each record with geolocation information before writing to an S3 bucket. Recently, the Lambda function has been failing with throttling errors. What is the MOST likely cause?
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
✓
The Lambda function's concurrent execution limit has been reached
The most likely cause is that the Lambda function's concurrent execution limit has been reached. Kinesis Data Streams invokes Lambda functions per shard, and with high throughput or many shards, concurrent invocations can exceed the default Lambda concurrency limit (1000 per region). This results in throttling errors. Option A is incorrect because the Lambda payload limit for asynchronous invocation (used by Kinesis) is 256 KB, not 6 MB. Option C is incorrect; setting reserved concurrency too high would not cause throttling—it could actually help avoid throttling. Option D is incorrect because the default shard limit is 500, but shard limits are a Kinesis concern, not directly causing Lambda throttling.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The Lambda function's payload size exceeds the 6 MB limit
Why it's wrong here
Kinesis records are limited to 1 MB, so payload size is not the issue.
- ✓
The Lambda function's concurrent execution limit has been reached
Why this is correct
Lambda throttles when the number of concurrent executions exceeds the account limit.
- ✗
The Lambda function's reserved concurrency is set too high
Why it's wrong here
High reserved concurrency would help, not cause throttling.
- ✗
The Kinesis stream has exceeded the default shard limit of 500
Why it's wrong here
Shard limit is a Kinesis limit, not Lambda. Throttling errors occur in Lambda.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
Courseiva writes every MLS-C01 question from scratch — 1,672 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MLS-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 MLS-C01 exam.