Exam DP-420 topic 2 question 5 discussion

I think is D - West US is the failoverPriority=0 right? Any change to a region with failoverPriority=0 triggers a manual failover and can only be done to an account configured for manual failover. Changes to all other regions simply changes the failover priority for an Azure Cosmos DB account. https://learn.microsoft.com/en-us/azure/cosmos-db/scripts/powershell/common/failover-priority-update

I think its worng, the answer is D Becouse just have 2 failover regions, if u flip this 2 this gona make a Manual Failover https://docs.microsoft.com/en-us/azure/cosmos-db/sql/manage-with-powershell

When you run the command Update-AzCosmosDBAccountFailoverPriority with the specified failover policy, you are changing the priority order of the regions. In this case, you are setting the East US region as the primary (read-write) region and the West US region as the secondary (read-only) region. The effect of this command is: A. The account will be unavailable to writes during the change. Changing the failover priority order involves a brief period during which write operations are unavailable. This is because the primary region is being switched, and during the transition, the account cannot accept write operations until the new primary region is fully operational.

Imagine your Azure Cosmos DB account as a bustling train station. Right now, West US is the central hub where all the trains (writes) depart from, and East US is a satellite station handling passengers (reads). By running this PowerShell command: powershell Update-AzCosmosDBAccountFailoverPriority -ResourceGroupName `rg1` -Name `account1` -FailoverPolicy @(`East US`, `West US`) You're essentially rerouting the main line to East US, making it the new central hub. Here's what happens: Effect of the Command: Manual Failover Triggered: You're updating the failover priority, placing East US above West US. Since your account is configured for automatic failover, this change initiates a manual failover to East US. The write region shifts from West US to East US. Answer: D. A manual failover will occur

A. The account will be unavailable to writes during the change: This is partially true. During the change, there might be a brief period where writes are unavailable as the system transitions the write region. However, this downtime is usually minimal. B. The provisioned throughput for account1 will increase: No, changing the failover priority does not affect the provisioned throughput. C. The account will be configured for multi-region writes: No, the command does not configure the account for multi-region writes. Multi-region writes need to be explicitly configured. D. A manual failover will occur: Yes, the command triggers a failover process by changing the priority, effectively causing a manual failover to the new region.

By changing the failover priority, you are effectively initiating a manual failover to the new primary region.

D is correct, setting failover priority 0 means it´s the new write region

It can't be D cause the account is configured for automatic failover. https://learn.microsoft.com/en-us/azure/cosmos-db/scripts/powershell/common/failover-priority-update The right option is C. The command Update-AzCosmosDBAccountFailoverPriority with the specified failover policy updates the failover priority of the Cosmos DB account. In this case, the failover policy includes both 'East US' and 'West US' regions, indicating that the account will be configured for multi-region writes. The command does not make the account unavailable for writes during the change, increase the provisioned throughput, or trigger a manual failover.

The failover occurs, but D's answer says that a manual failover occurs. In this case, the failover that occurred was a service-managed failover, not a manual failover, so D is not an answer. I also did not find the same results with answers B and C. The correct answer should be A.

It is D

Selected Answer: C

Selected Answer: C

Its A as an anwser

C. The account will be configured for multi-region writes. The Update-AzCosmosDBAccountFailoverPriority command with the -FailoverPolicy parameter updates the failover policy for the Cosmos DB account by specifying the order in which the regions are selected for failover. In this case, the command updates the failover policy for account1 to include both West US and East US regions, in that order. This means that if the primary (read-write) region in West US becomes unavailable, Cosmos DB will automatically failover to the secondary (read-only) region in East US. The command does not affect the availability of the account or the provisioned throughput. It only updates the failover policy to allow for multi-region writes in case of a failover. Option C is correct because the command enables multi-region writes in the failover policy. Options A and B are incorrect because the command does not affect the account's availability or provisioned throughput. Option D is incorrect because the command does not trigger a manual failover.

IMO its A , The Azure Cosmos DB account must be configured for manual failover for manual failover to succeed

As per exact example on the source: https://learn.microsoft.com/en-us/azure/cosmos-db/sql/manage-with-powershell#trigger-manual-failover From this website and according to A: "If you perform a manual failover operation while an asynchronous throughput scaling operation is in progress, the throughput scale-up operation will be paused. It will resume automatically when the failover operation is complete." 1. Has to be an asynchronous throughput scaling operation 2. It will continue after failover completes.

They said: "a single read-write region in West US and a read region in East US" If you flip the FailoverPolicy to "East US" you can't write because it's a read region. So i think A is a correct answer.