Bird
Raised Fist0
DynamoDBquery~30 mins

Querying GSI in DynamoDB - Mini Project: Build & Apply

Choose your learning style10 modes available
Querying a Global Secondary Index (GSI) in DynamoDB
📖 Scenario: You are managing a DynamoDB table that stores information about books in a library. Each book has a unique BookID as the primary key. You want to quickly find books by their Author using a Global Secondary Index (GSI).
🎯 Goal: Build a DynamoDB query to retrieve all books by a specific author using the GSI named AuthorIndex.
📋 What You'll Learn
Create a DynamoDB table named Books with BookID as the primary key.
Create a GSI named AuthorIndex with Author as the partition key.
Write a query to find all books by the author 'J.K. Rowling' using the GSI.
Use the AWS SDK for Python (boto3) syntax for the query.
💡 Why This Matters
🌍 Real World
Many applications need to query data by attributes other than the primary key. GSIs let you do this efficiently in DynamoDB.
💼 Career
Understanding how to create and query GSIs is essential for backend developers and database engineers working with DynamoDB.
Progress0 / 4 steps
1
Create the DynamoDB table data structure
Create a dictionary called table_definition that defines a DynamoDB table named Books with BookID as the primary key of type String. Include an attribute definition for BookID of type S.
DynamoDB
Hint

Define table_definition as a dictionary with keys TableName, AttributeDefinitions, and KeySchema. Use BookID as the partition key.

2
Add the Global Secondary Index (GSI) configuration
Add a GlobalSecondaryIndexes key to the table_definition dictionary. Define one GSI named AuthorIndex with Author as the partition key of type S. Also add Author to the AttributeDefinitions list.
DynamoDB
Hint

Update table_definition to include GlobalSecondaryIndexes with the correct index name and key schema. Also add Author to AttributeDefinitions.

3
Write the query to find books by author
Create a dictionary called query_params to query the Books table using the AuthorIndex. Set the IndexName to 'AuthorIndex', the KeyConditionExpression to check Author equals 'J.K. Rowling', and use the expression attribute values accordingly.
DynamoDB
Hint

Use boto3.dynamodb.conditions.Key to build the KeyConditionExpression. Set IndexName to 'AuthorIndex' and TableName to 'Books'.

4
Complete the query call to DynamoDB
Write a line of code that calls dynamodb_client.query() with query_params and stores the result in a variable called response. Assume dynamodb_client is already created.
DynamoDB
Hint

Use dynamodb_client.query(**query_params) to perform the query and assign the result to response.

Practice

(1/5)
1. What is the main purpose of querying a Global Secondary Index (GSI) in DynamoDB?
easy
A. To delete items from the table
B. To create a backup of the table
C. To update the primary key of items
D. To find items using an alternate key without scanning the whole table

Solution

  1. Step 1: Understand what a GSI is used for

    A GSI allows querying data using a different key than the primary key.
  2. Step 2: Identify the main benefit of querying a GSI

    Querying a GSI helps find items quickly without scanning the entire table.
  3. Final Answer:

    To find items using an alternate key without scanning the whole table -> Option D
  4. Quick Check:

    Query GSI = alternate key search [OK]
Hint: GSI lets you search by different keys fast [OK]
Common Mistakes:
  • Confusing GSI query with table scan
  • Thinking GSI is for deleting or updating keys
  • Assuming GSI creates backups
2. Which of the following is the correct way to specify a GSI name in a DynamoDB query using AWS SDK?
easy
A. query({ TableName: 'MyTable', Index: 'MyGSI', KeyConditionExpression: 'GSIKey = :val', ExpressionAttributeValues: { ':val': '123' } })
B. query({ TableName: 'MyTable', KeyName: 'MyGSI', KeyConditionExpression: 'GSIKey = :val', ExpressionAttributeValues: { ':val': '123' } })
C. query({ TableName: 'MyTable', IndexName: 'MyGSI', KeyConditionExpression: 'GSIKey = :val', ExpressionAttributeValues: { ':val': '123' } })
D. query({ TableName: 'MyTable', GSIName: 'MyGSI', KeyConditionExpression: 'GSIKey = :val', ExpressionAttributeValues: { ':val': '123' } })

Solution

  1. Step 1: Recall the correct parameter name for GSI in DynamoDB query

    The correct parameter to specify a GSI is 'IndexName'.
  2. Step 2: Check the options for correct syntax

    Only query({ TableName: 'MyTable', IndexName: 'MyGSI', KeyConditionExpression: 'GSIKey = :val', ExpressionAttributeValues: { ':val': '123' } }) uses 'IndexName' correctly with other required fields.
  3. Final Answer:

    query({ TableName: 'MyTable', IndexName: 'MyGSI', KeyConditionExpression: 'GSIKey = :val', ExpressionAttributeValues: { ':val': '123' } }) -> Option C
  4. Quick Check:

    Use IndexName to specify GSI [OK]
