A civic events app sees unpredictable traffic spikes, while a meter-reading API has steady, well-known load. How should DynamoDB capacity modes be chosen for cost?
Select an answer to reveal the explanation.
Short Explanation
Wild festival-app traffic loves on-demand DynamoDB; a boring steady meter API often wins with provisioned plus auto scaling. Match the mode to the shape of the load, not one dogma for city hall.
Full Explanation
DynamoDB on-demand fits unpredictable or spiky workloads by billing per request. Provisioned capacity with auto scaling is often more economical for steady, forecastable throughput. Architects should select per access pattern. Instance store is ephemeral and unsuitable as the system of record.