DP-420 Exam Dumps : Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB

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.

Scenario: Application updates in con-product frequently cause HTTP status code 429 " Too many requests " . You discover that the 429 status code relates to excessive request unit (RU) consumption during the updates.

You can use the Set-AzCosmosDBAccountRegion cmdlet to update the regions that an Azure Cosmos DB account uses. You can use this cmdlet to add a region or change the region failover order.  The cmdlet requires a resource group name, an Azure Cosmos DB account name, and a list of regions in desired failover order 1 .

For your scenario, based on the PowerShell command, you are using the Set-AzCosmosDBAccountRegion cmdlet to update the regions for an Azure Cosmos DB account named account1 that is configured for automatic failover. The command specifies two regions: West US and East US. The effect of running the command is that  the account will be configured for multi-region writes .

Multi-region writes is a feature of Azure Cosmos DB that allows you to write data to any region in your account and have it automatically replicated to all other regions. This feature provides high availability and low latency for write operations across multiple regions.  To enable multi-region writes, you need to specify at least two regions in your account and set them as write regions 2 . In your command, you are setting both West US and East US as write regions by using the -IsZoneRedundant parameter with a value of $true for both regions.