Microsoft DP-420 dumps - 100% Pass Guarantee!

Correct Answer:

Box 1: Yes

The Automatic failover option allows Azure Cosmos DB to failover to the region with the highest failover priority with no user action should a region become unavailable.

Box 2: No

West Europe is used for failover. Only North Europe is writable.

To Configure multi-region set UseMultipleWriteLocations to true.

Box 3: Yes

Provisioned throughput with single write region costs $0.008/hour per 100 RU/s and provisioned throughput with multiple writable regions costs $0.016/per hour per 100 RU/s.

Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how-to-multi-master https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-cost-regions

Correct Answer: B

Explanation:

Instead configure an Azure Monitor alert to trigger the function.

You can set up alerts from the Azure Cosmos DB pane or the Azure Monitor service in the Azure portal.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/create-alerts

Correct Answer: B

Incorrect:

Not A: Request Units in Azure Cosmos DB

The minimum RU/s is here MAX(400, 240 * 1 RU/s per GB, 20,000 RU/s / 100) = MAX(400, 240, 200)=400 RU/s.

Note: Minimum throughput on container

To estimate the minimum throughput required of a container with manual throughput, find the maximum of:

400 RU/s

Current storage in GB * 1 RU/s

Highest RU/s ever provisioned on the container / 100

For example, you have a container provisioned with 400 RU/s and 0-GB storage. You increase the throughput to 50,000 RU/s and import 20 GB of data. The minimum RU/s is now MAX(400, 20 * 1 RU/s per GB, 50,000 RU/s / 100) = 500 RU/

s. Over time, the storage grows to 2000 GB. The minimum RU/s is now MAX(400, 2000 * 1 RU/s per GB, 50,000 / 100) = 2000 RU/s.

Reference: https://learn.microsoft.com/en-us/azure/cosmos-db/concepts-limits

Correct Answer: B

Explanation:

Set up a CI/CD pipeline with the Azure Cosmos DB Emulator build task in Azure DevOps

The Azure Cosmos DB Emulator provides a local environment that emulates the Azure Cosmos DB service for development purposes. The emulator allows you to develop and test your application locally, without creating an Azure

subscription or incurring any costs.

Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/tutorial-setup-ci-cd

Correct Answer: D

App1 queries the con-product and con-productVendor containers.

Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.

Scenario:

Develop an app named App1 that will run from all locations and query the data in account1.

Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.

Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated.

Incorrect Answers:

A:

Bounded staleness relates to writes. App1 only do reads.

Note: Bounded staleness is frequently chosen by globally distributed applications that expect low write latencies but require total global order guarantee. Bounded staleness is great for applications featuring group collaboration and sharing, stock ticker, publish-subscribe/queueing etc.

Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels