DP-420 · Question #12
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…
The correct answer is A. Yes. Azure Monitor natively collects the NormalizedRUConsumption metric from Cosmos DB containers, which represents the percentage of provisioned throughput consumed. You can create a Metric Alert rule targeting this metric with a threshold (e.g., > 80%), and attach an Action Group…
Question
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 for NoSQL 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 Azure Monitor alert to trigger the function. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(39 responses)- A85% (33)
- B15% (6)
Explanation
Azure Monitor natively collects the NormalizedRUConsumption metric from Cosmos DB containers, which represents the percentage of provisioned throughput consumed. You can create a Metric Alert rule targeting this metric with a threshold (e.g., > 80%), and attach an Action Group that invokes an Azure Function via an HTTP webhook or direct function trigger. This is a fully supported, production-ready pattern for automated response to throughput pressure. The solution directly and correctly meets the stated goal.
Topics
Community Discussion
No community discussion yet for this question.