DVA-C02 · Question #627
A developer has built an application that inserts data into an Amazon DynamoDB table. The table is configured to use provisioned capacity. The application is deployed on a burstable nano Amazon EC2 in
The correct answer is B. Increase the number of read capacity units (RCUs) that are provisioned for the DynamoDB table. C. Reduce the frequency of requests to DynamoDB by implementing exponential backoff.. ProvisionedThroughputExceededException means requests are exceeding the table's provisioned read/write capacity. The fix requires either increasing capacity or reducing request rate with exponential backoff.
Question
A developer has built an application that inserts data into an Amazon DynamoDB table. The table is configured to use provisioned capacity. The application is deployed on a burstable nano Amazon EC2 instance. The application logs show that the application has been failing because of a ProvisionedThroughputExceededException error. Which actions should the developer take to resolve this issue? (Choose two.)
Options
- AMove the application to a larger EC2 instance.
- BIncrease the number of read capacity units (RCUs) that are provisioned for the DynamoDB table.
- CReduce the frequency of requests to DynamoDB by implementing exponential backoff.
- DIncrease the frequency of requests to DynamoDB by decreasing the retry delay.
- EChange the capacity mode of the DynamoDB table from provisioned to on-demand.
How the community answered
(23 responses)- B87% (20)
- D9% (2)
- E4% (1)
Why each option
ProvisionedThroughputExceededException means requests are exceeding the table's provisioned read/write capacity. The fix requires either increasing capacity or reducing request rate with exponential backoff.
Moving to a larger EC2 instance does not affect DynamoDB's provisioned throughput limits, which are configured at the table level independently of the compute tier.
Increasing RCUs (or WCUs for write operations) directly raises the provisioned throughput ceiling, allowing more requests to succeed without being throttled by DynamoDB.
Exponential backoff is AWS's recommended retry strategy for throttled DynamoDB requests - it progressively increases wait time between retries, reducing burst pressure on the table and improving success rate without requiring capacity changes.
Increasing request frequency would worsen throttling by generating more requests per second than the provisioned capacity allows, causing more exceptions not fewer.
While switching to on-demand capacity would also resolve throttling by auto-scaling, the question asks for two answers and B+C are the direct targeted solutions; E alone also would not implement proper retry logic.
Concept tested: DynamoDB provisioned capacity throttling remediation
Source: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html#Programming.Errors.RetryAndBackoff
Community Discussion
No community discussion yet for this question.