Microsoft DP-420 Exam With Confidence Using Practice Dumps

You can facilitate aggregate data by using Change Feed and Azure Functions, and then use it for reporting.

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

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.