[Solved] You have a DynamoDB table with 10,000 items. You run a Query operation specifying a... How does the Query operation's performance compare to a Scan operation that filters for the same 100 items? | AWS

AWS - DynamoDB

You have a DynamoDB table with 10,000 items. You run a Query operation specifying a partition key that matches 100 items. How does the Query operation's performance compare to a Scan operation that filters for the same 100 items?

AScan reads only the matching 100 items, Query reads all 10,000 items

BQuery reads all 10,000 items but returns only 100, Scan reads 100 items

CBoth Query and Scan read all 10,000 items internally

DQuery reads only the matching 100 items, while Scan reads all 10,000 items

Step-by-Step Solution

Solution:

Step 1: Understand Query operation
Query uses the partition key to directly access matching items, reading only those items.
Step 2: Understand Scan operation
Scan reads every item in the table and then applies filters, so it reads all 10,000 items.
Final Answer:
Query reads only the matching 100 items, while Scan reads all 10,000 items -> Option D
Quick Check:
Query is more efficient by reading fewer items [OK]

Quick Trick: Query reads only matching keys; Scan reads entire table [OK]

Common Mistakes:

MISTAKES

Assuming Scan reads fewer items due to filters
Believing Query reads entire table
Confusing filter application with read count

Master "DynamoDB" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More AWS Quizzes

How does the Query operation's performance compare to a Scan operation that filters for the same 100 items?

Step 1: Understand Query operation

Step 2: Understand Scan operation

Final Answer:

Quick Check:

Want More Practice?