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 B. Metadata Requests. Metric Metadata Requests: Count of metadata requests. Azure Cosmos DB maintains system metadata container for each account, that allows you to enumerate collections, databases, etc., and their configurations, free of charge. Used to monitor throttles due to metadata requests…

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

AData Usage
BMetadata Requests
CRegion Removed
DRegion Added

How the community answered

(38 responses)

B
92% (35)
C
5% (2)
D
3% (1)

Explanation

Metric Metadata Requests: Count of metadata requests. Azure Cosmos DB maintains system metadata container for each account, that allows you to enumerate collections, databases, etc., and their configurations, free of charge. Used to monitor throttles due to metadata requests. Not A: Metric Data Usage: Total data usage reported at 5-minutes granularity per region. Used to monitor total data usage at container and region, minimum granularity should be 5 minutes. https://docs.microsoft.com/en-us/azure/cosmos-db/monitor-cosmos-db-reference#metrics

Topics

#Cosmos DB Monitoring#Request Units (RU/s)#Azure Monitor Alerts#Performance Optimization

Community Discussion

No community discussion yet for this question.

Full DP-420 Practice