A company wants to start using Kinesis streams for their ingestion of data. They want their development team to spend less effort when it comes to developing components that send data to the streams. Which of the following would be ideal for such a use case?

Answer options:

A.Use the KPL library
B.Use the Kinesis API
C.Use AWS Lambda
D.Use AWS SQS

Answer - A
The AWS Documentation mentions the following
The KPL is an easy-to-use, highly configurable library that helps you write to a Kinesis data stream. It acts as an intermediary between your producer application code and the Kinesis Data Streams API actions. The KPL performs the following primary tasks:
Writes to one or more Kinesis data streams with an automatic and configurable retry mechanism
Collects records and uses PutRecords to write multiple records to multiple shards per request
Aggregates user records to increase payload size and improve throughput
Integrates seamlessly with the Kinesis Client Library (KCL) to de-aggregate batched records on the consumer
Submits Amazon CloudWatch metrics on your behalf to provide visibility into producer performance
Option B is partially correct but the KPL library gives you a lot of benefits
Option C is incorrect since AWS Lambda is normally used at the consumer side
Option D is incorrect since this is a messaging service
For more information on the KPL library, please refer to the below URL
https://docs.aws.amazon.com/streams/latest/dev/developing-producers-with-kpl.html