Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon BDS-C00 Exam - Topic 6 Question 93 Discussion

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?
C) Modify the application to use on the Kinesis Producer Library to aggregate requests before sending them to the Kinesis stream.
A) Create multiple Amazon Kinesis streams for page requests to increase the concurrency of the clickstream.
B) Increase the number of shards on the Kinesis stream to allow for more throughput to meet the peak spikes in traffic.
D) Attach more consumers to the Kinesis stream to process records in parallel, improving the performance on the stream.

Amazon BDS-C00 Exam - 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

by Jettie at May 20, 2024, 08:09 AM

Limited Time Offer

25%

Off

Get Premium BDS-C00 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
India
6 months ago
Attaching more consumers won't solve the throughput problem directly.
upvoted 0 times
...
Jina
6 months ago
Wait, can you really aggregate requests like that? Sounds interesting!
upvoted 0 times
...
Erasmo
7 months ago
More streams? That sounds expensive and complicated.
upvoted 0 times
...
Kassandra
7 months ago
I think using the Kinesis Producer Library is a smarter approach!
upvoted 0 times
...
Devon
7 months ago
Increasing the number of shards is a common fix for throughput issues.
upvoted 0 times
...
Mammie
7 months ago
Attaching more consumers could improve performance, but I feel like that wouldn't directly address the throughput issue. I think increasing shards might be the best bet.
upvoted 0 times
...
Claudia
7 months ago
I'm a bit confused about the best approach. Creating multiple streams sounds like it could help, but I wonder if it would just complicate things.
upvoted 0 times
...
Lauran
8 months ago
I think I came across a similar question where modifying the application to aggregate requests helped reduce the load. That might be a good option here too.
upvoted 0 times
...
Oneida
8 months ago
I remember studying Kinesis and how it handles throughput. Increasing shards seems like a straightforward solution, but I'm not sure if it's the most cost-effective.
upvoted 0 times
...
Leota
8 months ago
Okay, I think I've got a handle on this. The key is to find a way to reduce the load on the Kinesis stream without just throwing more resources at it. Aggregating the requests before sending them to the stream seems like the most efficient solution. I'm going to make sure I understand how to implement that properly.
upvoted 0 times
...
Ming
8 months ago
Hmm, this is a tricky one. I'm leaning towards option C - using the Kinesis Producer Library to aggregate requests. That seems like the most cost-effective approach, and it should help reduce the load on the stream during those peak traffic spikes. I'll make sure to read through the details on that option carefully.
upvoted 0 times
...
Detra
8 months ago
I'm a bit confused on this one. Creating multiple streams could work, but that might get complicated to manage. And I'm not sure if adding more consumers would really help if the issue is with the throughput on the stream itself. I'll have to think this through carefully.
upvoted 0 times
...
Erinn
8 months ago
I think the key here is to find the most cost-effective solution. Increasing the number of shards or adding more consumers might work, but they could get expensive. Modifying the application to aggregate requests before sending them to the stream seems like a good way to reduce the load on the stream.
upvoted 0 times
...
Val
8 months ago
Okay, this seems straightforward. The question is asking about the engineering mode setting on the gNodeB RF unit, so I'll select the correct answer based on that.
upvoted 0 times
...
Man
8 months ago
Virtual links were mentioned in a similar question, but did we cover whether they can be configured in Cisco FMC for FTD? I'm not entirely sure.
upvoted 0 times
...
Alberta
8 months ago
I've got this! The key is to configure the customer inventory records in a hierarchy and maintain the service history at the subcomponent level. This will allow us to easily track the containers and their components, which is exactly what the question is asking for. I'm confident this is the right approach.
upvoted 0 times
...
Krystal
1 year 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 year 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
12 months ago
D) Attaching more consumers to the stream could be costly with additional EC2 instances or Lambda functions.
upvoted 0 times
...
Ivette
1 year 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 year 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
1 year 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
1 year ago
D) Attach more consumers to the Kinesis stream to process records in parallel, improving the performance on the stream.
upvoted 0 times
...
Florencia
1 year 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 year 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
1 year ago
A) Create multiple Amazon Kinesis streams for page requests to increase the concurrency of the clickstream.
upvoted 0 times
...
...
Micah
1 year 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 year 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 year 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
1 year 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
1 year ago
B) Increasing the number of shards is definitely a cost-effective solution to address the ProvisionedThroughputExcededException events.
upvoted 0 times
...
Levi
1 year ago
D) Attaching more consumers to the Kinesis stream could improve performance by processing records in parallel.
upvoted 0 times
...
Delbert
1 year ago
A) Creating multiple Amazon Kinesis streams could also help increase concurrency and handle the peak spikes in traffic.
upvoted 0 times
...
Margo
1 year 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
1 year 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
1 year 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
1 year 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