Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 6 Question 93 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 93
Topic #: 6
[All BDS-C00 Questions]

An organization has added a clickstream to their website to analyze traffic. The website is sending each page request with the PutRecord API call to an Amazon Kinesis stream by using the page name as the partition key. During peak spikes in website traffic, a support engineer notices many ProvisionedThroughputExcededException events in the application logs.

What should be done to resolve the issue in the MOST cost-effective way?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Krystal
1 months ago
I bet the support engineer is just sitting there, tapping their foot, waiting for someone to suggest throwing more money at the problem. 'Increase the shards, that'll do it!'
upvoted 0 times
...
Jackie
1 months ago
D) Attaching more consumers to the stream seems like a good way to distribute the load, but I'm not sure it's the 'most cost-effective' solution. Wouldn't that just mean more EC2 instances or Lambda functions running?
upvoted 0 times
Tegan
2 days ago
D) Attaching more consumers to the stream could be costly with additional EC2 instances or Lambda functions.
upvoted 0 times
...
Ivette
23 days ago
C) Modify the application to use the Kinesis Producer Library to aggregate requests before sending them to the Kinesis stream.
upvoted 0 times
...
Dalene
1 months ago
B) Increase the number of shards on the Kinesis stream to allow for more throughput to meet the peak spikes in traffic.
upvoted 0 times
...
...
Malinda
2 months ago
Hmm, I wonder if the website developers are just trying to break the Kinesis stream on purpose. 'Clickstream analysis' sounds like a fancy way of saying 'let's overwhelm the poor Kinesis stream!'
upvoted 0 times
Mable
23 days ago
D) Attach more consumers to the Kinesis stream to process records in parallel, improving the performance on the stream.
upvoted 0 times
...
Florencia
25 days ago
C) Modify the application to use on the Kinesis Producer Library to aggregate requests before sending them to the Kinesis stream.
upvoted 0 times
...
Ashleigh
1 months ago
B) Increase the number of shards on the Kinesis stream to allow for more throughput to meet the peak spikes in traffic.
upvoted 0 times
...
William
2 months ago
A) Create multiple Amazon Kinesis streams for page requests to increase the concurrency of the clickstream.
upvoted 0 times
...
...
Micah
2 months ago
C) Using the Kinesis Producer Library to aggregate requests sounds like a smart idea. That way, you can batch the records and reduce the number of API calls, which should help avoid the throughput exceptions.
upvoted 0 times
Anjelica
1 months ago
C) Agreed, using the Kinesis Producer Library to aggregate requests seems like a good solution to handle the peak traffic spikes efficiently.
upvoted 0 times
...
Ben
1 months ago
B) Increase the number of shards on the Kinesis stream to allow for more throughput to meet the peak spikes in traffic.
upvoted 0 times
...
...
Boris
2 months ago
B) Increasing the number of shards seems like the most straightforward and effective way to handle the throughput issue. It's a simple fix that should solve the problem without too much overhead.
upvoted 0 times
Chun
16 days ago
B) Increasing the number of shards is definitely a cost-effective solution to address the ProvisionedThroughputExcededException events.
upvoted 0 times
...
Levi
17 days ago
D) Attaching more consumers to the Kinesis stream could improve performance by processing records in parallel.
upvoted 0 times
...
Delbert
21 days ago
A) Creating multiple Amazon Kinesis streams could also help increase concurrency and handle the peak spikes in traffic.
upvoted 0 times
...
Margo
27 days ago
B) Increasing the number of shards seems like the most straightforward and effective way to handle the throughput issue. It's a simple fix that should solve the problem without too much overhead.
upvoted 0 times
...
...
Luisa
2 months ago
That's a good point, Sylvia. Option C could indeed help optimize the performance of the clickstream in a cost-effective way.
upvoted 0 times
...
Sylvia
2 months ago
I disagree with Luisa. I believe option C is the most cost-effective solution. Using the Kinesis Producer Library to aggregate requests before sending them to the stream will help reduce the number of ProvisionedThroughputExceededException events.
upvoted 0 times
...
Luisa
3 months ago
I think option B is the best choice. Increasing the number of shards will allow for more throughput during peak spikes in traffic.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77