A globally replicated municipal settings table holds feature flags for kiosk apps that can tolerate brief staleness. Which DynamoDB read consistency choice is appropriate by default?
Select an answer to reveal the explanation.
Short Explanation
Kiosk flags that can be a moment behind don’t need a strongly consistent hammer every poll. Eventual consistency is cheaper and faster when brief staleness is fine.
Full Explanation
Eventually consistent reads are the DynamoDB default and are appropriate when applications tolerate short replication lag, improving latency and cost. Mandatory strong consistency or transactions for every tolerant read adds overhead without SLO benefit; ad-hoc S3 copies are not a substitute for the settings table’s consistency model.