HikeHills.com (HH) is an online specialty retailer that sells clothing and outdoor refreshment gear for trekking, go camping, boulevard biking, mountain biking, rock hiking, ice mountaineering, skiing, avalanche protection, snowboarding, fly fishing, kayaking, rafting, road and trace running, and many more.
HHruns their entire online infrastructure on java based web applications running on AWS. The HH is capturing click stream data and use custom-build recommendation engine to recommend products which eventually improve sales, understand customer preferences and already using AWS kinesis KPL to collect events and transaction logs and process the stream. The event/log size is around 12 KB.HHobserved couple of issues in the implementation and want to quickly fix the coding
Some of the events and transaction logs are missing and it’s adversely impacting the recommendation
Need for accountancy of failures
How can we solve the issues? select 3 options.

Answer options:

A.Write to a minimum of 2 streams to ensure replicas of event/log data is always available even if a record could not be inserted into a stream
B.Writes to the Kinesis data stream with an automatic and configurable retry mechanism
C.Maintain event/log information in temporary memory/storage of the application/session
D.Compare the stream records using GetRecords method with temporary memory/storage of the application/session
E.examine failures using the Future objects that are returned from addUserRecord method
F.Increase the time-to-live on records if records could not be inserted after RecordMaxBufferedTime

Answer : B, E, F
Option A is incorrect -Writing to more than 1 stream is needed if the requirement drives the demand for 2 or more different streams. There is no guarantee that the records would be written in case even into the second stream.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-writing.html
Option B is correct -Validate the transaction by checking the successful insert into the stream by embedding automatic and configurable retry mechanism
https://docs.aws.amazon.com/streams/latest/dev/developing-producers-with-kpl.html
Option C is incorrect -Kinesis Streams provide capabilities to use Future objects to validate UserRecords. No need to complicate the code by storing in memory/transient storage
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-writing.html
Option D is incorrect -Kinesis Streams provide capabilities to use Future objects to validate UserRecords. No need to complicate the code by storing in memory/transient storage
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-writing.html
Option E is correct -Kinesis Streams provide capabilities to use Future objects to validate UserRecords. No need to complicate the code by storing in memory/transient storage
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-writing.html
Option F is correct -time-to-live records need to be increases if the UserRecords could not inserted into stream in time.
https://github.com/awslabs/amazon-kinesis-producer/blob/master/java/amazon-kinesis-producer-sample/default_config.properties