Explanation:

Explanation:

Box 1: No
You set the highest, or maximum RU/s Tmax you don ' t want the system to exceed. The system automatically scales the throughput T such that 0.1* Tmax < = T < = Tmax.
In this example we have autoscaleMaxThroughput = 5000, so the minimum throughput for the container is
500 R/Us.
Box 2: No
First query: SELECT * FROM c WHERE c.EmployeeId > ' 12345 '
Here ' s a query that has a range filter on the partition key and won ' t be scoped to a single physical partition.
In order to be an in-partition query, the query must have an equality filter that includes the partition key:
SELECT * FROM c WHERE c.DeviceId > ' XMS-0001 '
Box 3: Yes
Example of In-partition query:
Consider the below query with an equality filter on DeviceId. If we run this query on a container partitioned on DeviceId, this query will filter to a single physical partition.
SELECT * FROM c WHERE c.DeviceId = ' XMS-0001 '
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-choose-offer
https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-query-container

Explanation:

Explanation:

Box 1: UseAuthentication
Need to validate users before users are allowed access to secure resources.
UseAuthentication adds the AuthenticationMiddleware to the specified IApplicationBuilder, which enables authentication capabilities.
Box 2: UseAuthorization
Need to permit users to access secure resources.
UseAuthorization adds the AuthorizationMiddleware to the specified IApplicationBuilder, which enables authorization capabilities.
Box 3: UseStaticFiles
Need to use the Export feature in the app without requiring a restart of the app.
UseStaticFiles enables static file serving for the current request path Reference:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.builder.iapplicationbuilder?view=aspnetcore-
5.0

Explanation:

Box 1: BoundedStaleness
Bounded staleness: The reads are guaranteed to honor the consistent-prefix guarantee. The reads might lag behind writes by at most " K " versions (that is, " updates " ) of an item or by " T " time interval. In other words, when you choose bounded staleness, the " staleness " can be configured in two ways:
The number of versions (K) of the item
The time interval (T) by which the reads might lag behind the writes
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/cosmos-db/manage-with-cli.md