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. The KCL application has been programmed to poll the Kinesis stream every 150 milliseconds. During a dry run, the KCL based application is getting a lot of “ProvisionedThroughputExceededException”errors. Which of the following could be underlying issue?

Answer options:

A.The Kinesis stream is created in the wrong region
B.The polling interval is too short
C.The polling interval is too long
D.You should use the Kinesis API for consuming records

Answer – B
The AWS Documentation mentions the following
Because Kinesis Data Streams has a limit of 5 GetRecords calls per second, per shard, setting the idleTimeBetweenReadsInMillisproperty lower than 200ms may result in your application observing the ProvisionedThroughputExceededException exception. Too many of these exceptions can result in exponential back-offs and thereby cause significant unexpected latencies in processing. If you set this property to be at or just above 200 ms and have more than one processing application, you will experience similar throttling.
Option A is incorrect because the dry run would not work at all if the Kinesis stream was created in the wrong region
Option C is incorrect because the polling interval is too short
Option D is incorrect since you should ideally use the KCL library in conjunction with the KPL library
For more information on Kinesis low latency, please refer to the below URL
https://docs.aws.amazon.com/streams/latest/dev/kinesis-low-latency.html