Microsoft Azure Architect Design (AZ-304) Practice Test

For generating alerts on Azure Cosmos DB requests, what should the alert threshold and evaluation period be?

1. 20 requests exceeding 100 within 30 minutes.

2. 20 requests exceeding 50 within 15 minutes.

3. 10 requests exceeding 100 within 10 minutes.

4. 15 requests exceeding 50 within 30 minutes.

The correct answer is: 20 requests exceeding 50 within 15 minutes.

Setting the correct threshold and evaluation period for generating alerts in Azure Cosmos DB is crucial for maintaining optimal performance and reliability. The correct choice establishes parameters that balance sensitivity to anomalies without causing unnecessary noise from alerts. In the case of the correct response, the alert threshold of 20 requests exceeding 50 within a 15-minute evaluation period indicates a proactive approach to monitoring system usage. This approach allows administrators to be alerted when the number of requests significantly deviates from the typical usage pattern, which could be indicative of performance issues or unexpected traffic spikes. The choice of 50 as the threshold is strategically placed to act as an early warning system without overwhelming the team with alerts for every minor fluctuation in request volume. Additionally, the 15-minute evaluation period strikes a balance between being reactive to immediate issues while providing enough data to determine if the spikes are consistent and warrant further investigation. In contrast, other choices either set thresholds that are too high or evaluation periods that are too long, potentially allowing issues to go unnoticed or resulting in excessive alerts for minor fluctuations in activity. The focus on a meaningful yet manageable threshold and evaluation period in the correct answer underscores the importance of a careful balance in alert configurations for effective cloud resource management.