Explanation:
After CPU usage has reached 80 percent for 15 minutes, [2 instances] will be running.
# Once the first scale-out instance is created, the minimum time before an additional instance is created will be [5 minutes].
Azure App Service autoscaling allows web apps to automatically adjust the number of instances based on resource usage metrics such as CPU Percentage. The scaling behavior is determined by the rules and thresholds you define within the App Service plan.
From the exhibits:
* The default instance count is set to 1.
* The maximum instance count is 5.
* The scale-out rule triggers when the average CPU Percentage > 70% for 10 minutes.
* The scale-out action is to increase the instance count by 1.
* A cool down period of 5 minutes is configured (the time before another scaling action can occur).
Therefore:
1## When CPU usage reaches 80% (above the 70% threshold) for 15 minutes, the first scale-out occurs, increasing the instance count from 1 to 2.
2## After the first scale-out, Azure waits for the cooldown period (5 minutes) before evaluating scaling again
- this prevents excessive or rapid scaling (known as "flapping").
This configuration aligns with Microsoft documentation for autoscale settings in App Service Plans, ensuring stability and cost efficiency.