Explanation:
Box 1 =Write and replicate data to every region synchronously
This is because the write concern is mapped to the default consistency level configured on your Azure Cosmos DB account2, which is strong in this case. Strong consistency ensures that every write operation is synchronously committed to every region associated with your Azure Cosmos DB account1. The request level consistency level of session only applies to the read operations of App11.
Box 2:That has the lowest estimated latency to the client
This is because the read operations of App1 will use the session consistency level that is specified in the request options. Session consistency is a client-centric consistency model that guarantees monotonic reads, monotonic writes, and read-your-own-writes within a session. A session is scoped to a client connection or a stored procedure execution. Session consistency allows clients to read from any region that has the lowest latency to the client.

Explanation:
Migrate
40000
According to the Azure CLI reference1, you need to use the az cosmosdb sql database throughput migrate command to migrate the throughput of the SQL database between autoscale and manually provisioned. You also need to use the --throughput-type parameter to specify the type of throughput to migrate to, and the --max-throughput parameter to specify the maximum throughput resource can scale to (RU
/s).
To complete the CLI statements, you should replace the missing values with:
* --throughput-type autoscale
* --max-throughput 40000
The final command should look like this:
az cosmosdb sql database throughput migrate \
--account-name account1 \
--name db1 \
--resource-group rg1 \
--throughput-type autoscale \
--max-throughput 40000

Explanation:

Box 1: ORDER BY c.name DESC, c.age DESC
Queries that have an ORDER BY clause with two or more properties require a composite index.
The following considerations are used when using composite indexes for queries with an ORDER BY clause with two or more properties:
If the composite index paths do not match the sequence of the properties in the ORDER BY clause, then the composite index can't support the query.
The order of composite index paths (ascending or descending) should also match the order in the ORDER BY clause.
The composite index also supports an ORDER BY clause with the opposite order on all paths.
Box 2: At the same time as the item creation
Azure Cosmos DB supports two indexing modes:
Consistent: The index is updated synchronously as you create, update or delete items. This means that the consistency of your read queries will be the consistency configured for the account.
None: Indexing is disabled on the container.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/index-policy

Explanation:

Box 1: No
An alert is triggered when the DB key is regenerated, not when it is used.
Note: The az cosmosdb keys regenerate command regenerates an access key for a Azure Cosmos DB database account.
Box 2: No
Only an SMS action will be taken.
Emailreceivers is empty so no email action is taken.
Box 3: Yes
Yes, an alert is triggered when the DB key is regenerated.
Reference: https://docs.microsoft.com/en-us/cli/azure/cosmosdb/keys