Question 1,551 of 1,755
Data EngineeringhardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to increase the number of shards in the Kinesis Data Stream to 20, as this directly boosts the parallelism of Lambda consumers. The core issue is that the existing shard count of 5 limits the maximum concurrent Lambda invocations to five, causing the shard iterator age to rise when throughput exceeds that capacity. By scaling shards to 20, you increase the stream’s ingestion units and allow Lambda to process more records in parallel, resolving the throttling without adding unnecessary cost or complexity. On the AWS Certified Machine Learning Specialty MLS-C01 exam, this scenario tests your understanding of Kinesis shard scaling for Lambda throughput, a common pitfall where candidates mistakenly tweak Lambda concurrency or batch windows instead of addressing the shard-level bottleneck. Remember the key relationship: one shard equals one Lambda consumer, so to scale processing, scale shards first. A useful memory tip is “shards sync with speed”—more shards mean more concurrent consumers and faster data flow.

MLS-C01 Data Engineering Practice Question

This MLS-C01 practice question tests your understanding of data engineering. 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 retail company runs an e-commerce platform on AWS. They have a Data Engineering team that processes clickstream data using Amazon Kinesis Data Streams (KDS) with a shard count of 5. The data is consumed by an AWS Lambda function that transforms and loads the data into an Amazon S3 bucket partitioned by year/month/day/hour. Recently, the team has noticed that the Lambda function is experiencing throttling errors, and the KDS shard iterator age is increasing, indicating that the consumer cannot keep up with the incoming data rate. The team has already increased the Lambda reserved concurrency to 1000 and enabled batch window of 60 seconds. The metrics show that the Lambda function duration is well under the 5-minute timeout, and there are no errors in the transformation logic. The S3 write operations are not failing. Which course of action would MOST effectively resolve the issue without unnecessary cost or complexity?

Question 1hardmultiple choice
Full question →

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 number of shards in the Kinesis Data Stream to 20 to increase the parallelism of Lambda consumers.

The core issue is that the Lambda consumer cannot keep up with the incoming data rate, as evidenced by the increasing shard iterator age. Increasing the shard count from 5 to 20 directly increases the number of Kinesis Data Streams shards, which in turn increases the number of concurrent Lambda invocations (one per shard) and the overall throughput of the stream. This addresses the bottleneck at the source without adding unnecessary complexity or cost, as KDS pricing is based on shard hours and Lambda concurrency is already set to 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 number of shards in the Kinesis Data Stream to 20 to increase the parallelism of Lambda consumers.

    Why this is correct

    More shards allow more concurrent Lambda invocations, improving throughput and reducing iterator age.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Increase the Lambda reserved concurrency to 5000 to allow more parallel executions.

    Why it's wrong here

    Higher concurrency may not help if the shard count is the bottleneck; each shard limits the number of concurrent Lambda invocations.

  • Increase the batch window to 300 seconds to accumulate more records per invocation and reduce the number of calls.

    Why it's wrong here

    Longer batch window increases latency and may not reduce backlog if the data arrival rate is high.

  • Switch to using Amazon Kinesis Data Analytics with a larger instance type to process the stream.

    Why it's wrong here

    Kinesis Data Analytics is a different service and would require rearchitecting; it is more complex and costly.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume increasing Lambda concurrency or batch window will solve throughput issues, but they fail to recognize that Kinesis shard count is the fundamental limiter of parallelism in the Lambda-Kinesis integration.

Detailed technical explanation

How to think about this question

Kinesis Data Streams uses shards as the unit of throughput, with each shard supporting up to 1 MB/s write and 2 MB/s read. Lambda integrates with KDS via event source mappings, which poll each shard independently and invoke one Lambda function per shard. The shard iterator age metric indicates how far behind the consumer is from the tip of the stream; if it increases, the consumer is not reading fast enough. Increasing shards increases the number of parallel Lambda invocations, directly improving read throughput.

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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

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.

Related practice questions

Related MLS-C01 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free MLS-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 MLS-C01 question test?

Data Engineering — This question tests Data Engineering — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Increase the number of shards in the Kinesis Data Stream to 20 to increase the parallelism of Lambda consumers. — The core issue is that the Lambda consumer cannot keep up with the incoming data rate, as evidenced by the increasing shard iterator age. Increasing the shard count from 5 to 20 directly increases the number of Kinesis Data Streams shards, which in turn increases the number of concurrent Lambda invocations (one per shard) and the overall throughput of the stream. This addresses the bottleneck at the source without adding unnecessary complexity or cost, as KDS pricing is based on shard hours and Lambda concurrency is already set to 1000.

What should I do if I get this MLS-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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.