nerdexam
Amazon

DBS-C01 · Question #164

A development team at an international gaming company is experimenting with Amazon DynamoDB to store in-game events for three mobile games. The most popular game hosts a maximum of 500,000…

The correct answer is D. Create one table for each game. Use the player identifier as the partition key. An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes. https://docs.aws.amazon.com/sdk-for- ruby/v3/api/Aws/DynamoDB/Types/ItemCollectionSizeLimitExceededException.html

Submitted by kevin_r· Mar 6, 2026Workload-Specific Database Design

Question

A development team at an international gaming company is experimenting with Amazon DynamoDB to store in-game events for three mobile games. The most popular game hosts a maximum of 500,000 concurrent users, and the least popular game hosts a maximum of 10,000 concurrent users. The average size of an event is 20 KB, and the average user session produces one event each second. Each event is tagged with a time in milliseconds and a globally unique identifier. The lead developer created a single DynamoDB table for the events with the following schema:

Partition key: game name Sort key: event identifier Local secondary index: player identifier Event time The tests were successful in a small-scale development environment. However, when deployed to production, new events stopped being added to the table and the logs show DynamoDB failures with the ItemCollectionSizeLimitExceededException error code. Which design change should a database specialist recommend to the development team?

Options

  • AUse the player identifier as the partition key.
  • BCreate two tables. Use the game name as the partition key in both tables.
  • CReplace the sort key with a compound value consisting of the player identifier collated with the
  • DCreate one table for each game. Use the player identifier as the partition key.

How the community answered

(26 responses)
  • A
    8% (2)
  • B
    23% (6)
  • C
    12% (3)
  • D
    58% (15)

Explanation

An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes. https://docs.aws.amazon.com/sdk-for- ruby/v3/api/Aws/DynamoDB/Types/ItemCollectionSizeLimitExceededException.html

Topics

#DynamoDB#partition key#schema design#database scaling

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DBS-C01 Practice