A query with ORDER BY on two properties fails asking for a composite index. Why?
- A Range indexes cover single properties only; multi-property ORDER BY needs a composite index (correct answer)
- B Composite indexes are required for all queries
- C The container lacks a partition key
- D ORDER BY is unsupported
Shortcut: The default policy creates range indexes per path, which serve single-property ordering. Multi-property ORDER BY requires an explicitly defined composite index in the matching order and direction.