Partition key distribution in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the partition key attribute name in a DynamoDB table creation.

DynamoDB

KeySchema=[{'AttributeName': [1], 'KeyType': 'HASH'}]

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

A'UserId'

B'SortKey'

C'Timestamp'

D'IndexKey'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the sort key name instead of the partition key.

Confusing 'HASH' with 'RANGE' key types.

The partition key attribute name is specified with 'AttributeName' in the KeySchema. 'UserId' is a common partition key.

2fill in blank

medium

Complete the code to define the attribute type for the partition key in the attribute definitions.

DynamoDB

AttributeDefinitions=[{'AttributeName': 'UserId', 'AttributeType': [1]]

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

A'S'

B'BOOL'

C'B'

D'N'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'BOOL' which is not a valid attribute type for keys.

Confusing 'N' (number) with 'S' (string).

The partition key attribute type must be specified. 'S' stands for String, which is common for partition keys.

3fill in blank

hard

Fix the error in the partition key definition by choosing the correct key type.

DynamoDB

KeySchema=[{'AttributeName': 'UserId', 'KeyType': [1]]

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

A'RANGE'

B'HASH'

C'PRIMARY'

D'PARTITION'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'RANGE' for partition key.

Using invalid key types like 'PRIMARY' or 'PARTITION'.

The partition key must have the key type 'HASH'. 'RANGE' is for sort keys.

4fill in blank

hard

Fill both blanks to create a DynamoDB table with a partition key and a sort key.

DynamoDB

KeySchema=[{'AttributeName': [1], 'KeyType': 'HASH'}, {'AttributeName': [2], 'KeyType': 'RANGE'}]

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

A'UserId'

B'Timestamp'

C'OrderId'

D'Category'

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping partition and sort key names.

Using invalid attribute names for keys.

The partition key is 'UserId' with 'HASH' key type, and the sort key is 'Timestamp' with 'RANGE' key type.

5fill in blank

hard

Fill all three blanks to define attribute definitions for a table with a string partition key and a number sort key.

DynamoDB

AttributeDefinitions=[{'AttributeName': [1], 'AttributeType': [2], {'AttributeName': [3], 'AttributeType': 'N'}]

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

A'UserId'

B'S'

C'Timestamp'

D'OrderId'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing attribute names and types.

Using wrong attribute types for keys.

'UserId' is the partition key with type 'S' (string), and 'Timestamp' is the sort key with type 'N' (number).

Practice

1. What is the main purpose of a partition key in DynamoDB?

easy

A. To create backups of the database

B. To store large files in the database

C. To encrypt data automatically

D. To divide data into parts for faster access

Solution

1. Step 1: Understand the role of partition key

   The partition key is used to split data into different sections called partitions.

2. Step 2: Recognize the benefit of partitioning

   This splitting helps DynamoDB access data faster by looking in smaller parts instead of the whole table.

3. Final Answer:

   To divide data into parts for faster access -> Option D

4. Quick Check:

   Partition key divides data = faster access [OK]

Hint: Partition key splits data to speed up access [OK]

Common Mistakes:

• Thinking partition key stores files
• Confusing partition key with encryption
• Assuming partition key creates backups

2. Which of the following is the correct way to define a partition key in a DynamoDB table using AWS CLI?

easy

A. aws dynamodb create-table --table-name MyTable --key-schema AttributeName=UserId,KeyType=HASH --attribute-definitions AttributeName=UserId,AttributeType=S --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5

B. aws dynamodb create-table --table-name MyTable --partition-key UserId --attribute-type String

C. aws dynamodb create-table --table-name MyTable --key UserId --type HASH

D. aws dynamodb create-table --table-name MyTable --primary-key UserId STRING

Solution

1. Step 1: Review AWS CLI syntax for creating table with partition key

   The correct syntax uses --key-schema with AttributeName and KeyType=HASH for partition key.

2. Step 2: Check attribute definitions and throughput

   Attribute definitions must specify AttributeName and AttributeType, and provisioned throughput is required.

3. Final Answer:

   aws dynamodb create-table --table-name MyTable --key-schema AttributeName=UserId,KeyType=HASH --attribute-definitions AttributeName=UserId,AttributeType=S --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 -> Option A

4. Quick Check:

   Correct AWS CLI syntax = aws dynamodb create-table --table-name MyTable --key-schema AttributeName=UserId,KeyType=HASH --attribute-definitions AttributeName=UserId,AttributeType=S --provisioned-throughput ReadCapacityUnits=5,WriteCapacityUnits=5 [OK]

Hint: Use --key-schema with KeyType=HASH for partition key [OK]

Common Mistakes:

• Using --partition-key instead of --key-schema
• Missing attribute definitions
• Incorrect key type syntax

3. Given a DynamoDB table with partition key 'UserId' having only two values: 'A' and 'B', what is the likely impact on partition key distribution?

medium

A. Good distribution because two keys are enough

B. Poor distribution causing hot partitions

C. No impact because DynamoDB balances automatically

D. Table will reject writes due to low key variety

Solution

1. Step 1: Understand partition key uniqueness importance

   Partition keys with few unique values cause data to cluster in few partitions.

2. Step 2: Recognize effect of low unique keys

   This clustering leads to hot partitions, slowing down performance and limiting scalability.

3. Final Answer:

   Poor distribution causing hot partitions -> Option B

4. Quick Check:

   Few unique keys = hot partitions [OK]

Hint: Few keys cause hot partitions, hurting performance [OK]

Common Mistakes:

• Assuming two keys are enough for good distribution
• Believing DynamoDB auto-balances all cases
• Thinking table rejects writes for low key variety

4. You notice your DynamoDB table has uneven partition key distribution causing slow queries. Which change will fix this?

medium

A. Change partition key to a field with many unique values

B. Increase read capacity units only

C. Add a sort key with the same values as partition key

D. Delete and recreate the table without changes

Solution

1. Step 1: Identify cause of uneven distribution

   Uneven distribution happens when partition key has few unique values.

2. Step 2: Choose a partition key with high uniqueness

   Changing to a key with many unique values spreads data evenly across partitions, improving performance.

3. Final Answer:

   Change partition key to a field with many unique values -> Option A

4. Quick Check:

   High uniqueness partition key = even distribution [OK]

Hint: Pick partition key with many unique values to fix distribution [OK]

Common Mistakes:

• Only increasing capacity without fixing key
• Adding sort key with same values doesn't help
• Recreating table without changing key

5. You have a DynamoDB table storing orders with partition key 'CustomerId'. Some customers place thousands of orders daily, others only a few. How can you improve partition key distribution to avoid hot partitions?

hard

A. Use 'OrderId' alone as partition key

B. Keep 'CustomerId' as partition key and add 'OrderId' as sort key

C. Use a composite key combining 'CustomerId' and 'OrderDate' as partition key

D. Use a random number as partition key for all orders

Solution

1. Step 1: Identify problem with current partition key

   Using only 'CustomerId' causes hot partitions for customers with many orders.

2. Step 2: Improve distribution by combining keys

   Combining 'CustomerId' and 'OrderDate' creates more unique partition keys, spreading load better.

3. Step 3: Understand why other options fail

   Keep 'CustomerId' as partition key and add 'OrderId' as sort key keeps same partition key, so hot partitions remain; Use 'OrderId' alone as partition key loses customer grouping; Use a random number as partition key for all orders breaks data organization.

4. Final Answer:

   Use a composite key combining 'CustomerId' and 'OrderDate' as partition key -> Option C

5. Quick Check:

   Composite key increases uniqueness, reduces hot partitions [OK]

Hint: Combine keys to increase uniqueness and spread load [OK]

Common Mistakes:

• Adding sort key but not changing partition key
• Using only order ID loses customer grouping
• Random keys break data access patterns