How can you design a DynamoDB table to efficiently support queries for recent orders by multiple customers without scanning the entire table?

hard🚀 Application Q9 of 15

DynamoDB - Access Patterns and Query Optimization

ACreate a GSI with OrderDate as PartitionKey and CustomerId as SortKey

BUse a composite primary key with CustomerId as PartitionKey and OrderDate as SortKey

CUse OrderDate as PartitionKey only

DStore all orders in one partition

Step-by-Step Solution

Solution:

Step 1: Understand query needs
Query recent orders across customers means querying by OrderDate first.
Step 2: Use GSI for alternate access
Main table keys group by CustomerId; GSI with OrderDate as PartitionKey and CustomerId as SortKey supports recent orders query efficiently.
Final Answer:
Create a GSI with OrderDate as PartitionKey and CustomerId as SortKey -> Option A
Quick Check:
GSI supports alternate query patterns efficiently [OK]

Quick Trick: Use GSI to query by different keys [OK]

Common Mistakes:

MISTAKES

Master "Access Patterns and Query Optimization" in DynamoDB

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More DynamoDB Quizzes