Why Query is the primary read operation in DynamoDB - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to query items from a DynamoDB table using the primary key.

DynamoDB

response = table.query(KeyConditionExpression=Key('[1]').eq('123'))

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

AFilterExpression

BScanIndexForward

CUserId

DProjectionExpression

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-key attribute in KeyConditionExpression causes errors.

Confusing FilterExpression with KeyConditionExpression.

The KeyConditionExpression requires the primary key attribute name. Here, 'UserId' is the partition key used to query items.

2fill in blank

medium

Complete the code to sort query results in descending order.

DynamoDB

response = table.query(KeyConditionExpression=Key('UserId').eq('123'), [1]=False)

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

AFilterExpression

BScanIndexForward

CConsistentRead

DProjectionExpression

Attempts:

3 left

💡 Hint

Common Mistakes

Using FilterExpression to sort results.

Omitting ScanIndexForward and expecting descending order.

The ScanIndexForward parameter controls the order of query results. Setting it to False returns results in descending order.

3fill in blank

hard

Fix the error in the query to use the correct key condition syntax.

DynamoDB

response = table.query(KeyConditionExpression=Key('UserId').[1]('123'))

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

Aeq

Bbegins_with

Ccontains

Dfilter

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'filter' which is not a valid method here.

Using 'contains' or 'begins_with' incorrectly for partition key.

The eq method is used to specify equality in the key condition expression for querying by primary key.

4fill in blank

hard

Fill both blanks to query items with a partition key and sort key condition.

DynamoDB

response = table.query(KeyConditionExpression=Key('[1]').eq('123') & Key('[2]').[3]('2023-01-01'))

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

AUserId

BOrderDate

Cbegins_with

Deq

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'eq' for the sort key when a prefix match is needed.

Mixing up partition and sort key names.

The query uses the partition key 'UserId' with equality and the sort key 'OrderDate' with the begins_with function to filter items starting with a date prefix.

5fill in blank

hard

Fill all three blanks to create a query that filters results and projects specific attributes.

DynamoDB

response = table.query(KeyConditionExpression=Key('[1]').eq('123'), FilterExpression=Attr('[2]').[3]('active'), ProjectionExpression='UserId, [2]')

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

AUserId

BStatus

Ceq

Dbegins_with

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'begins_with' instead of 'eq' in FilterExpression.

Not including the filtered attribute in ProjectionExpression.

The query filters items where the 'Status' attribute equals 'active' and projects only 'UserId' and 'Status' attributes in the result.

Practice

1. Why is Query considered the primary read operation in DynamoDB?

easy

A. Because it retrieves items efficiently by using the partition key.

B. Because it scans the entire table for matching items.

C. Because it updates items faster than other operations.

D. Because it deletes items based on a condition.

Solution

1. Step 1: Understand what Query does in DynamoDB

   Query retrieves items by searching only the partition key and optionally sort key, making it efficient.

2. Step 2: Compare Query with other read operations

   Scan reads the entire table, which is slower. Query targets specific items using keys.

3. Final Answer:

   Because it retrieves items efficiently by using the partition key. -> Option A

4. Quick Check:

   Query uses partition key = C [OK]

Hint: Query uses partition key for fast reads [OK]

Common Mistakes:

• Confusing Query with Scan operation
• Thinking Query updates or deletes data
• Believing Query reads the whole table

2. Which of the following is the correct syntax to perform a Query operation in DynamoDB using the AWS SDK?

easy

A. dynamodb.query({ TableName: 'MyTable', KeyConditionExpression: 'PartitionKey = :pk', ExpressionAttributeValues: { ':pk': '123' } })

B. dynamodb.scan({ TableName: 'MyTable', FilterExpression: 'PartitionKey = :pk' })

C. dynamodb.getItem({ TableName: 'MyTable', Key: { PartitionKey: '123' } })

D. dynamodb.update({ TableName: 'MyTable', Key: { PartitionKey: '123' } })

Solution

1. Step 1: Identify the Query syntax in AWS SDK

   The Query method requires TableName, KeyConditionExpression, and ExpressionAttributeValues to specify the partition key.

2. Step 2: Eliminate other options

   Scan reads all items, getItem retrieves a single item by key, update modifies data. Only Query uses KeyConditionExpression.

