Item size limits and considerations in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the maximum item size allowed in DynamoDB.

DynamoDB

The maximum item size in DynamoDB is [1] bytes.

Drag options to blanks, or click blank then click option'

A409600

B4000000

C4000

D40000

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing bytes with kilobytes or megabytes.

Using 4000 bytes which is too small for DynamoDB items.

DynamoDB limits each item to a maximum size of 400 KB (409,600 bytes).

2fill in blank

medium

Complete the code to identify which attribute types count towards the item size limit.

DynamoDB

In DynamoDB, the size of an item includes all attribute names and values, including [1].

Drag options to blanks, or click blank then click option'

Abinary data

Bonly string data

Conly numeric data

Donly primary key attributes

Attempts:

3 left

💡 Hint

Common Mistakes

Assuming only string or numeric data count towards size.

Ignoring binary data size contribution.

All attribute names and values count towards the item size, including binary data.

3fill in blank

hard

Fix the error in the statement about item size limits.

DynamoDB

DynamoDB items can be up to [1], including attribute names and values.

Drag options to blanks, or click blank then click option'

A10 MB

B100 KB

C400 KB

D1 MB

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 400 KB with 1 MB or 10 MB limits.

Assuming the limit is larger than it actually is.

The correct maximum item size is 400 KB, not 1 MB or larger.

4fill in blank

hard

Fill both blanks to complete the explanation about item size considerations.

DynamoDB

To avoid exceeding the [1] limit, you can [2] large attributes or split data across multiple items.

Drag options to blanks, or click blank then click option'

A400 KB

Bcompress

C1 MB

Dignore

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect size limits like 1 MB.

Ignoring large attribute handling.

The item size limit is 400 KB. Compressing large attributes helps stay within this limit.

5fill in blank

hard

Fill all three blanks to complete the code snippet about item size and attribute handling.

DynamoDB

If an item exceeds [1], consider [2] data into smaller items or using [3] to reduce size.

Drag options to blanks, or click blank then click option'

A400 KB

Bsplitting

Ccompression

Dignoring

Attempts:

3 left

💡 Hint

Common Mistakes

Ignoring the size limit or using wrong values.

Choosing 'ignoring' as a strategy.

Items larger than 400 KB should be split or compressed to fit DynamoDB limits.

Practice

1. What is the maximum size allowed for a single item in DynamoDB, including attribute names and values?

easy

A. 400 KB

B. 1 MB

C. 100 KB

D. 10 MB

Solution

1. Step 1: Understand DynamoDB item size limit

   DynamoDB limits each item to a maximum size of 400 KB, which includes both attribute names and values.

2. Step 2: Compare options with the known limit

   Among the options, only 400 KB matches the official DynamoDB item size limit.

3. Final Answer:

   400 KB -> Option A

4. Quick Check:

   Item size limit = 400 KB [OK]

Hint: Remember DynamoDB item max size is 400 KB total [OK]

Common Mistakes:

• Confusing item size with partition size
• Thinking 1 MB is allowed per item
• Ignoring attribute names in size calculation

2. Which of the following is the correct way to store a large file in DynamoDB considering item size limits?

easy

A. Store the entire file as a single attribute in one item

B. Split the file into chunks and store each chunk in separate items

C. Store the file outside DynamoDB and save only a reference in the item

D. Compress the file and store it in a single attribute without splitting

Solution

1. Step 1: Consider item size limits for large files

   Since DynamoDB items have a 400 KB size limit, storing large files directly is not practical.

2. Step 2: Evaluate storage options

   Storing large files outside DynamoDB (like in S3) and saving a reference inside DynamoDB is the recommended approach to handle large data efficiently.

3. Final Answer:

   Store the file outside DynamoDB and save only a reference in the item -> Option C

4. Quick Check:

   Large files stored externally with references = C [OK]

Hint: Use external storage for large files, keep references in DynamoDB [OK]

Common Mistakes:

• Trying to store large files directly in one item
• Splitting files into many items without external storage
• Ignoring size limits and compressing without splitting

3. Given a DynamoDB item with attributes: {"id": "123", "name": "Alice", "bio": "A" repeated 300000 times}, what will happen when you try to insert this item?

medium

A. The operation will fail due to item size exceeding 400 KB

B. The item will be inserted successfully

C. Only the "id" and "name" attributes will be stored

D. The "bio" attribute will be truncated automatically

Solution

1. Step 1: Calculate approximate item size

   The "bio" attribute contains 300,000 characters. Each character is roughly 1 byte, so bio alone is about 300 KB. Adding attribute names and other attributes likely exceeds 400 KB.

2. Step 2: Understand DynamoDB behavior on size limit breach

   DynamoDB rejects items that exceed the 400 KB limit; it does not truncate or partially store attributes.

3. Final Answer:

   The operation will fail due to item size exceeding 400 KB -> Option A

4. Quick Check:

   Item size > 400 KB causes failure = B [OK]

Hint: Check total size; over 400 KB items fail insert [OK]

Common Mistakes:

• Assuming DynamoDB truncates large attributes
• Thinking partial attributes are stored
• Ignoring attribute name size in total

4. You wrote code to insert an item with a large attribute but get a validation error. What is the most likely cause?

medium

A. The network connection timed out

B. The attribute name contains invalid characters

C. The table does not have a primary key defined

D. The item size exceeds DynamoDB's 400 KB limit

Solution

1. Step 1: Identify common causes of validation errors

   Validation errors often occur when the item violates DynamoDB constraints, such as size limits.

2. Step 2: Match error cause with large attribute insertion

   Inserting a large attribute likely caused the item size to exceed 400 KB, triggering the validation error.

3. Final Answer:

   The item size exceeds DynamoDB's 400 KB limit -> Option D

4. Quick Check:

   Validation error from size limit breach = A [OK]

Hint: Validation errors often mean item too large [OK]

Common Mistakes:

• Assuming network or key errors cause validation error
• Ignoring item size in error diagnosis
• Not checking attribute name rules

5. You need to store user profiles with a photo and detailed bio in DynamoDB. The photo is 1 MB and the bio is 300 KB. How should you design your data to respect DynamoDB item size limits?

hard

A. Store the photo and bio together in one item, compressing both to fit under 400 KB

B. Store the photo in Amazon S3 and save the S3 URL and bio in DynamoDB item

C. Split the photo into multiple items and store the bio in a separate item

D. Store only the photo in DynamoDB and omit the bio

Solution

1. Step 1: Analyze size constraints for photo and bio

   The photo is 1 MB, which exceeds DynamoDB's 400 KB item limit. The bio is 300 KB, close to the limit alone.

2. Step 2: Choose a design respecting limits and best practices

   Storing large files like photos in Amazon S3 and saving only the reference (URL) along with the bio in DynamoDB is the recommended approach.

3. Final Answer:

   Store the photo in Amazon S3 and save the S3 URL and bio in DynamoDB item -> Option B

4. Quick Check:

   Large files in S3, references in DynamoDB = A [OK]

Hint: Put big files in S3, keep metadata in DynamoDB [OK]

Common Mistakes:

• Trying to compress large files to fit in one item
• Splitting large files into multiple items unnecessarily
• Omitting important data like bio