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 A. Metadata Requests. In Azure Cosmos DB monitoring, requests that target the database itself (rather than a container) are classified as 'Metadata Requests' in Azure Monitor. Database-level operations - such as reading database properties or listing containers - are routed through Cosmos DB's…

Optimize an Azure Cosmos DB solution

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

AMetadata Requests
BDocument Count
CData Usage
DDocument Quota

How the community answered

(22 responses)

A
73% (16)
B
14% (3)
C
5% (1)
D
9% (2)

Explanation

In Azure Cosmos DB monitoring, requests that target the database itself (rather than a container) are classified as 'Metadata Requests' in Azure Monitor. Database-level operations - such as reading database properties or listing containers - are routed through Cosmos DB's system/master partition and are tracked under this metric. When these requests exceed the provisioned RU/s at the database level, the Metadata Requests metric is the appropriate signal to configure an alert on. The other options are storage-related metrics: Document Count and Data Usage track data volume, and Document Quota reflects the storage limit - none of these reflect request unit consumption or rate-limit (HTTP 429) conditions.

Topics

#Azure Monitor#Cosmos DB Metrics#Request Units#Performance Monitoring

Community Discussion

No community discussion yet for this question.

Full DP-420 Practice