DAS-C01 · Question #29
A Publisher website captures user activity and sends clickstream data to Amazon Kinesis Data Streams. The Publisher wants to design a cost-effective solution to process the data to create a timeline…
The correct answer is C. Include a session identifier in the clickstream data from the Publisher website and use as the. Partitioning by the session ID will allow a single processor to process all the actions for a user session in order. An AWS Lambda function can call the UpdateShardCount API action to change the number of shards in the stream. The KCL will automatically manage the number of…
Question
A Publisher website captures user activity and sends clickstream data to Amazon Kinesis Data Streams. The Publisher wants to design a cost-effective solution to process the data to create a timeline of user activity within a session. The solution must be able to scale depending on the number of active sessions. Which solution meets these requirements?
Options
- AInclude a variable in the clickstream data from the Publisher website to maintain a counter for the
- BInclude a variable in the clickstream to maintain a counter for each user action during their
- CInclude a session identifier in the clickstream data from the Publisher website and use as the
- DInclude a variable in the clickstream data from the Publisher website to maintain a counter for the
How the community answered
(26 responses)- B4% (1)
- C88% (23)
- D8% (2)
Explanation
Partitioning by the session ID will allow a single processor to process all the actions for a user session in order. An AWS Lambda function can call the UpdateShardCount API action to change the number of shards in the stream. The KCL will automatically manage the number of processors to match the number of shards. Amazon EC2 Auto Scaling will assure the correct number of instances are running to meet the processing load.
Topics
Community Discussion
No community discussion yet for this question.