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

You have a container in an Azure Cosmos DB Core (SQL) API account that stores data about orders.

The following is a sample of an order document.

Documents are up to 2 KB.

You plan to receive one million orders daily.

Customers will frequently view their past order history.

You are the evaluating whether to use orderDate as the partition key.

What are two effects of using orderDate as the partition key? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

You will exceed the maximum number of partition key values
You will exceed the maximum storage per partition
There will always be a hot partition
Queries will run cross-partition

Correct answer: CD

Explanation:

CD: 1 - Mosted

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB Core (SQL) API account named account1 that uses autoscale throughput.

You need to run an Azure function when the normalized request units per second for a container in account1 exceeds a specific value.

Solution: You configure Azure Event Grid to send events to the function by using an Event Grid trigger in the function.

Does this meet the goal?

Yes
No

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

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

You have three containers in an Azure Cosmos DB Core (SQL) API account as shown in the following table.

You have the following Azure functions:

A function named Fn1 that reads the change feed of cn1
A function named Fn2 that reads the change feed of cn2
A function named Fn3 that reads the change feed of cn3

You perform the following actions:

Delete an item named item1 from cn1.
Update an item named item2 in cn2.
For an item named item3 in cn3, update the item time to live to 3,600 seconds.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.

NOTE: Each correct selection is worth one point.

Correct answer: To work with this question, an Exam Simulator is required.

Explanation:

Box 1: No -Azure Cosmos DB's change feed is a great choice as a central data store in event sourcing architectures where all data ingestion is modeled as writes (no updates or deletes).Note: The change feed does not capture deletes. If you delete an item from your container, it is also removed from the change feed. The most common method of handling this is adding a soft marker on the items that are being deleted. You can add a property called "deleted" and set it to "true" at the time of deletion. This document update will show up in the change feed. You can set a TTL on this item so that it can be automatically deleted later.Box 2: No -The _etag format is internal and you should not take dependency on it, because it can change anytime.Box 3: Yes -Change feed support in Azure Cosmos DB works by listening to an Azure Cosmos container for any changes.Reference:https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-design-patterns https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed

Box 1: No -

Azure Cosmos DB's change feed is a great choice as a central data store in event sourcing architectures where all data ingestion is modeled as writes (no updates or deletes).

Note: The change feed does not capture deletes. If you delete an item from your container, it is also removed from the change feed. The most common method of handling this is adding a soft marker on the items that are being deleted. You can add a property called "deleted" and set it to "true" at the time of deletion. This document update will show up in the change feed. You can set a TTL on this item so that it can be automatically deleted later.

Box 2: No -

The _etag format is internal and you should not take dependency on it, because it can change anytime.

Box 3: Yes -

Change feed support in Azure Cosmos DB works by listening to an Azure Cosmos container for any changes.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-design-patterns

https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed

You have a global ecommerce application that stores data in an Azure Cosmos DB Core (SQL) API account. The account is configured for multi-region writes.

You need to create a stored procedure for a custom conflict resolution policy for a new container. In the event of a conflict caused by a deletion, the deletion must always take priority.

Which parameter should you check in the stored procedure function?

isTombstone
conflictingItems
existingItem
incomingItem

Correct answer: A

Explanation:

A: 3 - Mosted

You are building an application that will store data in an Azure Cosmos DB Core (SQL) API account. The account uses the session default consistency level. The account is used by five other applications. The account has a single read-write region and 10 additional read region.

Approximately 20 percent of the items stored in the account are updated hourly.

Several users will access the new application from multiple devices.

You need to ensure that the users see the same item values consistently when they browse from the different devices.

The solution must NOT affect the other applications.

Which two actions should you perform? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Set the default consistency level to eventual
Associate a session token to the device
Use implicit session management when performing read requests
Provide a stored session token when performing read requests
Associate a session token to the user account

Correct answer: DE

Explanation:

BC: 7BD: 1DE: 13 - Mosted

You need to create a data store for a directory of small and medium-sized businesses (SMBs). The data store must meet the following requirements:

Store companies and the users employed by them. Each company will have less than 1,000 users.
Some users have data that is greater than 2 KB.
Associate each user to only one company.
Provide the ability to browse by company.
Provide the ability to browse the users by company.
Whenever a company or user profile is selected, show a details page for the company and all the related users.
Be optimized for reading data.

Which design should you implement to optimize the data store for reading data?

In a directory container, create a document for each company and a document for each user. Use the company ID as the partition key.
Create a user container that uses the user ID as the partition key and a company container that uses the company ID as the partition key. Add the company ID to each user document.
In a user container, create a document for each user. Embed the company into each user document. Use the user ID as the partition key.
In a company container, create a document for each company. Embed the users into company documents. Use the company ID as the partition key.

Correct answer: D

Explanation:

A: 11B: 13D: 20 - Mosted

You plan to store order data in an Azure Cosmos DB Core (SQL) API account. The data contains information about orders and their associated items.

You need to develop a model that supports order read operations. The solution must minimize the number of requests.

What should you do?

Create a database for orders and a database for order items.
Create a single database that contains a container for orders and a container for order items.
Create a single database that contains one container. Store orders and order items in separate documents in the container.
Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.

Correct answer: D

Explanation:

B: 1D: 11 - Mosted

You have an Azure Cosmos DB Core (SQL) API account named account1 that supports an application named App1. App1 uses the consistent prefix consistency level.

You configure account1 to use a dedicated gateway and integrated cache.

You need to ensure that App1 can use the integrated cache.

Which two actions should you perform for App1? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Change the consistency level of requests to session.
Change the account endpoint to http://account1.documents.azure.com.
Change the account endpoint to http://account1.sqlx.cosmos.azure.com.
Change the connection mode to direct.
Change the consistency level of requests to strong.

Correct answer: AC

Explanation:

AB: 1AC: 6 - MostedAD: 3

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB Core (SQL) API account named account 1 that uses autoscale throughput.

You need to run an Azure function when the normalized request units per second for a container in account1 exceeds a specific value.

Solution: You configure an application to use the change feed processor to read the change feed and you configure the application to trigger the function.

Does this meet the goal?

Yes
No

Correct answer: B

Explanation:

B: 4 - Mosted

You are designing an Azure Cosmos DB Core (SQL) API solution to store data from IoT devices. Writes from the devices will be occur every second.

The following is a sample of the data.

You need to select a partition key that meets the following requirements for writes:

Minimizes the partition skew
Avoids capacity limits
Avoids hot partitions

What should you do?

Create a new synthetic key that contains deviceId and timestamp
Use timestamp as the partition key
Use deviceManufacturer as the partition key
Use sensor1Value as the partition key

Correct answer: A

Explanation:

A: 5 - Mosted

Vendor:	Microsoft
Exam Code:	DP-420
Exam Name:	Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB
Date:	Dec 28, 2025
File Size:	7 MB

Download Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB.DP-420.ExamTopics.2025-12-28.147q.vcex

How to open VCEX files?

Demo Questions

Question 1

Question 2

Question 3

Question 4

Question 5

Question 6

Question 7

Question 8

Question 9

Question 10

ProfExam at a 20% markdown