Tick-Bank is a privately held Internet retailer of both physical and digital products founded in 2008. The company has more than six-million clients worldwide. Tick-Bank aims to serve as a connection between digital content makers and affiliate dealers, who then promote them to clients. Tick-Bank`s technology aids in payments, tax calculations and a variety of customer service tasks. Tick-Bank assists in building perceptibility and revenue making opportunities for entrepreneurs.
Tick-Bank runs multiple java based web applications running on windows based EC2 machines in AWS managed by internal IT Java team, to serve various business functions. Tick-Bank is looking to enable web-site traffic analytics there by understanding user navigational behavior, preferences and other click related info. The amount of data captured per click is in tens of bytes. Tick-Bank has the following objectives in mind for the solution.
Tick-Bank uses KPL to process the data and KCL library to consume the records. Thousands of events are being generated every second and every event is sensitive and equally important and Gluebush.com wants to treat every record as a separate stream. please detail the implementation guidelines. select 2 options.

Answer options:

A.each record in a separate Kinesis Data Streams record and make one HTTP request to send it to Kinesis Data Streams
B.each HTTP request carries multiple Kinesis Stream records which is sent to kinesis Data streams
C.Batching is implemented as the target implementation
D.Batching is not implemented as the target implementation

Answer: A,D
Option A is correct -When batching is not implemented, each record is treated as a separate data stream record. In this context batching is not implemented. 
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.html
Option B is incorrect - When batching is not implemented, each record is treated as a separate data stream record. In this context batching is not implemented. 
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.html
Option C is incorrect -Batching refers to performing a single action on multiple items instead of repeatedly performing the action on each individual item. In this context, the "item" is a record, and the action is sending it to Kinesis Data Streams. In a non-batchingsituation, you would place each record in a separate Kinesis Data Streams record and make one HTTP request to send it to Kinesis Data Streams. With batching, each HTTP request can carry multiple records instead of just one. 
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.html
Option D is correct -Batching refers to performing a single action on multiple items instead of repeatedly performing the action on each individual item. In this context, the "item" is a record, and the action is sending it to Kinesis Data Streams. In a non-batchingsituation, you would place each record in a separate Kinesis Data Streams record and make one HTTP request to send it to Kinesis Data Streams. With batching, each HTTP request can carry multiple records instead of just one. 
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.html