A company is making use of Kinesis streams to process millions of records. Enough shards have been assigned to the stream. The KPL library is being used in an application to submit the requests. A Lambda function is being used to process the requests. During the initial stages of execution, there is a latency of around 150 to 200 Milliseconds being recorded in Cloudwatch for the consumption of records. The AWS Lambda function is showing no throttling errors and the memory and time is being consumed as per standard specifications. Which of the following could be the underlying problem?

Answer options:

A.An incorrect IAM Role has been assigned to the Lambda function
B.The throughput for the DynamoDB table is being exceeded.
C.The right packages have not been installed for the Lambda function
D.The wrong programming language has been chosen for the Lambda function

Answer – B
The AWS Documentation mentions the following
If your Amazon Kinesis Data Streams application receives provisioned-throughput exceptions, you should increase the provisioned throughput for the DynamoDB table. The KCL creates the table with a provisioned throughput of 10 reads per second and 10 writes per second, but this might not be sufficient for your application. For example, if your Amazon Kinesis Data Streams application does frequent checkpointing or operates on a stream that is composed of many shards, you might need more throughput.
All other options are incorrect since if this were the cases, then the Lambda function would never run at all.
For more information on reading records from Kinesis, please visit the url
https://docs.aws.amazon.com/streams/latest/dev/kinesis-record-processor-ddb.html