An administrator is configuring autoscale rules for an Azure Virtual Machine Scale Set (VMSS) named `vmss-backend`. The scale-out rule is configured to add `` instances when the average CPU utilization exceeds ``. The administrator wants to configure a scale-in rule that decreases the instance count while preventing instance thrashing (continuous launching and terminating of VMs).
Which CPU utilization threshold should the administrator set for the scale-in rule?
- A scale-in threshold of `` average CPU utilizationCevap
- BA scale-in threshold of `` average CPU utilization
- CA scale-in threshold of `` average CPU utilization
- DA scale-in threshold of `` average CPU utilization
Cevap
A scale-in threshold of `` average CPU utilization
The correct answer is the option specifying a scale-in threshold of `` average CPU utilization. In autoscale configurations, there must be a significant gap between the scale-out threshold and the scale-in threshold. When an instance is removed (scale-in), the workload is distributed among fewer virtual machines, which increases the average CPU utilization on those remaining. If the scale-in threshold is too close to the scale-out threshold, this sudden increase in average CPU usage will immediately trigger a scale-out event, causing continuous scaling cycles (thrashing). A low threshold like `` prevents this.
Adım Adım Çözüm
Anahtar Kavram
Avoiding instance thrashing in Virtual Machine Scale Sets by setting a sufficient margin between scale-out and scale-in thresholds.
Tahmini Süre:45s