Partition key distribution in DynamoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is a good partition key important in DynamoDB?

Imagine you have a large table in DynamoDB. Why does choosing a good partition key matter for performance?

A It automatically backs up the table data to another region.

B It makes the table smaller by compressing data automatically.

C It encrypts the data stored in the table for security.

D It evenly spreads data and requests across partitions to avoid hot spots.

💡 Hint

Think about how DynamoDB stores data internally and handles requests.

A good partition key ensures data and traffic are spread evenly, preventing any single partition from becoming overloaded, which keeps performance steady.

❓ query_result

intermediate

What is the output of this DynamoDB query?

Given a DynamoDB table with partition key 'UserID' and sort key 'Timestamp', what will this query return?

Query: KeyConditionExpression = UserID = 'user123' AND Timestamp BETWEEN 100 AND 200

A All items for 'user123' with Timestamp between 100 and 200 inclusive.

B All items for all users with Timestamp between 100 and 200.

C All items for 'user123' with Timestamp exactly 100 or 200 only.

D An error because BETWEEN cannot be used with sort keys.

💡 Hint

Remember how KeyConditionExpression works with partition and sort keys.

The query filters items by partition key 'user123' and returns those with sort key values between 100 and 200 inclusive.

📝 Syntax

advanced

Identify the syntax error in this DynamoDB query expression

Which option contains a syntax error in the KeyConditionExpression for DynamoDB?

KeyConditionExpression: "UserID = :uid AND Timestamp > :start AND Timestamp < :end"

A UserID = :uid AND Timestamp >= :start AND Timestamp <= :end

B UserID = :uid OR Timestamp BETWEEN :start AND :end

C UserID = :uid AND Timestamp BETWEEN :start AND :end

D UserID = :uid AND Timestamp > :start AND Timestamp < :end

💡 Hint

Check if all logical operators are allowed in KeyConditionExpression.

KeyConditionExpression only supports AND between conditions on partition and sort keys. OR is not allowed and causes syntax error.

❓ optimization

advanced

How to optimize partition key design for a high-traffic table?

You have a DynamoDB table receiving many requests for a few partition key values, causing throttling. What is the best way to optimize partition key design?

A Remove the partition key and use only a sort key.

B Use a single static partition key for all items to simplify queries.

C Add a random suffix to the partition key to spread traffic across more partitions.

D Increase the provisioned throughput without changing the key design.

💡 Hint

Think about how to avoid hot partitions by spreading requests.

Adding a random suffix to the partition key creates more partitions and balances the load, reducing throttling.

🔧 Debug

expert

Why does this DynamoDB query cause a 'ValidationException' error?

Consider this query code snippet:

KeyConditionExpression = "UserID = :uid AND OrderDate = :date"
ExpressionAttributeValues = {":uid": "user1", ":date": "2023-01-01"}

Why does this cause a ValidationException?

A Because the table does not have a sort key named 'OrderDate'.

B Because the sort key condition uses '=' instead of a range operator like BETWEEN or >.

C Because the sort key 'OrderDate' must use a range operator, '=' is not allowed.

D Because the partition key 'UserID' is missing from ExpressionAttributeValues.

💡 Hint

Check the table schema and key names carefully.

The error occurs because the table does not have a sort key named 'OrderDate'. The query references a non-existent key, causing ValidationException.