Exam AWS Certified Developer - Associate DVA-C02 topic 1 question 29 discussion

100% AC as per AWS : ProvisionedThroughputExceededException The request rate for the stream is too high, or the requested data is too large for the available throughput. Reduce the frequency or size of your requests. For more information, see Streams Limits in the Amazon Kinesis Data Streams Developer Guide, and Error Retries and Exponential Backoff in AWS in the AWS General Reference. https://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecords.html

A) Correct - Retries with exponential backoff help manage temporary spikes by delaying subsequent retry attempts progressively B) Eliminated - Switching to PutRecord would increase API calls, worsening the throughput issue C) Correct - Reducing request size or frequency directly addresses the throughput limits by spreading out the data more evenly. D) Eliminated - Amazon SNS is a messaging service, not designed for streaming data with high throughput like Kinesis.

==> Discard B: PutRecord doesn't reduce throughput issues as it sends one record at a time, increasing API calls. ==> Discard D: SNS isn't designed for streaming data; it handles pub/sub messaging. ==> Discard E: Reducing KCL consumers affects reading, not writing throughput. - A: Exponential backoff reduces retries during peak usage, easing shard throughput pressure. - C: Lowering request frequency or size directly mitigates throughput exceedance on shards.

Answer is A and C Batch Efficiency: The `PutRecords` API allows you to send multiple records in a single request, which is generally more efficient than sending individual records with `PutRecord`. Using `PutRecords` can help optimize throughput by reducing the number of API calls and better utilizing the available capacity.

AC is the correct answer.

AC is the best answer. When there is throttling, it is best practise to implement retries with exponential backoff.

I think this is really tricky question. To get this exception, the request rate for the stream is too high, or the requested data is too large for the available throughput. Reduce the frequency or size of your requests. So we can "Reduce the frequency and/or size of the requests" also decrease the size with "Use a PutRecord API instead of PutRecords" The API already implements retries with exponential backoff. So there is no need for A.

A and C https://aws.amazon.com/premiumsupport/knowledge-center/kinesis-data-stream-throttling-errors/

AC https://www.examtopics.com/discussions/amazon/view/69142-exam-aws-certified-developer-associate-topic-1-question-370/