DynamoDB Secondary Indexes: GSI and LSI

A DynamoDB table uses customer_id as the partition key. Frequent queries require sorting customers by order_date for each customer_id. Which type of secondary index is most suitable for this scenario?

You need to create a DynamoDB index that allows you to query your products table by category and sort the results by price. The products table uses product_id as its primary key. Which type of secondary index should you use?

Which statement accurately describes a key difference between Global Secondary Indexes (GSIs) and Local Secondary Indexes (LSIs) in DynamoDB?

A DynamoDB table named game_scores uses user_id as the partition key. You want to efficiently query and sort scores based on game_type for a specific user_id. Given the need for strong consistency, which index type is most appropriate?

You are designing a DynamoDB table to store user activity events. The table uses event_type as the partition key. You now realize the need to query events based on user_id within each event_type. You have already created 5 LSIs on the table. What is the recommended approach?

Which of the following statements is true regarding the modification of secondary indexes in DynamoDB after table creation?

A transactions table stores financial transactions with transaction_id as the primary key. There's a need to efficiently query transactions by customer_id and filter by transaction_amount. Which indexing strategy would be most effective, assuming you want the index to only contain customer_id, transaction_amount and transaction_id?

You have a DynamoDB table with millions of entries and need to perform complex queries that involve filtering and sorting on multiple non-key attributes. You anticipate high read/write traffic. What is the most important consideration when choosing between using multiple Global Secondary Indexes (GSIs) versus performing scans with filters?

When should you consider using a Global Secondary Index (GSI) over a Local Secondary Index (LSI) in DynamoDB?

A DynamoDB table has a partition key CustomerID and a sort key OrderDate. You need to frequently query the table to find all orders placed on a specific date for each customer. Which type of secondary index is most suitable, and why?

Your application needs to query a DynamoDB table based on an attribute that is not the primary key. You anticipate a high volume of read requests on this index. Which factor would be MOST important when choosing between a GSI and an LSI?

You're designing a DynamoDB table for an e-commerce application. The table stores customer orders, and you need to support queries based on both CustomerID (partition key) and OrderDate. Furthermore, you want to enable queries based on OrderStatus (e.g., 'Shipped', 'Delivered'). Which indexing strategy offers the most flexible querying options?

When creating an LSI, which of the following statements is correct regarding its partition key?

Consider a scenario where you have a DynamoDB table named Employees with EmployeeID as the partition key. You need to frequently query employees based on their Department. Which of the following approaches is MOST efficient?

You have a DynamoDB table with a high volume of write operations and frequent queries on a non-key attribute. Which secondary index characteristic is MOST important to consider for optimizing performance and minimizing costs?

Which of the following is a limitation of Local Secondary Indexes (LSIs) compared to Global Secondary Indexes (GSIs) in DynamoDB?

Which of the following scenarios is best suited for using an LSI over a GSI?

Referring to the CLI examples provided, what is the primary difference in how a GSI and LSI are created in DynamoDB?

Secondary Indexes

Global Secondary Index (GSI)

GSI Query Scope

When to Use GSI

Local Secondary Index (LSI)

LSI Use Case

LSI Limit per Table

Index Modification

GSI Partition Key

LSI Partition Key

GSI Capacity Mode

LSI Capacity Mode

GSI Consistency

LSI Consistency