Explanation:

Explanation:

Explanation:
Box 1 = Range
Azure Cosmos DB supports three types of indexes: range, spatial and composite. For the query you provided, which is an equality query on a single property, the best type of index to use is range . Range index is based on an ordered tree-like structure and it is used for equality queries, range queries and checking for the presence of a property 1 . Range index also supports any string or number 2 .
Box 2 = Composite
Azure Cosmos DB supports three types of indexes: range, spatial and composite. For the query you provided, which is an order by query on two properties, the best type of index to use is composite . Composite ind ex is used for optimizing order by queries on multiple prop erties 1 . Composite index allows you to specify a list of property paths and sort orders that are used for ordering items 2 .
Box 3 = spatial
Azure Cosmos DB supports three types of indexes: range, spatial and composite. For the query you provided, which is a spatial query on a point property, the best type of index to use is spatial . Spatial index is used for querying items based on their location or proximity to a given point 1 . Spatial index supports point, polygon and linestring data types 2 .

Explanation:
New and updated orders will be added to contoso-erp.orders: Yes
The code performs bulk data ingestion from contoso-app: No
Both contoso-app and contoso-erp have Analytics store enabled: Yes
The code uses the spark.readStream method to read data from a container named orders in a database named contoso-app. The data is then filtered by a condition and written to another container named orders in a database named contoso-erp using the spark.writeStream method. The write mode is set to "append", which means that new and updated orders will be added to the destination container 1 .
The code does not perform bulk data ingestion from contoso-app, but rather stream processing. Bulk data ingestion is a process of loading large amounts of data into a data store in batches. St ream processing is a process of continuously processing data as it arrives in real-time 2 .
Both contoso-app and contoso-erp have Analytics store enabled, because they are both accessed by Spark pools using the spark.cosmos.oltp method. This method requires that the containers h ave Analytics store enabled, which is a feature that allows Spa rk pools to query data stored in Azure Cosmos DB containers using SQL APIs 3 .

Explanation:

Box 1: CompanyID
After you create a container with a unique key policy, the creation of a new or an update of an existing item resulting in a duplicate within a logical partition is prevented, as specified by the unique key constraint. The partition key combined with the unique key guarantees the uniqueness of an item within the scope of the container.
For example, consider an Azure Cosmos container with Email address as the unique key constraint and CompanyID as the partition key. When you configure the user ' s email address with a unique key, each item has a unique email address within a given CompanyID. Two items can ' t be created with duplicate email addresses and with the same partition key value.
Box 2: emailAddress
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/unique-keys