In North America, a business launched a mobile game that swiftly expanded to 10 million daily active players. The game's backend is hosted on AWS and makes considerable use of a TTL-configured Amazon DynamoDB table.
When an item is added or changed, its TTL is set to 600 seconds plus the current epoch time. The game logic is reliant on the purging of outdated data in order to compute rewards points properly. At times, items from the table are read that are many hours beyond their TTL expiration.
How should a database administrator resolve this issue?

Question

In North America, a business launched a mobile game that swiftly expanded to 10 million daily active players. The game's backend is hosted on AWS and makes considerable use of a TTL-configured Amazon DynamoDB table.

When an item is added or changed, its TTL is set to 600 seconds plus the current epoch time. The game logic is reliant on the purging of outdated data in order to compute rewards points properly. At times, items from the table are read that are many hours beyond their TTL expiration.

How should a database administrator resolve this issue?

Sanaa CHOKIRI · Accepted Answer

Include a query filter expression to ignore items with an expired TTL.

Sanaa CHOKIRI · Answer

Use a client library that supports the TTL functionality for DynamoDB.

Sanaa CHOKIRI · Answer

Set the ConsistentRead parameter to true when querying the table.

Sanaa CHOKIRI · Answer

Create a local secondary index on the TTL attribute.

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 178 - DBS-C01 discussion

Suggested answer: B

0 comments