DynamoDB - Cost Optimization and Monitoring
An auto-scaling policy has MinCapacity 5 and MaxCapacity 15, but scaling never goes above 5. What is a possible error?
An auto-scaling policy has MinCapacity 5 and MaxCapacity 15, but scaling never goes above 5. What is a possible error?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand scaling limits
Min and MaxCapacity allow scaling between 5 and 15.Step 2: Identify why scaling stuck at 5
If policy is attached to wrong resource, scaling won't apply correctly.Final Answer:
Auto-scaling policy is attached to wrong resource -> Option BQuick Check:
Wrong resource attachment blocks scaling = D [OK]
Quick Trick: Attach policies to correct resource for scaling [OK]
Common Mistakes:
MISTAKES- Blaming cooldown without checking policy attachment
- Misunderstanding TargetValue as capacity number
- Assuming region mismatch causes scaling failure
Master "Cost Optimization and Monitoring" in DynamoDB
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore DynamoDB Quizzes