Which actions should the solutions architect take to resolve this issue?
(Choose three.)
Reshard the stream to increase the number of shards in the stream.
Use the Kinesis Producer Library (KPL). Adjust the polling frequency.
Use consumers with the enhanced fan-out feature.
Reshard the stream to reduce the number of shards in the stream.
Use an error retry and exponential backoff mechanism in the consumer logic.
Configure the stream to use dynamic partitioning.
Explanations:
Increasing the number of shards increases the read and write capacity, which helps to prevent throttling by providing additional throughput.
Kinesis Producer Library (KPL) optimizes data batching and aggregation for writes but does not directly address read-side throttling or ReadProvisionedThroughputExceeded errors.
Enhanced fan-out provides dedicated throughput for each consumer, which prevents consumers from being throttled due to shared read capacity limitations on the stream.
Reducing the number of shards decreases throughput capacity, worsening throttling issues rather than alleviating them.
Implementing error retry and exponential backoff in consumers can help mitigate throttling issues by retrying operations at controlled intervals rather than overwhelming the stream.
Dynamic partitioning is not a supported feature in Amazon Kinesis Data Streams and does not address the read throttling issue.
I categorize that the answer is:
Reshard the stream to increase the number of shards in the stream.
I weigh that the answer is:
Reshard the stream to increase the number of shards in the stream.