Bird
0
0

You configured auto-scaling but notice your table never scales up despite high traffic. Which is a likely cause?

medium📝 Debug Q6 of 15
DynamoDB - Cost Optimization and Monitoring
You configured auto-scaling but notice your table never scales up despite high traffic. Which is a likely cause?
ATable has no primary key
BMinCapacity is higher than MaxCapacity
CAuto-scaling is disabled in AWS Console
DTargetValue is set too high
Step-by-Step Solution
Solution:
  1. Step 1: Check TargetValue effect

    If TargetValue is very high, scaling triggers only at very high usage.
  2. Step 2: Understand impact on scaling

    High TargetValue delays scaling up even if traffic is high.
  3. Final Answer:

    TargetValue is set too high -> Option D
  4. Quick Check:

    High TargetValue delays scaling = A [OK]
Quick Trick: Set TargetValue reasonably to trigger scaling [OK]
Common Mistakes:
MISTAKES
  • Confusing MinCapacity and MaxCapacity order
  • Assuming auto-scaling disables itself
  • Thinking primary key affects scaling triggers

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More DynamoDB Quizzes