Dynamodb medium
What is the operational consequence of exceeding the 10GB 'Item Collection' size limit in a table with Local Secondary Indexes (LSIs)?
- A The table data is automatically moved to S3 Glacier.
- B Write Blockage: DynamoDB will reject any further writes to that specific Partition Key (Item Collection) to prevent the physical partition from becoming unmanageably large, though other partitions remain unaffected.
- C The database will charge a 500% premium for every subsequent byte stored.
- D The LSI is converted into a GSI automatically in the background.
Answer: B. Write Blockage: DynamoDB will reject any further writes to that specific Partition Key (Item Collection) to prevent the physical partition from becoming unmanageably large, though other partitions remain unaffected.
LSIs must reside on the same server partition as the base data to support strong consistency. If all items for `UserID: 1` exceed 10GB (including their index entries), they literally run out of room on the physical slice and can no longer be updated. This is why GSIs (which have no collection limit) are preferred for large datasets.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- DynamoDB has a strict 400KB limit on the size of a single item. What is the recommended design pattern if you need to store larger documents (e.g., 5MB PDFs)?
- What is the primary role of the 'Partition Key' in ensuring DynamoDB's infinite horizontal scalability?
- Why is the `Query` operation generally preferred over `Scan` for production workloads in DynamoDB?
- DynamoDB is a 'fully managed' serverless database. What is a primary operational benefit of this model for an engineering team?
- In 'Provisioned Capacity' mode, how is the performance budget of a DynamoDB table defined?
- When would an architect choose to implement DAX (DynamoDB Accelerator) in front of an existing DynamoDB table?