A dashboard refreshes all open cases citywide by running a full DynamoDB table Scan every minute, consuming excess capacity. What should the developer prefer?
Select an answer to reveal the explanation.
Short Explanation
A Scan every minute is reading the whole warehouse to find open boxes—Query with the right keys is walking straight to the open-cases shelf. Burning capacity on endless Scans is the expensive habit to break.
Full Explanation
DynamoDB Scan reads every item and is inefficient for frequent dashboard refresh. Designing keys and secondary indexes to support Query for open-case access patterns reduces consumed capacity and latency. Scaling capacity alone without fixing the access pattern, or abandoning the database, does not address the root issue.