You are configuring an Azure Cosmos DB account for a mission-critical application. The account is multi-region and has automatic failover enabled. What is the primary purpose of automatic failover in Azure Cosmos DB?

To automatically promote a read region to become the write region if the current write region becomes unavailable

To automatically replicate data to a new region when storage usage exceeds a threshold

To automatically redirect read requests to the nearest region based on latency

To automatically balance write requests across all regions

A development team is designing a new application that will use Azure Cosmos DB. The application will be deployed in multiple Azure regions and needs to support global distribution. When should the team add additional regions to the Cosmos DB account to ensure data is distributed before the application goes live?

Only when a regional outage occurs

After the application is deployed and initial traffic is observed

Before the application goes live, during the design and provisioning phase

Only when the application requires read scaling in a new region

A retail company runs a globally distributed e-commerce application on Azure Cosmos DB for NoSQL. The account is configured with two write regions (West US and East US) and uses Session consistency. The operations team wants to ensure that if the West US region becomes unavailable, the application automatically continues to accept writes with minimal manual intervention. What should the operations team configure?

Manually fail over to East US by using the Azure portal as soon as West US is detected as unavailable.

Enable automatic failover on the account and set the failover priority order so that East US becomes the write region.

Update the application connection string to point to the East US region endpoint.

Change the consistency level to Strong so that the account can automatically fail over without data loss.

You are performing a manual failover on an Azure Cosmos DB account to change the write region. What is the primary purpose of a manual failover?

To change the consistency level of the account

To add a new region to the account

To test the application's ability to handle a regional outage

To change the write region to a different region without waiting for a failure

Microsoft Certified:Azure Cosmos DB Developer Specialty

Domain 2Objective 1

Design and Implement a Replication Strategy for Azure Cosmos DB DP-420 Practice Questions (Page 4)

Part of the Design and implement data distribution domain, which makes up ~11% of our current practice bank. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~4–7 in this domain), expect 2–4 from this objective — we provide 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

8concepts

Questions 16–20

16foundation · easy
You are configuring an Azure Cosmos DB account for a mission-critical application. The account is multi-region and has automatic failover enabled. What is the primary purpose of automatic failover in Azure Cosmos DB?
Select an answer first
17foundation · easy
A development team is designing a new application that will use Azure Cosmos DB. The application will be deployed in multiple Azure regions and needs to support global distribution. When should the team add additional regions to the Cosmos DB account to ensure data is distributed before the application goes live?
Select an answer first
18foundation · easy
An application displays a social media feed where users can tolerate slight delays in seeing new posts, but the order of posts must be preserved. Which consistency model is most appropriate for this Azure Cosmos DB scenario?
Select an answer first
19application · medium
A retail company runs a globally distributed e-commerce application on Azure Cosmos DB for NoSQL. The account is configured with two write regions (West US and East US) and uses Session consistency. The operations team wants to ensure that if the West US region becomes unavailable, the application automatically continues to accept writes with minimal manual intervention. What should the operations team configure?
Select an answer first
20foundation · easy
You are performing a manual failover on an Azure Cosmos DB account to change the write region. What is the primary purpose of a manual failover?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DP-420

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “DP-420” is a trademark of its owner, used for identification only.

Design and Implement a Replication Strategy for Azure Cosmos DB DP-420 Practice Questions (Page 4)

Questions 16–20

You are configuring an Azure Cosmos DB account for a mission-critical application. The account is multi-region and has automatic failover enabled. What is the primary purpose of automatic failover in Azure Cosmos DB?

An application displays a social media feed where users can tolerate slight delays in seeing new posts, but the order of posts must be preserved. Which consistency model is most appropriate for this Azure Cosmos DB scenario?

You are performing a manual failover on an Azure Cosmos DB account to change the write region. What is the primary purpose of a manual failover?

Keep studying — Design and implement data distribution