Pass the Microsoft Microsoft Certified: Azure Cosmos DB Developer Specialty DP-420 Questions and answers with CertsForce

The Cosmos DB Built-in Data  Contributor role  provides the necessary permissions to insert items into a container in an Azure Cosmos DB for NoSQL account. This role grants the  minimum required privileges  for the described task, adhering to the principle of least privilege.

If the primary write region fails, applications that write to the database must use a different connection string to continue to use the service. = NO

You do not need to use a different connection string to continue to use the service if the primary write region fails.  This is because Azure Cosmos DB supports automatic failover, which means that it will automatically switch the primary write region to another region in case of a regional o utage 2 .  The application doe s not need to change the connection string or specify the failover priority 3 .  The connection string contains a list of all the regions associated with your account, and Azure Cos mos DB will route the requests to the appropriate region based on the availability and latency 1 .

The primary Read-Only SQL Connection String and the Secondary Read-Only SQL Connection String will connect to different regions from an application running in the East US Azure region = Yes

The primary read-only SQL connection string and the secondary read-only SQL connection string will connect to different regions from an application running in the East US Azure region. This is because the primary read-only SQL connection string contains the endpoint for the East US region, which is the same as the primary write region. The secondary read-only SQL connection string contains the endpoint for the West US region, which is the additional read region. Therefore, if an application running in the East US Azure region uses these connection strings, it will connect to different regions depending on which one it chooses.

Applications can choose from which region by setting the PreferredLocations property within their connection properties = Yes

Applications can choose from which region by setting the PreferredLocations property within their connection properties.  This property allows you to specify a list of regions that you prefer to read from based on their proximity to your application 2 .  Azure Cosmos DB will route the requests to the appropriate region based on the availability and latency 1 .  You can also set the ApplicationRegion property to the region where your application is deployed, and Azure Cosmos DB will automatically populate the PreferredLocations property based on the geo-proximity from that location 1 .

Azure Monitor is a service that provides comprehensive monitoring for Azure resources, including Azure Cosmos DB. You can use Azure Monitor to collect, analyze, and alert on metrics and logs from your Azure Cosmos DB account.  You can c reate alerts for Azure Cosmos DB using Azure Monitor based on the metrics, activity log events, or Log Analytics logs on your account 1 .

For your scenario, if you want to receive an alert when requests that target the database exceed the available request units per second (RU/s), you should use the  Document Quota  metric. This metric measures the percentage of RU/s consumed by your account or container.  You can create an alert rule on this metric from the Azure portal by following these steps 2 :

In the Azure portal, select the Azure Cosmos DB account you want to monitor.

Under the Monitoring section of the sidebar, select Alerts, and then select New alert rule.

In the Create alert rule pane, fill out the Scope section by selecting your subscription name and resource type (Azure Cosmos DB accounts).

In the Condition section, select Add condition and choose Document Quota from the list of signals.

In the Configure signal logic pane, specify the threshold value and operator for your alert condition. For example, you can choose Greater than or equal to 90 as the threshold value and operator to receive an alert when your RU/s consumption reaches 90% or more of your provisioned throughput.

In the Alert rule details section, specify a name and description for your alert rule.

In the Actions section, select Add action group and choose how you want to receive notifications for your alert. For example, you can choose Email/SMS/Push/Voice as an action type and enter your email address or phone number as a receiver.

Review your alert rule settings and select Create alert rule to save it.