Which strategy best reduces DynamoDB costs for an application with highly variable traffic and frequent idle periods?
hard📝 Application Q9 of 15
AWS - DynamoDB
Which strategy best reduces DynamoDB costs for an application with highly variable traffic and frequent idle periods?
AProvision maximum throughput capacity at all times to avoid throttling
BUse on-demand capacity mode to pay only for the requests made
CManually adjust provisioned capacity every hour based on traffic predictions
DUse global secondary indexes extensively to improve query speed
Step-by-Step Solution
Solution:
Step 1: Identify cost optimization needs
For unpredictable traffic with idle times, paying only for actual usage is ideal.
Step 2: Evaluate options
Use on-demand capacity mode to pay only for the requests made describes on-demand capacity mode, which charges per request and adapts automatically. Provision maximum throughput capacity at all times to avoid throttling wastes money by over-provisioning. Manually adjust provisioned capacity every hour based on traffic predictions is inefficient and error-prone. Use global secondary indexes extensively to improve query speed affects performance but not cost optimization directly.
Final Answer:
Use on-demand capacity mode to pay only for the requests made -> Option B
Quick Check:
On-demand mode optimizes cost for variable workloads [OK]
Quick Trick:On-demand mode saves cost with variable traffic [OK]
Common Mistakes:
Over-provisioning capacity unnecessarily
Relying on manual capacity adjustments
Confusing indexes with cost optimization
Master "DynamoDB" in AWS
9 interactive learning modes - each teaches the same concept differently