When Scan is acceptable in DynamoDB - Mini Project: Build & Apply

When Scan is Acceptable in DynamoDB

📖 Scenario: You are managing a small DynamoDB table that stores information about books in a local library. The table is small and you want to understand when it is okay to use a Scan operation instead of a Query.

🎯 Goal: Build a simple DynamoDB setup and write a Scan operation that is acceptable because the table is small and you want to retrieve all items.

📋 What You'll Learn

Create a DynamoDB table data structure with exactly 3 book items

Add a variable to hold the table name

Write a Scan operation to retrieve all items from the table

Add a final configuration to limit the scan to 3 items

💡 Why This Matters

🌍 Real World

In small DynamoDB tables or during development, using Scan to get all items is acceptable because the data size is small and performance impact is minimal.

💼 Career

Understanding when Scan is acceptable helps database developers and cloud engineers optimize DynamoDB usage and avoid costly or slow operations in production.

1

Create a DynamoDB table data structure

Create a variable called books_table that is a list of dictionaries. Add exactly these 3 items with keys BookID, Title, and Author: {'BookID': '1', 'Title': 'The Hobbit', 'Author': 'J.R.R. Tolkien'}, {'BookID': '2', 'Title': '1984', 'Author': 'George Orwell'}, {'BookID': '3', 'Title': 'To Kill a Mockingbird', 'Author': 'Harper Lee'}.

DynamoDB

# Create the books_table list with 3 book dictionaries
# Your code here

Hint

Use a list with three dictionaries exactly as shown.

2

Add a variable for the table name

Create a variable called table_name and set it to the string 'LibraryBooks'.

DynamoDB

books_table = [
    {'BookID': '1', 'Title': 'The Hobbit', 'Author': 'J.R.R. Tolkien'},
    {'BookID': '2', 'Title': '1984', 'Author': 'George Orwell'},
    {'BookID': '3', 'Title': 'To Kill a Mockingbird', 'Author': 'Harper Lee'}
]

# Create the table_name variable
# Your code here

Hint

Set the variable table_name to the exact string 'LibraryBooks'.

3

Write a Scan operation to retrieve all items

Create a variable called scan_result and set it to a dictionary with a key Items whose value is the books_table list. This simulates scanning the entire table to get all items.

DynamoDB

books_table = [
    {'BookID': '1', 'Title': 'The Hobbit', 'Author': 'J.R.R. Tolkien'},
    {'BookID': '2', 'Title': '1984', 'Author': 'George Orwell'},
    {'BookID': '3', 'Title': 'To Kill a Mockingbird', 'Author': 'Harper Lee'}
]

table_name = 'LibraryBooks'

# Create scan_result dictionary with Items key set to books_table
# Your code here

Hint

Set scan_result to a dictionary with key 'Items' and value books_table.

4

Limit the Scan to 3 items

Add a variable called limit and set it to the number 3. Then add this limit as a key-value pair in the scan_result dictionary with key Limit.

DynamoDB

books_table = [
    {'BookID': '1', 'Title': 'The Hobbit', 'Author': 'J.R.R. Tolkien'},
    {'BookID': '2', 'Title': '1984', 'Author': 'George Orwell'},
    {'BookID': '3', 'Title': 'To Kill a Mockingbird', 'Author': 'Harper Lee'}
]

table_name = 'LibraryBooks'

scan_result = {'Items': books_table}

# Create limit variable and add it to scan_result dictionary
# Your code here

Hint

Set limit to 3 and add it to scan_result with key 'Limit'.

Practice

1. Which situation is best suited for using a Scan operation in DynamoDB?

easy

A. When you want to update an item quickly.

B. When you want to retrieve a single item by its primary key.

C. When you need to read all items from a small table.

D. When you want to delete an item by its key.

Solution

1. Step 1: Understand Scan operation purpose

   Scan reads every item in the table, which is simple but slow for large tables.

2. Step 2: Match Scan use case

   Scan is acceptable when the table is small and you need all data, not a specific item by key.

3. Final Answer:

   When you need to read all items from a small table. -> Option C

4. Quick Check:

   Scan = small table full read [OK]

Hint: Use Scan only for small tables or full data needs [OK]

Common Mistakes:

• Using Scan to get a single item by key
• Using Scan for updates or deletes
• Ignoring performance impact on large tables

2. Which of the following is the correct syntax to perform a Scan operation with a filter expression in DynamoDB?

easy

A. Scan(TableName='Users', ConditionExpression='Age > :age')

B. Scan(TableName='Users', KeyConditionExpression='Age > :age', ExpressionAttributeValues={':age': 30})

