Which solutions will mitigate this error MOST cost-effectively?
(Choose two.)
Modify the application code to perform exponential backoff when the error is received.
Modify the application to use the AWS SDKs for DynamoDB.
Increase the read and write throughput of the DynamoDB table.
Create a DynamoDB Accelerator (DAX) cluster for the DynamoDB table.
Create a second DynamoDB table. Distribute the reads and writes between the two tables.
Explanations:
Exponential backoff is a recommended approach for handling ProvisionedThroughputExceededException errors. It helps by delaying retries in increasing intervals, reducing the chances of overwhelming the table with requests, and preventing further throughput throttling.
Using the AWS SDKs for DynamoDB abstracts the retry logic and implements best practices for handling throughput exceptions, such as exponential backoff, which improves reliability and helps avoid throughput errors.
Increasing the throughput can temporarily solve the issue but is not a cost-effective long-term solution. It incurs additional costs and does not address the root cause of the issue, which is the application’s request pattern.
DynamoDB Accelerator (DAX) is primarily for improving read performance and would not directly mitigate write throughput errors (ProvisionedThroughputExceededException). It also introduces additional costs and complexity.
Creating a second DynamoDB table is not an effective solution for managing throughput limits. It adds complexity to the application and does not directly address the underlying issue of exceeding the provisioned throughput.
Based on what I know, the answer is:
Modify the application code to perform exponential backoff when the error is received.