Web Traffic Analytics Implementation Specifications
Question
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.
Tick-Bank has multiple data streams supporting various business processes.
Since the amount of data generated by stream is very small, planning to use API operation PutRecords to send multiple Kinesis Data Streams records to one or more shards in your Kinesis data stream.
Please detail the specifications of implementation. Select 3 options.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.Answer: A,C,D.
Option A is correct -Batching refers to performing a single action on multiple items instead of repeatedly performing the action on each individual item.
Batching of records is part of implementation.
The KPL supports two types of batching:
Aggregation - Storing multiple records within a single Kinesis Data Streams record.
Collection - Using the API operation PutRecords to send multiple Kinesis Data Streams records to one or more shards in your Kinesis data stream.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.htmlOption B is incorrect -Batching refers to performing a single action on multiple items instead of repeatedly performing the action on each individual item.
Batching of records is part of implementation.
The KPL supports two types of batching:
Aggregation - Storing multiple records within a single Kinesis Data Streams record.
Collection - Using the API operation PutRecords to send multiple Kinesis Data Streams records to one or more shards in your Kinesis data stream.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.htmlOption C is correct -Aggregation refers to the storage of multiple records in a Kinesis Data Streams record.
Aggregation allows customers to increase the number of records sent per API call, which effectively increases producer throughput.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.htmlOption D is corerct -Collection refers to batching multiple Kinesis Data Streams records and sending them in a single HTTP request with a call to the API operation PutRecords, instead of sending each Kinesis Data Streams record in its own HTTP request.
This increases throughput compared to using no collection because it reduces the overhead of making many separate HTTP requests.
In fact, PutRecords itself was specifically designed for this purpose.
Collection differs from aggregation in that it is working with groups of Kinesis Data Streams records.
The Kinesis Data Streams records being collected can still contain multiple records from the user.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.htmlOption E is incorrect -Aggregation and Collection can coexist and can be turned on or off independently of one another.
By default, both are turned on.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-concepts.htmlTick-Bank is looking to enable web-site traffic analytics by understanding user navigational behavior, preferences, and other click-related information. They plan to use Amazon Kinesis Data Streams to capture this data. The data captured per click is in tens of bytes, and they have multiple data streams supporting various business processes.
To implement this solution, Tick-Bank uses the Kinesis Producer Library (KPL) to process the data and the Kinesis Client Library (KCL) to consume the records. They plan to use the API operation PutRecords to send multiple Kinesis Data Streams records to one or more shards in their Kinesis data stream.
The following are the specifications of the implementation:
Batching of records is part of the implementation: This means that Tick-Bank will group multiple records together before sending them to the Kinesis Data Streams. This approach helps to reduce the number of API calls needed to send data and improves performance.
Perform aggregation by storing multiple records within a single Kinesis Data Streams record: In this approach, Tick-Bank will combine multiple records into a single Kinesis Data Streams record before sending it to the data stream. This approach helps to reduce the number of records in the stream and can also help to reduce costs.
Perform collection by sending multiple Kinesis Data Streams records to one or more shards in your Kinesis data stream: This approach involves sending multiple records to one or more shards in the Kinesis data stream. This approach helps to distribute the load across multiple shards and can also help to improve the performance of the solution.
Based on the objectives of Tick-Bank for this solution, options A, C, and D are the correct answers. Option B is incorrect because batching of records is indeed part of the implementation. Option E is also incorrect because aggregation and collection can coexist, and they can be turned on or off independently of one another.