C. Scan(TableName='Users', Filter='Age > 30')

D. Scan(TableName='Users', FilterExpression='Age > :age', ExpressionAttributeValues={':age': 30})

Solution

1. Step 1: Identify correct Scan parameters

   Scan uses FilterExpression to filter results after scanning all items.

2. Step 2: Check syntax correctness

   Scan(TableName='Users', FilterExpression='Age > :age', ExpressionAttributeValues={':age': 30}) uses FilterExpression and ExpressionAttributeValues correctly for filtering.

3. Final Answer:

   Scan(TableName='Users', FilterExpression='Age > :age', ExpressionAttributeValues={':age': 30}) -> Option D

4. Quick Check:

   FilterExpression syntax = Scan(TableName='Users', FilterExpression='Age > :age', ExpressionAttributeValues={':age': 30}) [OK]

Hint: FilterExpression filters after Scan, not KeyConditionExpression [OK]

Common Mistakes:

• Using KeyConditionExpression with Scan
• Using wrong parameter names like Filter or ConditionExpression
• Not providing ExpressionAttributeValues for placeholders

3. Given a DynamoDB table 'Products' with 3 items: {"ID":1, "Category":"Book"}, {"ID":2, "Category":"Toy"}, {"ID":3, "Category":"Book"}, what will be the result of this Scan operation?

Scan(TableName='Products', FilterExpression='Category = :cat', ExpressionAttributeValues={':cat': 'Book'})

medium

A. [{"ID":1, "Category":"Book"}, {"ID":3, "Category":"Book"}]

B. [{"ID":2, "Category":"Toy"}]

C. [{"ID":1, "Category":"Book"}, {"ID":2, "Category":"Toy"}, {"ID":3, "Category":"Book"}]

D. []

Solution

1. Step 1: Understand Scan with FilterExpression

   Scan reads all items, then returns only those matching the filter Category = 'Book'.

2. Step 2: Apply filter to items

   Items with Category 'Book' are ID 1 and ID 3, so only these are returned.

3. Final Answer:

   [{"ID":1, "Category":"Book"}, {"ID":3, "Category":"Book"}] -> Option A

4. Quick Check:

   Filter returns matching items only [OK]

Hint: Scan returns all, filter narrows results after [OK]

Common Mistakes:

• Expecting Scan to return only filtered items without FilterExpression
• Confusing Scan with Query operation
• Ignoring that Scan reads all items first

4. You wrote this Scan code but it returns all items without filtering:

Scan(TableName='Orders', FilterExpression='Status = :s')

What is the most likely error?

medium

A. Missing ExpressionAttributeValues for ':s'.

B. Using FilterExpression instead of KeyConditionExpression.

C. Scan does not support FilterExpression.

D. Table name is incorrect.

Solution

1. Step 1: Check FilterExpression usage

   FilterExpression uses placeholders like ':s' which must be defined in ExpressionAttributeValues.

2. Step 2: Identify missing ExpressionAttributeValues

   Code lacks ExpressionAttributeValues, so filter cannot apply and returns all items.

3. Final Answer:

   Missing ExpressionAttributeValues for ':s'. -> Option A

4. Quick Check:

   Filter needs ExpressionAttributeValues [OK]

Hint: Always provide ExpressionAttributeValues for FilterExpression [OK]

Common Mistakes:

• Confusing FilterExpression with KeyConditionExpression
• Forgetting ExpressionAttributeValues
• Assuming Scan ignores missing values silently

5. You have a large DynamoDB table with millions of items but no suitable key for your query. You need to find all items where Status = 'Active'. Which approach is best?

hard

A. Use Scan with FilterExpression 'Status = :status' and paginate results.

B. Create a Global Secondary Index on 'Status' and use Query.

C. Use Query with KeyConditionExpression on 'Status'.

D. Use Scan without any filter to get all items.

Solution

1. Step 1: Understand limitations of Scan on large tables

   Scan reads all items and is slow and costly on large tables, even with filters.

2. Step 2: Use Global Secondary Index (GSI) for efficient queries

   Creating a GSI on 'Status' allows Query operation, which is fast and efficient for filtering by 'Status'.

3. Final Answer:

   Create a Global Secondary Index on 'Status' and use Query. -> Option B

4. Quick Check:

   GSI + Query = efficient large table filter [OK]

Hint: Use GSI for filtering large tables, not Scan [OK]

Common Mistakes:

• Using Scan on large tables causing slow performance
• Trying Query without suitable key or index
• Ignoring cost and speed implications