DynamoDB - Cost Optimization and Monitoring
You set a DynamoDB table to provisioned mode with 5 read and 5 write capacity units, but your app suddenly needs 20 reads per second. What is the likely problem and how to fix it?
You set a DynamoDB table to provisioned mode with 5 read and 5 write capacity units, but your app suddenly needs 20 reads per second. What is the likely problem and how to fix it?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Identify the mismatch between capacity and usage
The app needs 20 reads per second but provisioned capacity is only 5 reads, causing throttling.Step 2: Determine the fix
To fix, increase provisioned capacity or switch to on-demand mode which scales automatically.Final Answer:
Provisioned capacity too low; increase capacity or switch to on-demand -> Option AQuick Check:
Low provisioned capacity causes throttling; increase or switch [OK]
Quick Trick: If usage > provisioned, increase capacity or use on-demand [OK]
Common Mistakes:
MISTAKES- Confusing on-demand and provisioned modes
- Reducing capacity when usage is high
- Ignoring throttling symptoms
Master "Cost Optimization and Monitoring" in DynamoDB
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore DynamoDB Quizzes