A developer has an application that uses an Amazon DynamoDB table with a configured local secondary index (LSI). During application testing, the DynamoDB table metrics report a ProvisionedThroughputExceededException error message. The number of requests made by the test suite did not exceed the table's provisioned capacity limits. What is the cause of this issue?

Question

Accepted Answer

A. The data in the table's partition key column is not evenly distributed. DynamoDB distributes data across partitions based on partition key values. When partition key data is not evenly distributed, a disproportionate share of requests is routed to a single partition, exhausting that partition's share of the allocated throughput even though the table-level capacity appears sufficient.

Answer

B. The LSI's capacity is different from the table's capacity. A Local Secondary Index shares the read and write capacity of its base table partition; it does not have separate or different capacity limits that could cause this error independently.

Answer

C. The application is not implementing exponential backoff retry logic while interacting with the Lack of exponential backoff retry logic means the application does not handle throttling gracefully, but it is not the root cause of the throttling itself.

Answer

D. The application has the IAM permission to query the DynamoDB table but not to query the LSI. Insufficient IAM permissions to query an LSI would result in an AccessDeniedException, not a ProvisionedThroughputExceededException.

A developer has an application that uses an Amazon DynamoDB table with a configured local secondary index (LSI). During application testing, the DynamoDB table metrics report a ProvisionedThroughputEx

Question

Options

How the community answered

Why each option

Community Discussion