You have many Lambda functions that read data from the AWS Kinesis stream. Your colleague informs you that our application has too many Lambda function invocations, increasing latency for your application. How can you minimize latency and increase the read throughput of your function efficiently?

Answer options:

A.Create a data stream consumer.
B.Reduce the number of functions and let each function do the work of 2 functions.
C.Configure CloudWatch logs to check the latency and rebuild the Lambda functions.
D.Configure a dead letter queue.

Answer: A
Option A is CORRECT as creating a data stream consumer assures a dedicated connection to each shard. The connection will help maximize throughput and minimize latency. By default, Amazon states that the Lambda function polls each shard at a base rate of 1 per second.
Option B is incorrect as this option will increase the function execution time that will require longer timeouts and maybe more memory. This will not be an efficient solution.
Option C is incorrect because the question mentions that there are many Lambda functions. So it is not feasible to rebuild the Lambda functions.
Option D is incorrect as a dead letter queue will help when your Lambda functions are overwhelmed and are missing processing of the data coming from the stream which is not the case in this scenario.
Reference:
https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html