Local Secondary Index (LSI) concept in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Local Secondary Index (LSI) with a sort key.

DynamoDB

LocalSecondaryIndexes: [{
  IndexName: 'LSI1',
  KeySchema: [
    { AttributeName: 'UserId', KeyType: 'HASH' },
    { AttributeName: [1], KeyType: 'RANGE' }
  ],
  Projection: { ProjectionType: 'ALL' }
}]

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

AEmail

BUserId

CTimestamp

DStatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same attribute 'UserId' for both partition and sort key.

Choosing an attribute not defined in the table schema.

The sort key for an LSI must be different from the partition key. 'Timestamp' is commonly used as a sort key.

2fill in blank

medium

Complete the query to use the LSI by specifying the index name.

DynamoDB

const params = {
  TableName: 'Orders',
  IndexName: [1],
  KeyConditionExpression: 'UserId = :uid and Timestamp > :ts',
  ExpressionAttributeValues: {
    ':uid': 'user123',
    ':ts': 1609459200
  }
};

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

ADefaultIndex

BLSI1

CGSI1

DPrimaryIndex

Attempts:

3 left

💡 Hint

Common Mistakes

Using the primary index name or a Global Secondary Index name instead of the LSI name.

Omitting the 'IndexName' parameter.

To query using a Local Secondary Index, you specify its name in the 'IndexName' parameter. Here, 'LSI1' is the correct index name.

3fill in blank

hard

Fix the error in the LSI definition by choosing the correct attribute type for the sort key.

DynamoDB

AttributeDefinitions: [
  { AttributeName: 'UserId', AttributeType: 'S' },
  { AttributeName: 'Timestamp', AttributeType: [1] }
],

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

AN

BB

CS

DBOOL

Attempts:

3 left

💡 Hint

Common Mistakes

Setting 'Timestamp' as a string when it is stored as a number.

Using unsupported attribute types like 'BOOL' for keys.

The 'Timestamp' attribute is usually a number, so its type should be 'N' (Number) in DynamoDB.

4fill in blank

hard

Fill both blanks to complete the LSI query with correct KeyConditionExpression and attribute values.

DynamoDB

const params = {
  TableName: 'Orders',
  IndexName: 'LSI1',
  KeyConditionExpression: 'UserId = :uid and [1] > :ts',
  ExpressionAttributeValues: {
    ':uid': 'user123',
    [2]: 1609459200
  }
};

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

ATimestamp

B:ts

C:timestamp

D:time

Attempts:

3 left

💡 Hint

Common Mistakes

Using different placeholder names in the expression and values.

Using attribute names instead of placeholders in ExpressionAttributeValues.

The sort key attribute is 'Timestamp' and the placeholder in ExpressionAttributeValues must match ':ts' used in the KeyConditionExpression.

5fill in blank

hard

Fill all three blanks to define an LSI with correct attribute definitions, key schema, and projection type.

DynamoDB

AttributeDefinitions: [
  { AttributeName: 'UserId', AttributeType: 'S' },
  { AttributeName: [1], AttributeType: 'N' }
],
LocalSecondaryIndexes: [{
  IndexName: 'LSI1',
  KeySchema: [
    { AttributeName: 'UserId', KeyType: 'HASH' },
    { AttributeName: [2], KeyType: 'RANGE' }
  ],
  Projection: { ProjectionType: [3] }
}]

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

ATimestamp

CALL

DUserId

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between attribute definitions and key schema attribute names.

Using incorrect projection types.

The LSI uses 'Timestamp' as the sort key attribute with type 'N'. The projection type 'ALL' means all attributes are projected.

Practice

1. What is the main purpose of a Local Secondary Index (LSI) in DynamoDB?

easy

A. To store data in a separate table

B. To allow querying data with the same partition key but different sort keys

C. To create a new partition key for faster queries

D. To backup data automatically

Solution

1. Step 1: Understand LSI functionality

   LSI lets you query items with the same partition key but sorted by an alternate sort key.

2. Step 2: Compare options

   Only To allow querying data with the same partition key but different sort keys correctly describes this feature; others describe unrelated features.

3. Final Answer:

   To allow querying data with the same partition key but different sort keys -> Option B

4. Quick Check:

   LSI = alternate sort key with same partition key [OK]

Hint: LSI changes sort key, not partition key [OK]

Common Mistakes:

• Thinking LSI creates new partition keys
• Confusing LSI with Global Secondary Index
• Believing LSI stores data separately

2. Which of the following is the correct way to define a Local Secondary Index (LSI) when creating a DynamoDB table?