3. Final Answer:

   dynamodb.query({ TableName: 'MyTable', KeyConditionExpression: 'PartitionKey = :pk', ExpressionAttributeValues: { ':pk': '123' } }) -> Option A

4. Quick Check:

   Query uses KeyConditionExpression = D [OK]

Hint: Query needs KeyConditionExpression with partition key [OK]

Common Mistakes:

• Using scan instead of query for key-based reads
• Missing ExpressionAttributeValues in query
• Confusing getItem with query syntax

3. Given a DynamoDB table with partition key UserId and sort key OrderDate, what will the following Query return?

dynamodb.query({
  TableName: 'Orders',
  KeyConditionExpression: 'UserId = :uid AND OrderDate > :date',
  ExpressionAttributeValues: { ':uid': 'user123', ':date': '2023-01-01' }
})

medium

A. An error because Query cannot filter by sort key.

B. All orders for all users placed after January 1, 2023.

C. All orders for user 'user123' regardless of date.

D. All orders for user 'user123' placed after January 1, 2023.

Solution

1. Step 1: Analyze the KeyConditionExpression

   The expression specifies UserId equals 'user123' and OrderDate greater than '2023-01-01', filtering by partition and sort key.

2. Step 2: Understand Query behavior with partition and sort keys

   Query returns items matching the partition key and applies conditions on the sort key, so only orders after the date for that user are returned.

3. Final Answer:

   All orders for user 'user123' placed after January 1, 2023. -> Option D

4. Quick Check:

   Query filters by partition and sort key = A [OK]

Hint: Query filters partition and sort keys with KeyConditionExpression [OK]

Common Mistakes:

• Thinking Query returns all users' data
• Believing Query cannot filter by sort key
• Confusing Query with Scan filtering

4. You wrote this Query but it returns no results:

dynamodb.query({
  TableName: 'Products',
  KeyConditionExpression: 'Category = :cat',
  ExpressionAttributeValues: { ':cat': 'Books' }
})

What is the likely problem?

medium

A. ExpressionAttributeValues is missing a value for ':cat'.

B. The partition key is not named 'Category', so the query fails to match items.

C. Query cannot filter by partition key, only by sort key.

D. The table name 'Products' is incorrect.

Solution

1. Step 1: Check the partition key name used in Query

   Query requires the exact partition key name in KeyConditionExpression. If 'Category' is not the partition key, no items match.

2. Step 2: Verify ExpressionAttributeValues and table name

   ExpressionAttributeValues has ':cat' defined, and table name is assumed correct, so these are not the issue.

3. Final Answer:

   The partition key is not named 'Category', so the query fails to match items. -> Option B

4. Quick Check:

   Partition key name must match = A [OK]

Hint: Always use correct partition key name in Query [OK]

Common Mistakes:

• Using attribute names that are not partition keys
• Forgetting to define ExpressionAttributeValues
• Assuming Query filters all attributes

5. You want to efficiently retrieve all orders for a user placed in 2023 from a DynamoDB table with UserId as partition key and OrderDate as sort key. Which Query approach is best?

hard

A. Use Scan with FilterExpression: 'UserId = :uid AND OrderDate BETWEEN :start AND :end'.

B. Use Query with KeyConditionExpression: 'UserId = :uid' only, then filter results in application code.

C. Use Query with KeyConditionExpression: 'UserId = :uid AND begins_with(OrderDate, :year)' and ExpressionAttributeValues for user and '2023'.

D. Use GetItem for each order separately by specifying UserId and OrderDate.

Solution

1. Step 1: Identify efficient Query usage with partition and sort keys

   Using KeyConditionExpression with partition key and a condition on sort key (begins_with) efficiently filters orders in 2023.

2. Step 2: Compare with other options

   Scan reads entire table (slow), filtering in app wastes resources, GetItem for each order is inefficient for multiple items.

3. Final Answer:

   Use Query with KeyConditionExpression: 'UserId = :uid AND begins_with(OrderDate, :year)' and ExpressionAttributeValues for user and '2023'. -> Option C

4. Quick Check:

   Query with partition and sort key prefix = B [OK]

Hint: Use Query with partition key and begins_with on sort key [OK]

Common Mistakes:

• Using Scan instead of Query for key-based reads
• Filtering in application instead of Query
• Using GetItem for multiple items