Your development team has created separate applications which implement the KPL and KCL library for writing and reading data from Kinesis streams. The KPL is being used to stream information from thousands of IoT devices. The KCL application is consuming the records and providing real time analytics to the data science team. After a dry run, the KCL based application is getting provisioned throughput errors. Which of the following could should be carried out to resolve this issue?

Answer options:

A.Ensure the number of shards is increased
B.Increase the number of streams
C.Increase the throughput for DynamoDB tables
D.Ensure the application has the right IAM Role attached

Answer – C
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.
Options A and B are incorrect because the issue is related to a data consuming issue
Option D is incorrect because this is not a security related issue
For more information on KCL and DynamoDB, please refer to the below URL
https://docs.aws.amazon.com/streams/latest/dev/kinesis-record-processor-ddb.html
Note:
For each Amazon Kinesis Data Streams application, the KCL uses a unique Amazon DynamoDB table to keep track of the application`s state.
For more detailed info, please read through below link:
https://docs.aws.amazon.com/streams/latest/dev/kinesis-record-processor-ddb.html