A logistics company uses Azure Cosmos DB for NoSQL to store shipment tracking data. The container is provisioned with 10,000 RU/s. The operations team notices that the Normalized RU Consumption metric is consistently at 95% for one physical partition, while other partitions are below 20%. They want to ensure the container can handle traffic spikes without throttling. What should you do?

Increase the container's provisioned throughput to 20,000 RU/s.

Change the partition key to a more evenly distributed attribute, such as shipment ID.

Create an alert on the Normalized RU Consumption metric to notify when it exceeds 90%.

Enable the Azure Monitor autoscale feature on the container.

A real-time analytics company uses Azure Cosmos DB for NoSQL. Users report that some queries are slow, but the Server Side Latency metric is low. The application is hosted in a different Azure region than the Cosmos DB account. The network team suspects that the issue is due to cross-region latency. What should you do to confirm this?

Compare the Server Side Latency metric with the end-to-end latency observed by the client.

Enable diagnostic logs and query for the duration field in DataPlaneRequests.

Check the ReplicationLatency metric.

Increase the provisioned throughput on the container.

While monitoring an Azure Cosmos DB account, you notice that the Total Requests metric shows a high count of responses with status code 429. What does this indicate?

The database account is experiencing a regional outage.

The container has reached its maximum storage size.

Requests are being throttled because the provisioned throughput is insufficient for the workload.

The client SDK is using an outdated version that is incompatible with the service.

You observe that the Server-side Latency metric for a specific query is higher than expected. What is the most likely cause?

The client SDK is using an outdated version.

The query is consuming more RUs than expected due to a missing index.

The client is located far from the Azure region.

The container has too many partitions.

Microsoft Certified:Azure Cosmos DB Developer Specialty

Domain 5Objective 1

Monitor and Troubleshoot an Azure Cosmos DB Solution DP-420 Practice Questions (Page 8)

Part of the Maintain an Azure Cosmos DB solution domain, which makes up ~22% of our current practice bank. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~9–14 in this domain), expect 3–5 from this objective — we provide 46 practice questions to prepare you well beyond it. (estimate)

46questions here

10free pages

10concepts

Questions 36–40

36application · medium
A logistics company uses Azure Cosmos DB for NoSQL to store shipment tracking data. The container is provisioned with 10,000 RU/s. The operations team notices that the Normalized RU Consumption metric is consistently at 95% for one physical partition, while other partitions are below 20%. They want to ensure the container can handle traffic spikes without throttling. What should you do?
Select an answer first
37expert · hard
A real-time analytics company uses Azure Cosmos DB for NoSQL. Users report that some queries are slow, but the Server Side Latency metric is low. The application is hosted in a different Azure region than the Cosmos DB account. The network team suspects that the issue is due to cross-region latency. What should you do to confirm this?
Select an answer first
38foundation · easy
While monitoring an Azure Cosmos DB account, you notice that the Total Requests metric shows a high count of responses with status code 429. What does this indicate?
Select an answer first
39foundation · easy
You observe that the Server-side Latency metric for a specific query is higher than expected. What is the most likely cause?
Select an answer first
40foundation · easy
You need to monitor the distribution of data size across physical partitions in an Azure Cosmos DB container. Which Azure Monitor metric should you use?
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.

Monitor and Troubleshoot an Azure Cosmos DB Solution DP-420 Practice Questions (Page 8)

Questions 36–40

While monitoring an Azure Cosmos DB account, you notice that the Total Requests metric shows a high count of responses with status code 429. What does this indicate?

You observe that the Server-side Latency metric for a specific query is higher than expected. What is the most likely cause?

You need to monitor the distribution of data size across physical partitions in an Azure Cosmos DB container. Which Azure Monitor metric should you use?

Keep studying — Maintain an Azure Cosmos DB solution