Hierarchical data modeling in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the partition key for a DynamoDB table storing hierarchical data.

DynamoDB

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

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

AParentId

BItemId

CSortKey

DCategory

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ItemId' as partition key prevents efficient retrieval of all children under a parent.

The partition key 'ParentId' groups all child items under the same parent for efficient hierarchical queries.

2fill in blank

medium

Complete the code to define the sort key for ordering child items under a parent in DynamoDB.

DynamoDB

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

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

AParentId

BCategory

CTimestamp

DChildId

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ParentId' as sort key, which duplicates the partition key.

The sort key 'ChildId' uniquely identifies and allows ordering of child items under the same parent.

3fill in blank

hard

Fix the error in the DynamoDB query to fetch all children of a parent item.

DynamoDB

const params = { TableName: 'Items', KeyConditionExpression: '[1] = :parentId', ExpressionAttributeValues: { ':parentId': 'parent456' } };

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

AChildId

BCategory

CParentId

DSortKey

Attempts:

3 left

💡 Hint

Common Mistakes

Adding a sort key condition like 'ChildId = :id', which returns only one child.

The KeyConditionExpression uses only the partition key 'ParentId = :parentId' to retrieve all children under the parent.

4fill in blank

hard

Fill both blanks to create a DynamoDB item representing a child with a reference to its parent.

DynamoDB

Item: { 'ChildId': [1], 'ParentId': [2], 'Name': 'Child Item' }

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

A'child123'

B'parent456'

C'child456'

D'parent123'

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping child and parent IDs.

The 'ChildId' is the child's unique ID (sort key), and 'ParentId' references the parent's ID (partition key).

5fill in blank

hard

Fill all three blanks to write a DynamoDB query that retrieves all children of a parent sorted by child ID.

DynamoDB

const params = { TableName: 'Items', KeyConditionExpression: '[1] = :parentId', ExpressionAttributeValues: { ':parentId': [2] }, ScanIndexForward: [3] };

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

AParentId

B'parent456'

Ctrue

DItemId

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ItemId' instead of 'ParentId' in the condition.

Using false for ScanIndexForward when ascending order is needed.

The query filters by 'ParentId' equal to the parent's ID and sorts results in ascending order by ChildId (ScanIndexForward: true).

Practice

1. What is the main purpose of hierarchical data modeling in DynamoDB?

easy

A. To organize data with parent-child relationships

B. To store unrelated data in separate tables

C. To improve data encryption

D. To increase the size of the database

Solution

1. Step 1: Understand hierarchical data modeling

   Hierarchical data modeling organizes data by showing relationships where one item is the parent and others are children.

2. Step 2: Relate to DynamoDB usage

   DynamoDB uses this model to efficiently store and query related items using keys.

3. Final Answer:

   To organize data with parent-child relationships -> Option A

4. Quick Check:

   Hierarchical data = parent-child organization [OK]

Hint: Think parent and child data linked by keys [OK]

Common Mistakes:

• Confusing hierarchical with unrelated data storage
• Thinking it improves encryption
• Assuming it increases database size

2. Which key should be used as the partition key to model a parent item in DynamoDB hierarchical data?

easy

A. Child ID

B. Parent ID

C. Timestamp

D. Random UUID

Solution

1. Step 1: Identify the role of partition key

   The partition key groups related items together in DynamoDB.

2. Step 2: Choose the key representing the parent

   Since the parent is the main group, its ID should be the partition key to link children under it.

3. Final Answer:

   Parent ID -> Option B

4. Quick Check:

   Partition key = Parent ID for grouping [OK]

Hint: Partition key groups parents; use Parent ID [OK]

Common Mistakes:

• Using Child ID as partition key
• Choosing timestamp which is unrelated
• Using random UUID that breaks grouping

3. Given a DynamoDB table with partition key ParentID and sort key ChildID, what will the query KeyConditionExpression: ParentID = 'P1' return?

medium

A. Only child items with ChildID 'P1'

B. Only the parent item with ID 'P1'

C. All items with ParentID 'P1' including parent and children

D. No items, syntax error in query

Solution

1. Step 1: Understand the query condition

   The query filters items where partition key ParentID equals 'P1'.

2. Step 2: Recall hierarchical data structure

   All items with ParentID 'P1' include the parent and its children because they share the same partition key.

3. Final Answer:

   All items with ParentID 'P1' including parent and children -> Option C

4. Quick Check:

   Query by ParentID returns parent + children [OK]

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

Common Mistakes:

• Thinking only parent is returned
• Confusing sort key with partition key
• Assuming syntax error without cause

4. You wrote a DynamoDB query to get all children of a parent using KeyConditionExpression: ParentID = :pid AND ChildID = :cid. It returns only one child instead of all children. What is the mistake?

medium

A. Using '=' on ChildID filters to one child only

B. ParentID should be in filter expression, not key condition

C. Missing a sort key in the table schema

D. ChildID cannot be used in KeyConditionExpression

Solution

1. Step 1: Analyze the key condition

   The condition ChildID = :cid restricts results to one specific child.

2. Step 2: Understand how to get all children

   To get all children, use a range operator like begins_with or omit ChildID condition.

3. Final Answer:

   Using '=' on ChildID filters to one child only -> Option A

4. Quick Check:

   Equals on sort key limits to one item [OK]

Hint: Use range operators, not '=' on sort key for multiple children [OK]

Common Mistakes:

• Thinking ParentID should be filter, not key condition
• Assuming ChildID can't be in key condition
• Ignoring sort key usage in queries

5. You want to model a company hierarchy in DynamoDB where each employee can have multiple subordinates. Which key design best supports efficient queries for all subordinates of a manager?

hard

A. Partition key: EmployeeID, Sort key: Timestamp

B. Partition key: EmployeeID, Sort key: ManagerID

C. Partition key: DepartmentID, Sort key: EmployeeID

D. Partition key: ManagerID, Sort key: EmployeeID

Solution

1. Step 1: Identify parent-child relationship

   Manager is the parent; employees are children (subordinates).

2. Step 2: Choose keys to group subordinates

   Using ManagerID as partition key groups all subordinates under one manager.

3. Step 3: Use EmployeeID as sort key

   Sort key EmployeeID uniquely identifies each subordinate under the manager.

4. Final Answer:

   Partition key: ManagerID, Sort key: EmployeeID -> Option D

5. Quick Check:

   Parent key = ManagerID groups subordinates [OK]

Hint: Partition by parent (manager) to group children (employees) [OK]

Common Mistakes:

• Using EmployeeID as partition key breaks grouping
• Using DepartmentID ignores manager-subordinate relation
• Using timestamp unrelated to hierarchy