What is a key limitation of Local Secondary Indexes (LSI) compared to Global Secondary Indexes (GSI)?
easy📝 Conceptual Q2 of 15
AWS - DynamoDB
What is a key limitation of Local Secondary Indexes (LSI) compared to Global Secondary Indexes (GSI)?
ALSIs allow different partition keys than the base table.
BLSIs can only be created during table creation and cannot be added later.
CLSIs consume separate read and write capacity units.
DLSIs can be created and deleted anytime without downtime.
Step-by-Step Solution
Solution:
Step 1: Recall LSI creation constraints
LSIs must be defined when the table is created and cannot be added or removed later.
Step 2: Evaluate other options
The claim that LSIs allow different partition keys is false because they share the partition key; separate capacity and anytime creation/deletion describe GSI behavior.
Final Answer:
LSIs can only be created during table creation and cannot be added later. -> Option B
Quick Check:
LSI creation = Only at table creation [OK]
Quick Trick:LSI fixed at table creation, no later changes [OK]
Common Mistakes:
MISTAKES
Assuming LSIs can be added after table creation
Confusing capacity billing between LSI and GSI
Thinking LSIs have different partition keys
Master "DynamoDB" in AWS
9 interactive learning modes - each teaches the same concept differently