Free DP-420 Exam Braindumps
Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB Questions 81–85 (page: 18)

Updated On: 16-Nov-2026
View Related Case Study

You have a container in an Azure Cosmos DB for NoSQL 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.

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

Answer(s): C,D

Explanation:

Not C: But the problem is that – when the application writes new data, the writes will always be directed to the same partition, based on whatever day it is. This results in what’s called a hot partition, where we have a bottleneck that’s going to quickly consume a great deal more of the reserved throughput you’ve provisioned for the container. Specifically, Cosmos DB evenly distributes your provisioned throughput across all the physical partitions in the container.
D: Customers will frequently view their past order history. OrderID will be used. Queries will run cross-partition
Incorrect:
Not B: 1 million a day x 2KB -> 2 GB of data/day while maximum storage across all items per (logical) partition: 20 GB


Reference:

https://www.tallan.com/blog/2019/04/30/horizontal-partitioning-in-azure-cosmos-db https://docs.microsoft.com/en-us/azure/cosmos-db/concepts-limits



View Related Case Study

You provision an Azure Cosmos DB for NoSQL container. You set the throughput to Autoscale, and the maximum request units per second (RU/s) to 20,000.
For how many RU/s will you be charged when the actual RU/s usage is zero?

  1. 0
  2. 200
  3. 2,000
  4. 4,000
  5. 10,000

Answer(s): C



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You provision Azure resources by using the following Azure Resource Manager (ARM) template.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: No
An alert is triggered when the DB key is regenerated, not when it is used.
Note: The az cosmosdb keys regenerate command regenerates an access key for a Azure Cosmos DB database account.
Box 2: No
Only an SMS action will be taken.
Emailreceivers is empty so no email action is taken.
Box 3: Yes
Yes, an alert is triggered when the DB key is regenerated.


Reference:

https://docs.microsoft.com/en-us/cli/azure/cosmosdb/keys



View Related Case Study

You have an Azure Cosmos DB database.
You plan to create a new container named container1 that will store product data and product category data and will primarily support read requests.
You need to configure a partition key for container1. The solution must meet the following requirements:
-Minimize the size of the partition.
-Minimize maintenance effort.
Which two characteristics should you prioritize? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. unique
  2. high cardinality
  3. low cardinality
  4. static

Answer(s): B,D

Explanation:

B: For all containers, your partition key should:
* Have a high cardinality. In other words, the property should have a wide range of possible values. * Etc.
D: Be a property that has a value, which doesn't change. If a property is your partition key, you can't update that property's value.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/partitioning-overview



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You are migrating a relational database to Azure Cosmos DB for NoSQL. The existing database contains the following relational tables.

The most commonly executed query for each reference table is to return all the items in the reference table.
You need to migrate all the reference tables to Azure Cosmos DB. The solution must minimize the number of containers.
How should you configure storage for the reference tables? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: 1
Number of containers
For this scenario, one container is the recommended minimum.
In Azure Cosmos DB for NoSQL, it is a best practice to consolidate small, frequently read reference datasets into a single container to optimize for cost and provisioned throughput (RU/s).
Why one container?
Small Data Volume: The six reference tables contain only 331 rows combined. This is a negligible amount of storage for a single container.
Throughput Efficiency: If you created six separate containers, you would have to provision throughput (minimum 400 RU/s) for each, leading to unnecessary costs.
Query Pattern: Since the most common query is to return all items in a table, you can easily distinguish between them in a single container by adding a type or entityName property (e.g., WHERE c.type = 'Brand').
Box 2: type
Partition key
Partition Key: You can use the type property as the Partition Key, ensuring that all items for a specific reference table reside within the same logical partition for efficient retrieval.


Reference:

https://devblogs.microsoft.com/cosmosdb/4-design-patterns-to-deal-with-large-item-sizes



Viewing page 18 of 61
Viewing questions 86 - 90 out of 296 questions


Post your Comments and Discuss Microsoft DP-420 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!