An application has been making use of AWS DynamoDB for its back-end data store.
The size of the table has now grown to 20 GB, and the scans on the table are causing throttling errors.
Which of the following should now be implemented to avoid such errors?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - B.
When you scan your table in Amazon DynamoDB, you should follow the DynamoDB best practices for avoiding sudden bursts of read activity.
You can use the following technique to minimize the impact of a scan on a table's provisioned throughput.
Reduce page size.
Because a Scan operation reads an entire page (by default, 1 MB), you can reduce the scan operation's impact by setting a smaller page size.
The Scan operation provides a Limit parameter that you can use to set the page size for your request.
Each Query or Scan request with a smaller page size uses fewer read operations and creates a "pause" between each request.
For example, suppose that, each item is 4 KB, and you set the page size to 40 items.
A Query request would then consume only 20 eventually consistent read operations or 40 strongly consistent read operations.
A larger number of smaller Query or Scan operations would allow your other critical requests to succeed without throttling.
Option A is incorrect because the page size should be reduced rather than enlarged.
Option C is incorrect because a parallel scan with many workers can easily consume all of the provisioned read capacity.
Option D is incorrect because the sequential scan processes data sequentially.
It does not help to avoid the throttling errors.
For more information, please check below AWS Docs-
https://aws.amazon.com/blogs/developer/rate-limited-scans-in-amazon-dynamodb/ https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-query-scan.htmlIn this scenario, the table in DynamoDB has grown to a size of 20 GB, which has led to throttling errors during scans on the table. To avoid such errors, the following solutions can be implemented:
A. Large Page size - This option is not recommended as a larger page size would mean more data being fetched in each query, which can lead to higher latency and increase the likelihood of throttling errors. Therefore, this option is incorrect.
B. Reduced page size - Reducing the page size would mean that lesser data is being fetched during each query, which can help reduce latency and prevent throttling errors. Therefore, this option could be a possible solution.
C. Parallel Scans - Parallel scans can be used to split the workload across multiple workers, thus reducing the load on each worker and preventing throttling errors. Therefore, this option could also be a possible solution.
D. Sequential scans - Sequential scans would not be an effective solution in this scenario as the size of the table has grown to a point where sequential scans can lead to throttling errors. Therefore, this option is incorrect.
In conclusion, reducing the page size and using parallel scans are both possible solutions to avoid throttling errors when scanning a 20 GB DynamoDB table.