Question 3
UnclassifiedA query scans many partitions and consumes high request units. What is the best improvement direction?
Correct answer: C
Explanation
High request units usually come from scanning data that the query does not need. Redesigning the query, partition strategy, or indexing reduces unnecessary scans by narrowing the partitions and rows read, which lowers RU consumption.
Why each option is right or wrong
A. Ignore RU consumption because it never affects cost.
B. Add random delays to the user interface.
C. Redesign the query, partition strategy, or indexing to reduce unnecessary scans.
In Cosmos DB, request units are driven primarily by the amount of data the query engine must read, so a query that fans out across many partitions and performs broad scans will predictably consume a high RU charge. The appropriate fix is to change the query shape, partition key design, or indexing policy so the engine can target fewer partitions and read fewer documents; otherwise the query continues to pay for unnecessary cross-partition work.
D. Rename the database account.