In Azure App Service, autoscale rules automatically adjust the number of running instances based on performance metrics such as CPU, memory, or custom metrics. The configuration shown uses the Memory Percentage metric with a threshold of 70%, meaning that if average memory utilization exceeds 70% for 15 minutes, Azure will trigger a scale-out action.
From the exhibit, the rule specifies:
* Metric threshold: Greater than 70%
* Duration: 15 minutes
* Action: Increase count by 1 instance
* Cool down: 5 minutes
* Maximum instance limit: 5
App1 currently has 2 running instances.
If App1 maintains 80% memory utilization for 30 minutes, the autoscale mechanism will trigger the scale-out action after each qualifying 15-minute window, adding 1 instance every 5-minute cooldown period until the maximum instance limit (5) is reached.
Therefore, the progression would be:
* Start: 2 instances
* After first 15 minutes: +1 instance # 3 total
* After next 5-minute cooldown and continuing high memory # +1 instance # 4 total
* After another cycle # +1 instance # 5 total
Since the rule continues to trigger until the maximum (5) is reached, and the memory usage remains above the threshold, the maximum number of instances that App1 will scale to during the 30-minute period is 5.