DynamoDB Global Secondary Indexes Practice Test 2026 | Exam

When designing a Global Secondary Index (GSI) in DynamoDB to support efficient "starts-with" queries on a string attribute, which projection type offers the most flexibility for subsequent client-side filtering or aggregation if the GSI's projected attributes are insufficient?

A common challenge with GSIs is the potential for "hot partitions" if the GSI's partition key is heavily skewed. The course emphasizes a pattern to mitigate this for time-series dat

Consider a scenario where you need to query for items based on a combination of two attributes, `category` and `creation_date`, where `category` is a broad filter and `creation_date` is a more specific, often time-range, filter. You're considering a GSI. What is the optimal design for the GSI's partition key (PK) and sort key (SK) to efficiently support queries like "all items in category 'X' created between date Y and date Z"?