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.)
The application is experiencing a ProvisionedThroughputExceededException, which indicates that the request rate is exceeding the provisioned throughput for the DynamoDB table. To address this issue, the developer should reduce the frequency of requests to DynamoDB by implementing exponential backoff. This strategy involves progressively increasing the delay between retries, effectively managing request retries and smoothing out the burst rate of requests. Additionally, changing the capacity mode of the DynamoDB table from provisioned to on-demand will automatically adjust to the request rate as necessary, eliminating the need to manage provisioned capacity manually and preventing the exception.
C. Reduce the frequency of requests to DynamoDB by implementing exponential backoff. E. Change the capacity mode of the DynamoDB table from provisioned to on-demand.
C & E correct
B. This error indicates that the application's request rate is exceeding the throughput that has been provisioned for the table. Increasing the provisioned read capacity units (RCUs) and/or write capacity units (WCUs) for the DynamoDB table will allow it to handle a higher request rate, thereby reducing the likelihood of encountering this error. However, this approach requires careful capacity planning and may increase costs. C. Exponential backoff is a standard error retry strategy that involves progressively increasing the delay between retries when there is a ProvisionedThroughputExceededException. This approach helps to smooth out the rate of requests, giving the table time to accommodate bursts of read or write requests. Implementing exponential backoff in the application will help to effectively manage request retries and reduce the chance of continually hitting the provisioned throughput limit.
What the question said is insert data..so B increase read capacity is not correct.Hence C and E.
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html
CE is the correct answer.
B. Increase the number of read capacity units (RCUs) that are provisioned for the DynamoDB table. OR E. Change the capacity mode of the DynamoDB table from provisioned to on-demand. C. Reduce the frequency of requests to DynamoDB by implementing exponential backoff.
It 'inserts' data, so it needs WCUs and not RCUs. So option B is invalid too. C and E are the correct options.
Based on ChatGPT: BC
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ProvisionedThroughput.html#:~:text=The%20DynamoDB%20console%20displays%20Amazon%20CloudWatch%20metrics%20for%20your%20tables%2C%20so%20you%20can%20monitor%20throttled%20read%20requests%20and%20write%20requests.%20If%20you%20encounter%20excessive%20throttling%2C%20you%20should%20consider%20increasing%20your%20table%27s%20provisioned%20throughput%20settings.
choosing C & E after going through https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html
Answer is C & E: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html ProvisionedThroughputExceededException Message: You exceeded your maximum allowed provisioned throughput for a table or for one or more global secondary indexes. To view performance metrics for provisioned throughput vs. consumed throughput, open the Amazon CloudWatch console. Example: Your request rate is too high. The AWS SDKs for DynamoDB automatically retry requests that receive this exception. Your request is eventually successful, unless your retry queue is too large to finish. Reduce the frequency of requests using Error retries and exponential backoff.