A company hosts a web application on an Azure App Service plan that currently runs on instances. You configure an autoscale rule to add instance (scale out) when the average CPU Percentage exceeds . If the CPU load is evenly distributed, the CPU percentage per instance drops to immediately after scaling out to instances. To prevent autoscale flapping, which configuration should you apply for the scale-in rule?
- Set the scale-in threshold to CPU Percentage.Cevap
- BSet the scale-in threshold to CPU Percentage.
- CSet the scale-in threshold to CPU Percentage.
- DChange the App Service plan tier to Free (F1) to enable automatic scale-in without configuring thresholds.
Cevap
Set the scale-in threshold to CPU Percentage.
Setting the scale-in threshold to CPU Percentage prevents flapping. Since the CPU percentage drops to immediately after scaling out to instances, the scale-in threshold must be lower than (e.g., ) so that the newly added instance is not immediately removed.
Adım Adım Çözüm
Anahtar Kavram
Autoscale flapping occurs when a scale action causes the metric to cross the threshold for the opposite scale action, triggering a continuous cycle of scaling up and down.