Bird
0
0

Why does a Query operation in DynamoDB generally consume fewer read capacity units than a Scan operation for the same table?

hard📝 Conceptual Q10 of 15
AWS - DynamoDB
Why does a Query operation in DynamoDB generally consume fewer read capacity units than a Scan operation for the same table?
AQuery caches results automatically; Scan does not
BQuery reads only matching items using keys; Scan reads entire table regardless of filters
CScan uses more CPU resources, increasing read units
DQuery compresses data before reading, reducing cost
Step-by-Step Solution
Solution:
  1. Step 1: Understand read capacity unit consumption

    Read capacity units depend on the amount of data read, not just returned.
  2. Step 2: Compare Query and Scan reading behavior

    Query reads only items matching the key condition; Scan reads all items regardless of filters.
  3. Final Answer:

    Query reads only matching items using keys; Scan reads entire table regardless of filters -> Option B
  4. Quick Check:

    Read units depend on data read; Query reads less [OK]
Quick Trick: Read units depend on data read, Query reads less [OK]
Common Mistakes:
  • Thinking Query caches reduce read units
  • Believing Scan uses more CPU affects read units
  • Assuming Query compresses data automatically

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes