Exam AWS Certified Developer Associate topic 1 question 83 discussion

I don't know how people can vote for B and D. B - increases RCU, but the application inserts data, so WCU are needed, => B is wrong D - you application will make more requests per minute, the problem with lack of resources will not disappear, application will have more errors in logs. => D is wrong C. Exponential algorithm will lead to fewer requests per minute => application will start working properly. C is correct E. capacity on demand means that your database will get more required WCU automatically. => E is correct

I'm not sure how increasing the EC2 instance size would help here - seems to be issues with too many writes to DynamoDB. So I'd go for C and E

The ProvisionedThroughputExceedException occurs when the number of read or write requests exceeds the provisioned capacity for the DynamoDB table. B) - Eliminated - As application is inserted the data (so we need to increase WCU, instead of RCU)

ProvisionedThroughputExceedException is related to throughput capacity of DynamoDB. In this context, it is nowhere related to EC2 instance. Answer is C & E.

The key is "an application that **inserts** data into an Amazon DynamoDB table"

ProvisionedThroughputExceededException happens with writing/reading. but the question claims that data is inserted. Therefore B is wrong. E comes with different cost implications and operational considerations but in question we are not looking for the best solution.

the correct actions are B and C

C. Reduce the frequency of requests to DynamoDB by implement ng exponential backoff. I don't know why this is "ng" there? if not typo error, C can't be correct because there isn't "ng exponential backoff" function.

B. Increase the number of read capacity units (RCUs) that are provisioned for the DynamoDB table: The error message indicates that the application is exceeding the provisioned throughput capacity for the DynamoDB table. Increasing the number of RCUs provisioned for the table can help prevent this error from occurring by providing additional throughput capacity. C. Reduce the frequency of requests to DynamoDB by implementing exponential backoff: When an application receives a ProvisionedThroughputExceedException error, it can indicate that it is making too many requests to DynamoDB too quickly. Implementing exponential backoff in the application can help to reduce the frequency of requests and prevent the error from occurring. E. Changing the capacity mode of the DynamoDB table from provisioned to on-demand may help in situations where the workload is unpredictable and sporadic, but it may not provide the necessary performance guarantees required by the application. Additionally, the pricing model for on-demand capacity is different from provisioned capacity and may not be cost-effective for high-volume workloads.

the nominated answer is wrong! The application on its existing infra is already beating the DynamoDB instance - thus the throughput choke. Its C + E - 100%. This answer needs to be corrected

C and E is correct. Good job with putting A as it can really trick you into choosing it, but A says read capacity units, whereas the question states that the problem is about writing data, not reading.

BC The ProvisionedThroughputExceedException error occurs when the number of read or write requests to a DynamoDB table exceeds the provisioned capacity for the table. To resolve this issue, the developer can either increase the number of read capacity units (RCUs) that are provisioned for the DynamoDB table or reduce the frequency of requests to DynamoDB by implementing exponential backoff. Increasing the RCUs allows the table to handle a larger number of requests, while reducing the frequency of requests to DynamoDB can help to avoid exceeding the provisioned capacity.

BC correct answer

CE, who voted for A or D lol

CE: because https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html, not choosing B because it only inceases the RCU (read units), the issue of throughput exceeded could also be with WCU (write units)

A wont help as the issue is facing DynamoDB not application on EC2 B. is incorrect because we are facing issue with writes, not reads C. True D. This statement is logicless - increasing request to dynamo results in higher API usage. E. TRUE

ProvisionedThroughputExceededException is a DynamoDB exception, for this I exclude A. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html The error message says: 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 For this i say B and 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. for this i say D