An application named PromoCampaignPortal is currently hosted on a Basic () App Service plan. During marketing campaigns, the application experiences significant memory spikes. You want to implement autoscaling to automatically handle this demand, while ensuring that the scaling behavior remains stable and does not cause rapid, repeated scaling actions (flapping).
Which two of the following actions must you perform to meet these requirements?
- Scale up the App Service plan to the Standard () pricing tier.Cevap
- Configure a scale-out rule to add an instance when memory usage exceeds and a scale-in rule to remove an instance when memory usage falls below .Cevap
- CConfigure autoscaling directly on the existing Basic () App Service plan by setting the minimum instance count to .
- DConfigure a scale-out rule to add an instance when memory usage exceeds and a scale-in rule to remove an instance when memory usage falls below .
Cevap
To configure autoscaling for the application, you must scale up the App Service plan to the Standard () pricing tier, as the Basic () tier does not support autoscale. In addition, you must set a scale-out rule to add an instance when memory usage exceeds and a scale-in rule to remove an instance when memory usage falls below to maintain a safe margin and prevent autoscale flapping.
To enable rules-based autoscaling, the App Service plan must be scaled up to at least the Standard () pricing tier, as the Basic () tier only supports manual scaling. In addition, when configuring scale-out and scale-in rules, there must be a sufficient margin between the thresholds to prevent flapping. Setting the scale-out rule to trigger when memory exceeds and the scale-in rule to trigger when memory drops below ensures that the reduction in average memory usage per instance after scaling out does not immediately trigger a scale-in action.
Adım Adım Çözüm
Anahtar Kavram
Autoscaling configuration requirements and flapping prevention in Azure App Service