
Explanation:
Box 1: compositeIndexes
Queries that have an ORDER BY clause with two or more properties require a composite index.
You can also define a composite index to improve the performance of many equality and range queries. By default, no composite indexes are defined so you should add composite indexes as needed.
Box 2: ascending
In the scenario composite index defined as name ASC and age DESC. It is optional to specify the order. If not specified, the order is ascending.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/index-policy#composite-indexes
https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-manage-indexing-policy?tabs=dotnetv2%2Cpythonv3#composite-index-defined-for-name-asc-age-asc