Scenario: Develop an app named App2 that will run from the retail stores and query the data in account2. App2 must be limited to a single DNS endpoint when accessing account2.

By using Azure Private Link, you can connect to an Azure Cosmos account via a private endpoint. The private endpoint is a set of private IP addresses in a subnet within your virtual network.

When you're using Private Link with an Azure Cosmos account through a direct mode connection, you can use only the TCP protocol. The HTTP protocol is not currently supported.

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 account 2 , which is strong in this case.  Strong consiste ncy ensures that every write operation is synchronously committed to every region associated with your Azure Cosmos DB account 1 .  The request level consistency level of session only applies to the read operations of App1 1 .

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.

Box 1: Yes

VM1 is on vnet1.subnet1 which has the Endpoint Status enabled.

Box 2: No

Only virtual network and their subnets added to Azure Cosmos account have access. Their peered VNets cannot access the account until the subnets within peered virtual networks are added to the account.

Box 3: No

Only virtual network and their subnets added to Azure Cosmos account have access.

Migrate

40000

According to the Azure CLI reference 1 , 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

 Azure Cosmos DB offers two different capacity modes: provisioned through put and serverless 1 . Provisioned throughput mode allows you to configure a certain amount of throughput (expressed in Request Units per second or RU/s) that is provisioned on your databases and containers.  You get billed for the amount of throughput you’ve provisioned, regardless of how many RUs were consumed 1 . Serverless mode allows you to run your database operations without having to configure any previously provisioned capacity.  You get billed for the number of RUs that were consumed by your database operations and the storage consumed by your data 1 .

To create a database that minimizes costs, you should consider the following factors:

The read and write volumes of your containers

The predictability and variability of your traffic

The latency and throughput requirements of your application

The geo-distribution and availability needs of your data

Based on these factors, one possible option that you could choose is  B. Create a provisioned throughput account. Set the throughput for coll1 to Autoscale. Set the throughput for coll2 and coll3 to Manual .

This option has the following advantages:

It allows you to handle unpredictable read and write v olumes for coll1 by using Autoscale, which automatically adjusts the provisioned throughput based on the current load 1 .

It allows you to handle predictable read and write volumes for coll2 and coll3 by using Manual, which le ts you specify a fixe d amount of provisioned throughput that meets your performance needs 1 .

It allo ws you to optimize your costs by paying only for the throughput you need for each container 1 .

It allows you to enable geo-distribution for your account if you need to r eplicate your data across multiple regions 1 .

This option also has some limitations, such as:

It may not be suitable for scenarios where all containers have intermittent or bursty traffic that is hard to forecast or has a low average-to-peak ratio 1 .

It may not be optimal for scenarios where all containers have low or sporadic traffic that does not justify provisioned capacity 1 .

It may not support availability zones or multi-master replication for your account 1 .

Depending on your specific use case and requirements, you may need to choose a different option.  F or example, you could use a serverless account if all containers have low or sporadic traffic that does not require predictable performance or geo-distribution 1 .  Alternatively, you could use a provisioned t hroughput account with Manual for all c ontainers if all containers have stable and consistent traffic that requires predictable performance or geo-distribution 1 .

Batch size: An integer that represents how many objects are being written to Cosmos DB collection in each batch. Usually, starting with the default batch size is sufficient. To further tune this value, note:

Cosmos DB limits single request's size to 2MB. The formula is "Request Size = Single Document Size * Batch Size". If you hit error saying "Request size is too large", reduce the batch size value.

The larger the batch size, the better throughput the service can achieve, while make sure you allocate enough RUs to empower your workload.