A company uses Amazon DynamoDB for managing and tracking orders. The DynamoDB table is partitioned based on the order date. The company receives a huge increase in orders during a sales event, causing DynamoDB writes to throttle, and the consumed throughput is far below the provisioned throughput.
According to AWS best practices, how can this issue be resolved with MINIMAL costs?

Question

A company uses Amazon DynamoDB for managing and tracking orders. The DynamoDB table is partitioned based on the order date. The company receives a huge increase in orders during a sales event, causing DynamoDB writes to throttle, and the consumed throughput is far below the provisioned throughput.

According to AWS best practices, how can this issue be resolved with MINIMAL costs?

J. Cuylits · Accepted Answer

Add a random number suffix to the partition key values.

J. Cuylits · Answer

Create a new DynamoDB table for every order date.

J. Cuylits · Answer

Increase the read and write capacity units of the DynamoDB table.

J. Cuylits · Answer

Add a global secondary index to the DynamoDB table.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 130 - DVA-C01 discussion

Suggested answer: C

0 comments