DP-420 · Question #151
You have an Azure Cosmos DB for NoSQL account that has multiple write regions. You need to receive an alert when requests that target the database exceed the available request units per second…
The correct answer is C. Provisioned Throughput. To alert when requests to an Azure Cosmos DB database exceed its available request units per second (RU/s), you should use the Azure Monitor signal that tracks provisioned throughput metrics.
Question
You have an Azure Cosmos DB for NoSQL account that has multiple write regions. You need to receive an alert when requests that target the database exceed the available request units per second (RU/s). Which Azure Monitor signal should you use?
Options
- ARegion Removed
- BMetadata Requests
- CProvisioned Throughput
- DData Usage
How the community answered
(55 responses)- A2% (1)
- B4% (2)
- C93% (51)
- D2% (1)
Why each option
To alert when requests to an Azure Cosmos DB database exceed its available request units per second (RU/s), you should use the Azure Monitor signal that tracks provisioned throughput metrics.
`Region Removed` indicates a change in the account's region configuration, not its operational throughput.
`Metadata Requests` tracks requests for metadata operations, which are distinct from data read/write operations that consume provisioned throughput.
The `Provisioned Throughput` metric directly measures the Request Units per second (RU/s) allocated to a database or container. Alerts can be configured on this signal to trigger when the consumed RU/s approach or exceed the provisioned amount, indicating potential throttling.
`Data Usage` typically refers to storage consumption, not the rate of request units consumed.
Concept tested: Azure Cosmos DB monitoring metrics for throughput
Source: https://learn.microsoft.com/azure/cosmos-db/monitor-cosmos-db?tabs=azure-portal#metrics
Topics
Community Discussion
No community discussion yet for this question.