Tick-Bank's Web Traffic Analytics Solution

Implementation Guidelines

Prev Question Next Question

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.

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.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

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

Tick-Bank is looking to capture web-site traffic analytics to understand user navigational behavior, preferences, and other click-related information. Thousands of events are generated every second, and every event is sensitive and equally important, and Tick-Bank wants to treat every record as a separate stream.

To implement this solution, Tick-Bank can use Amazon Kinesis Data Streams to capture and process streaming data. Kinesis Data Streams is a fully managed service that enables real-time processing of streaming data at a massive scale.

When using Kinesis Data Streams, the following implementation guidelines can be followed:

  1. Each record in a separate Kinesis Data Streams record and make one HTTP request to send it to Kinesis Data Streams:

    • This means that every event generated will be treated as a separate record in the Kinesis Data Stream.
    • By making one HTTP request for each record, Tick-Bank ensures that every record is processed independently, and any issues or errors with one record do not affect the processing of other records.
    • This approach also provides better control over data processing and makes it easier to monitor and manage the data.

  2. Batching is not implemented as the target implementation:

    • Since Tick-Bank wants to treat every record as a separate stream, batching is not required.
    • Batching is used when multiple records are combined into a single unit to optimize data processing and reduce costs.
    • However, in this case, since every record is important and sensitive, batching may cause data loss or inconsistency.

Therefore, the recommended implementation approach for Tick-Bank is to send each record in a separate Kinesis Data Streams record and make one HTTP request to send it to Kinesis Data Streams. Batching is not implemented as the target implementation.

Tick-Bank can use the Kinesis Producer Library (KPL) to process the data and the Kinesis Client Library (KCL) to consume the records. KPL provides an efficient and reliable way to send data to Kinesis Data Streams, while KCL simplifies the process of consuming and processing the data from Kinesis Data Streams.

In summary, using Kinesis Data Streams, Tick-Bank can capture web-site traffic analytics and understand user navigational behavior, preferences, and other click-related information in real-time. By treating every record as a separate stream, Tick-Bank ensures that every event is processed independently and with the utmost importance.

Prev Question Next Question