easy

A. Define the LSI with a different partition key than the main table

B. Define the LSI with a new partition key and no sort key

C. Define the LSI after the table is created using updateTable API

D. Define the LSI with the same partition key but a different sort key

Solution

1. Step 1: Recall LSI definition rules

   LSIs must use the same partition key as the main table but can have a different sort key.

2. Step 2: Check options

   Only Define the LSI with the same partition key but a different sort key matches this rule; others violate partition key or timing constraints.

3. Final Answer:

   Define the LSI with the same partition key but a different sort key -> Option D

4. Quick Check:

   LSI = same partition key + different sort key [OK]

Hint: LSI shares partition key, differs in sort key [OK]

Common Mistakes:

• Trying to create LSI after table creation
• Using different partition keys for LSI
• Omitting sort key in LSI definition

3. Given a DynamoDB table with partition key UserID and sort key Timestamp, and an LSI with sort key OrderStatus, what will the following query return?

Query: KeyConditionExpression = UserID = '123' AND OrderStatus = 'Pending'

medium

A. All items with OrderStatus 'Pending' regardless of UserID

B. All items with UserID '123' sorted by Timestamp

C. All items with UserID '123' and OrderStatus 'Pending' sorted by OrderStatus

D. Syntax error because OrderStatus cannot be used in KeyConditionExpression

Solution

1. Step 1: Understand query with LSI

   Query on LSI uses same partition key but different sort key (OrderStatus). The query filters UserID = '123' and OrderStatus = 'Pending'.

2. Step 2: Analyze query result

   It returns items with UserID '123' and OrderStatus 'Pending', sorted by OrderStatus.

3. Final Answer:

   All items with UserID '123' and OrderStatus 'Pending' sorted by OrderStatus -> Option C

4. Quick Check:

   Query on LSI filters by partition and LSI sort key [OK]

Hint: LSI query filters by partition key + LSI sort key [OK]

Common Mistakes:

• Assuming LSI changes partition key
• Thinking query returns all items with OrderStatus only
• Believing syntax error occurs using LSI sort key

4. You created a DynamoDB table with an LSI but your query using the LSI's sort key returns no results even though matching items exist. What is the most likely cause?

medium

A. The partition key value in the query is incorrect

B. You used the LSI's partition key instead of the main table's partition key

C. The LSI's sort key attribute is missing in some items

D. The LSI was not defined at table creation time

Solution

1. Step 1: Check LSI query requirements

   Queries on LSI require the correct partition key value; wrong partition key returns no results.

2. Step 2: Evaluate options

   The partition key value in the query is incorrect explains no results due to incorrect partition key; other options are less likely or invalid.

3. Final Answer:

   The partition key value in the query is incorrect -> Option A

4. Quick Check:

   Correct partition key needed for LSI query [OK]

Hint: Always verify partition key value in LSI queries [OK]

Common Mistakes:

• Trying to add LSI after table creation
• Ignoring missing sort key attributes
• Confusing LSI partition key with main table partition key

5. You have a DynamoDB table with partition key CustomerID and sort key OrderDate. You want to query all orders for a customer sorted by OrderStatus instead of OrderDate. How should you design the Local Secondary Index (LSI) to achieve this?

hard

A. Create an LSI with partition key CustomerID and sort key OrderStatus defined at table creation

B. Create an LSI with partition key OrderStatus and sort key OrderDate after table creation

C. Create a Global Secondary Index (GSI) with partition key CustomerID and sort key OrderStatus

D. Add OrderStatus as a new partition key in the main table

Solution

1. Step 1: Understand LSI design rules

   LSI must use the same partition key as the main table but can have a different sort key.

2. Step 2: Apply to problem

   To sort by OrderStatus for the same CustomerID, create an LSI with partition key CustomerID and sort key OrderStatus at table creation.

3. Step 3: Eliminate wrong options

   Create an LSI with partition key OrderStatus and sort key OrderDate after table creation is invalid because LSI cannot be created after table creation; Create a Global Secondary Index (GSI) with partition key CustomerID and sort key OrderStatus is about GSI, not LSI; Add OrderStatus as a new partition key in the main table changes partition key, which is not allowed.

4. Final Answer:

   Create an LSI with partition key CustomerID and sort key OrderStatus defined at table creation -> Option A

5. Quick Check:

   LSI = same partition key + new sort key at creation [OK]

Hint: LSI must be defined at table creation with same partition key [OK]

Common Mistakes:

• Trying to create LSI after table creation
• Confusing LSI with GSI
• Changing partition key in LSI