Partition key selection in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

DynamoDB

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

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

AEmail

BTimestamp

CSortKey

DUserId

Attempts:

3 left

💡 Hint

Common Mistakes

Using the sort key attribute name as the partition key.

Choosing an attribute that is not unique.

The partition key attribute name is typically a unique identifier like UserId.

2fill in blank

medium

Complete the code to specify the attribute type for the partition key in DynamoDB.

DynamoDB

AttributeDefinitions=[{"AttributeName": "UserId", "AttributeType": "[1]"}]

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

AN

BB

CS

DBOOL

Attempts:

3 left

💡 Hint

Common Mistakes

Using BOOL as an attribute type for partition key.

Confusing number (N) with string (S).

The partition key attribute type is usually a string, represented by S in DynamoDB.

3fill in blank

hard

Fix the error in the partition key definition by completing the missing part.

DynamoDB

KeySchema=[{"AttributeName": "UserId", "KeyType": "[1]"}]

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

ARANGE

BHASH

CPRIMARY

DSORT

Attempts:

3 left

💡 Hint

Common Mistakes

Using RANGE instead of HASH for partition key.

Using invalid key types like PRIMARY or SORT.

The partition key must have the key type HASH in DynamoDB.

4fill in blank

hard

Fill both blanks to define a composite key with partition and sort keys.

DynamoDB

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

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

AUserId

BTimestamp

COrderDate

DEmail

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping partition and sort key names.

Using non-unique attributes as partition key.

The partition key is UserId and the sort key is Timestamp to order items.

5fill in blank

hard

Fill all three blanks to define attribute definitions for a composite key.

DynamoDB

AttributeDefinitions=[{"AttributeName": "[1]", "AttributeType": "S"}, {"AttributeName": "[2]", "AttributeType": "[3]"}]

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

AUserId

BTimestamp

CN

DS

Attempts:

3 left

💡 Hint

Common Mistakes

Using string type for Timestamp when it should be number.

Mixing attribute names and types incorrectly.

UserId is a string (S) and Timestamp is a number (N) attribute type.

Practice

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

easy

A. It sets the maximum size of the table.

B. It defines the data type of the table.

C. It determines how data is distributed across storage nodes.

D. It controls the read and write capacity of the table.

Solution

1. Step 1: Understand partition key purpose

   The partition key is used to decide where data is stored in DynamoDB's distributed system.

2. Step 2: Compare options

   Only It determines how data is distributed across storage nodes. correctly describes this role; others describe unrelated features.

3. Final Answer:

   It determines how data is distributed across storage nodes. -> Option C

4. Quick Check:

   Partition key = data distribution [OK]

Hint: Partition key decides data location in storage [OK]

Common Mistakes:

• Confusing partition key with capacity settings
• Thinking partition key sets data type
• Assuming partition key limits table size

2. Which of the following is a valid way to define a partition key in a DynamoDB table creation command?

easy

A. "KeySchema": [{"AttributeName": "UserId", "KeyType": "HASH"}]

B. "KeySchema": [{"AttributeName": "UserId", "KeyType": "RANGE"}]

C. "KeySchema": [{"AttributeName": "UserId", "KeyType": "PRIMARY"}]

D. "KeySchema": [{"AttributeName": "UserId", "KeyType": "INDEX"}]

Solution

1. Step 1: Recall partition key syntax

   Partition key uses KeyType "HASH" in DynamoDB KeySchema.

2. Step 2: Check each option

   Only "KeySchema": [{"AttributeName": "UserId", "KeyType": "HASH"}] uses "HASH" correctly; others use invalid or incorrect KeyType values.

3. Final Answer:

   "KeySchema": [{"AttributeName": "UserId", "KeyType": "HASH"}] -> Option A

4. Quick Check:

   Partition key = KeyType HASH [OK]

Hint: Partition key uses KeyType 'HASH' in schema [OK]

Common Mistakes:

• Using RANGE instead of HASH for partition key
• Confusing PRIMARY or INDEX as KeyType
• Misnaming KeyType values

3. Given a DynamoDB table with partition key UserId having many unique values, and sort key OrderDate, what will happen if you query with UserId = '123' only?

medium

A. The query will fail because sort key is missing.

B. You get all orders for user '123' sorted by OrderDate.

C. You get only one order for user '123' without sorting.

D. You get all orders for all users sorted by OrderDate.

Solution

1. Step 1: Understand query with partition key only

   Querying with partition key returns all items with that key, optionally sorted by sort key.

2. Step 2: Analyze given keys

   Since UserId is partition key and OrderDate is sort key, querying UserId='123' returns all orders for that user sorted by OrderDate.

3. Final Answer:

   You get all orders for user '123' sorted by OrderDate. -> Option B

4. Quick Check:

   Query by partition key returns all matching items [OK]

Hint: Query by partition key returns all matching items [OK]

Common Mistakes:

• Thinking query needs sort key value
• Expecting only one item without sort key
• Assuming query returns all users' data

4. You designed a DynamoDB table with CustomerId as partition key but notice hot partitions causing slow performance. What is the likely cause?

medium

A. CustomerId has too many unique values causing large partitions.

B. CustomerId is used as sort key instead of partition key.

C. CustomerId is missing from the KeySchema.

D. CustomerId has very few unique values causing uneven data distribution.

Solution

1. Step 1: Understand hot partitions

   Hot partitions happen when few partition keys get most traffic, causing uneven load.

2. Step 2: Analyze CustomerId uniqueness

   If CustomerId has few unique values, many requests hit same partitions causing hot spots.

3. Final Answer:

   CustomerId has very few unique values causing uneven data distribution. -> Option D

4. Quick Check:

   Few unique keys = hot partitions [OK]

Hint: Few unique partition keys cause hot partitions [OK]

Common Mistakes:

• Assuming too many unique keys cause hot partitions
• Confusing missing key with performance issue
• Mixing partition key with sort key roles

5. You want to design a DynamoDB table to store IoT sensor data from thousands of devices. Which partition key choice will best support even data distribution and scalability?

hard

A. Use DeviceId as partition key because it has many unique values.

B. Use a constant string like 'SensorData' as partition key for all items.

C. Use Timestamp as partition key to sort data by time.

D. Use DeviceType as partition key since it groups similar devices.

Solution

1. Step 1: Identify key with many unique values

   DeviceId uniquely identifies each device, providing many distinct partition keys.

2. Step 2: Evaluate other options

   Constant string causes hot partition; Timestamp changes too fast for partition key; DeviceType groups few devices causing uneven load.

3. Final Answer:

   Use DeviceId as partition key because it has many unique values. -> Option A

4. Quick Check:

   Many unique keys = good partition key [OK]

Hint: Choose partition key with many unique values [OK]

Common Mistakes:

• Using constant value causing hot partitions
• Choosing timestamp as partition key
• Grouping by device type causing uneven load