You are designing autoscale rules for a production Azure Virtual Machine Scale Set (VMSS) hosting a microservice API. The VMSS has a minimum instance count of and a maximum instance count of .
The current autoscale settings are configured as follows:
* Scale-out rule: When the CPU Percentage (aggregated as Average) is greater than for minutes, increase the instance count by .
* Scale-in rule: When the CPU Percentage (aggregated as Average) is less than for minutes, decrease the instance count by .
You need to configure the scale-in rule to prevent autoscale flapping (repeated scale-out and scale-in cycles) under constant workload conditions.
Which two changes should you implement? (Select two.)
- Set the scale-in threshold to .Cevap
- Set the scale-in threshold to and change the scale-in action to decrease the instance count by .Cevap
- CSet the scale-in threshold to .
- DSet the scale-in threshold to and change the scale-in action to decrease the instance count by .
Cevap
To prevent autoscale flapping under constant workload, you should either set the scale-in threshold to 45% or set the scale-in threshold to 55% and change the scale-in action to decrease the instance count by 1.
To prevent autoscale flapping, the average CPU percentage after a scale-in event must remain below the scale-out threshold of 80%. When using the default configuration (decrement by 2), the most restrictive scale-in scenario occurs when scaling from 5 to 3 instances. A scale-in threshold of 45% ensures that the total workload is less than , which translates to a post-scale-in average CPU of less than on 3 instances. Alternatively, reducing the decrement to 1 instance allows a higher threshold of 55%. In this case, the most restrictive scenario is scaling from 4 to 3 instances. A threshold of 55% ensures the total workload is less than , leading to a post-scale-in average CPU of less than . Both options successfully prevent immediate scale-out.
Adım Adım Çözüm
Anahtar Kavram
Autoscale flapping occurs when a scale-in action reduces capacity to a point where the remaining instances immediately exceed the scale-out threshold, causing an endless loop. To prevent this, the scale-in threshold and scale-in step size must be configured such that the workload at the trigger point, when distributed over the reduced instance count, does not exceed the scale-out threshold.
Tahmini Süre:3m 0s