Tick-Bank Web Analytics: Understanding User Navigational Behavior and Preferences

Web Analytics for Tick-Bank: User Behavior and Preferences

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.

Tick-Bank is also looking at improving operations ingesting monitoring logs.

Kinesis agent is used to process the logs and kinesis firehose the process the stream and data is stored into multiple data destinations like S3, ES and Splunk.

What is the data delivery frequency? select 3 options.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

Answer: A,D, F.

The frequency of data delivery to Amazon S3 is determined by the Amazon S3 Buffer size and Buffer interval value that you configured for your delivery stream.

Kinesis Data Firehose buffers incoming data before it delivers it to Amazon S3

You can configure the values for Amazon S3 Buffer size (1-128 MB) or Buffer interval (60-900 seconds)

Kinesis Data Firehose buffers incoming data before delivering it to Amazon ES.

You can configure the values for Elasticsearch Buffer size (1-100 MB) or Buffer interval (60-900seconds)

Kinesis Data Firehose buffers incoming data before delivering it to Splunk.

The buffer size is 5 MB, and the buffer interval is 60 seconds.

https://docs.aws.amazon.com/firehose/latest/dev/basic-deliver.html#frequency

Tick-Bank is using Kinesis Firehose to process logs and store data into multiple data destinations such as S3, ES, and Splunk. To determine the data delivery frequency, we need to consider the buffer size and buffer interval configured for the delivery streams.

Option A states that the delivery streams to S3 with buffer size between 1-128 MB and buffer interval between 60-900 seconds. This means that data is delivered to S3 at a frequency of 1-128 MB every 60-900 seconds.

Option B states that the delivery streams to S3 with buffer size between 1-100 MB and buffer interval between 60-900 seconds. This means that data is delivered to S3 at a frequency of 1-100 MB every 60-900 seconds.

Option C states that the delivery streams to ES with buffer size between 1-128 MB and buffer interval between 60-900 seconds. This means that data is delivered to ES at a frequency of 1-128 MB every 60-900 seconds.

Option D states that the delivery streams to ES with buffer size between 1-100 MB and buffer interval between 60-900 seconds. This means that data is delivered to ES at a frequency of 1-100 MB every 60-900 seconds.

Option E states that the delivery streams to Splunk with minimum buffer size 1MB and buffer interval 900 seconds. This means that data is delivered to Splunk at a frequency of 1 MB every 900 seconds.

Option F states that the delivery streams to Splunk with buffer size of 5 MB and buffer interval of 60 seconds. This means that data is delivered to Splunk at a frequency of 5 MB every 60 seconds.

Therefore, the three options for data delivery frequency are:

  • A. The kinesis firehose delivery streams to S3 with buffer size between 1-128 MB and buffer interval between 60-900 seconds
  • B. The kinesis firehose delivery streams to S3 with buffer size between 1-100 MB and buffer interval between 60-900 seconds
  • C. The kinesis firehose delivery streams to ES with buffer size between 1-128 MB and buffer interval between 60-900 seconds