Hint: Use 'IndexName' to specify GSI in query params [OK]
Common Mistakes:
  • Using 'KeyName' or 'GSIName' instead of 'IndexName'
  • Omitting ExpressionAttributeValues
  • Wrong key condition syntax
3. Given a DynamoDB table with a GSI named 'StatusIndex' on attribute 'status', what will the following query return?
query({ TableName: 'Orders', IndexName: 'StatusIndex', KeyConditionExpression: 'status = :s', ExpressionAttributeValues: { ':s': 'shipped' } })
medium
A. All orders with status 'shipped' using the GSI
B. All orders regardless of status
C. An error because 'status' is not the primary key
D. No results because GSI queries are not supported

Solution

  1. Step 1: Understand the query parameters

    The query uses 'StatusIndex' GSI with a key condition on 'status' = 'shipped'.
  2. Step 2: Determine what the query returns

    It returns all items where 'status' attribute equals 'shipped' using the GSI, which is designed for this attribute.
  3. Final Answer:

    All orders with status 'shipped' using the GSI -> Option A
  4. Quick Check:

    Query GSI by status = shipped returns matching items [OK]
Hint: Query GSI with key condition returns matching items [OK]
Common Mistakes:
  • Thinking GSI query returns all items
  • Assuming GSI query causes error if attribute not primary key
  • Believing GSI queries are unsupported
4. You wrote this DynamoDB query to use a GSI but get an error:
query({ TableName: 'Products', IndexName: 'CategoryIndex', KeyConditionExpression: 'category = :c', ExpressionAttributeValues: { ':c': 'books' } })

What is the most likely cause of the error?
medium
A. You cannot query a GSI in DynamoDB
B. The attribute 'category' is not the partition key of the GSI 'CategoryIndex'
C. ExpressionAttributeValues is missing a value
D. The table name 'Products' is incorrect

Solution

  1. Step 1: Understand GSI key requirements

    When querying a GSI, the KeyConditionExpression must use the GSI's partition key attribute.
  2. Step 2: Identify the error cause

    If 'category' is not the partition key of 'CategoryIndex', the query will fail with an error.
  3. Final Answer:

    The attribute 'category' is not the partition key of the GSI 'CategoryIndex' -> Option B
  4. Quick Check:

    GSI query key must be GSI partition key [OK]
Hint: GSI query key must match GSI partition key [OK]
Common Mistakes:
  • Using a non-key attribute in KeyConditionExpression
  • Assuming table name typo causes this error
  • Believing GSI queries are unsupported
5. You have a DynamoDB table 'Employees' with a GSI named 'DeptIndex' where the partition key is 'department' and sort key is 'hireDate'. You want to find all employees in 'Sales' hired after '2023-01-01'. Which query is correct?
hard
A. query({ TableName: 'Employees', IndexName: 'DeptIndex', KeyConditionExpression: 'department = :d AND hireDate > :h', ExpressionAttributeValues: { ':d': 'Sales', ':h': '2023-01-01' } })
B. query({ TableName: 'Employees', IndexName: 'DeptIndex', KeyConditionExpression: 'department = :d OR hireDate > :h', ExpressionAttributeValues: { ':d': 'Sales', ':h': '2023-01-01' } })
C. query({ TableName: 'Employees', KeyConditionExpression: 'department = :d AND hireDate > :h', ExpressionAttributeValues: { ':d': 'Sales', ':h': '2023-01-01' } })
D. query({ TableName: 'Employees', IndexName: 'DeptIndex', FilterExpression: 'department = :d AND hireDate > :h', ExpressionAttributeValues: { ':d': 'Sales', ':h': '2023-01-01' } })

Solution

  1. Step 1: Use the GSI name and correct key condition

    Query must specify 'IndexName' as 'DeptIndex' and use KeyConditionExpression with partition key and sort key conditions.
  2. Step 2: Check logical operators and expressions

    KeyConditionExpression supports 'AND' for partition key and sort key conditions; 'OR' is invalid here.
  3. Step 3: Verify FilterExpression usage

    FilterExpression filters after query; it cannot replace KeyConditionExpression for keys.
  4. Final Answer:

    query({ TableName: 'Employees', IndexName: 'DeptIndex', KeyConditionExpression: 'department = :d AND hireDate > :h', ExpressionAttributeValues: { ':d': 'Sales', ':h': '2023-01-01' } }) -> Option A
  5. Quick Check:

    Use KeyConditionExpression with AND on GSI keys [OK]
Hint: Use AND in KeyConditionExpression for partition and sort keys [OK]
Common Mistakes:
  • Using OR instead of AND in KeyConditionExpression
  • Omitting IndexName for GSI query
  • Using FilterExpression instead of KeyConditionExpression for keys
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard