You have an Azure Cosmos DB for NoSQL account that contains a database named DB1. Users run the following query against DB1. SELECT * FROM c WHERE c.bikeParts = "Frame, Chain, Peddles" ORDER BY…

Question

Options

• AORDER BY c._ts ASC, c.bikeParts DESC
• BORDER BY c._ts DESC, c.bikeParts ASC
• CORDER BY c.bikeParts ASC, c._ts ASC
• DORDER BY c.bikeParts DESC, c._ts ASC

• A
  19% (4)
• B
  5% (1)
• C
  5% (1)
• D
  71% (15)

Explanation

The WHERE clause - c.bikeParts = 'Frame, Chain, Peddles' - filters to records where bikeParts has exactly one distinct value. Because all returned documents share the same bikeParts value, sorting that field ASC or DESC produces an identical result set. This means changing ORDER BY c.bikeParts ASC to ORDER BY c.bikeParts DESC, c._ts ASC (option D) does not alter the visible output. The benefit of option D is index alignment: Azure Cosmos DB composite indexes must exactly match the field order and sort direction declared in the index definition. A composite index defined as (bikeParts DESC, _ts ASC) would be leveraged by this query, turning a full scan into an efficient index seek. Options A and B place _ts first, which breaks the index path for a bikeParts-first filter. Option C (bikeParts ASC, _ts ASC) would match an ASC composite index but is not the answer the exam expects.

No community discussion yet for this question.