You are configuring an Azure Virtual Machine Scale Set (VMSS) named `vmss-processor` that processes messages from an Azure Service Bus queue. The VMSS is configured with the following parameters:
- Orchestration mode: Flexible
- Upgrade policy: Manual
- Current instance count: 4
- Scale-in policy: Default
You need to configure autoscale rules to meet the following requirements:
1. Scale out by 2 instances when the average queue depth exceeds 1,000 messages.
2. Scale in by 1 instance when the average queue depth falls below 200 messages.
3. Prevent instance thrashing (frequent, consecutive scale-out and scale-in actions).
Which of the following configurations should you apply to the autoscale rules? (Select TWO.)
- Configure the scale-out rule with a threshold of 1,000 messages and the scale-in rule with a threshold of 200 messages.Cevap
- Configure a cooldown period of 10 minutes for both the scale-out and scale-in rules.Cevap
- CConfigure the scale-in rule with a threshold of 950 messages to quickly terminate idle instances after workload spikes.
- DSet the cooldown period to 0 minutes for the scale-in rule to ensure immediate deprovisioning of instances.
Cevap
To configure the VMSS autoscale rules correctly, you should configure the scale-out threshold to 1,000 messages and the scale-in threshold to 200 messages, and configure a cooldown period of 10 minutes for both rules.
Establishing a wide gap between the scale-out threshold of 1,000 messages and the scale-in threshold of 200 messages prevents rapid fluctuations in queue depth from triggering conflicting scale actions. Additionally, setting a cooldown period of 10 minutes ensures that Azure Monitor allows the VMSS to stabilize and the queue metrics to catch up after a scale action before evaluating the rules again.
Adım Adım Çözüm
Anahtar Kavram
Virtual Machine Scale Set (VMSS) Autoscale Rules and Thrashing Prevention