Examkin

Soru

Zorluk: OrtaScale Azure App Service Web Apps

An organization hosts a web application named `FleetTelemetryAPI` on an App Service plan that is currently configured for the Basic (B1B1) pricing tier. During peak operation hours, the application experiences CPU usage spikes that degrade performance. The administrator wants to configure autoscale rules to automatically scale out the application when CPU utilization is high, and scale it back in when demand decreases, ensuring that the configuration prevents flapping.

Which two of the following actions should you perform? (Select two.)

  1. Scale up the App Service plan to the Standard (S1S1) tier or higher.Cevap
  2. Configure a scale-out rule to increase the instance count when CPU usage exceeds 80%80\%, and a scale-in rule to decrease the instance count when CPU usage drops below 60%60\%.Cevap
  3. C
    Configure a scale-out rule to increase the instance count when CPU usage exceeds 80%80\%, and a scale-in rule to decrease the instance count when CPU usage drops below 85%85\%.
  4. D
    Configure Azure Monitor autoscale rules directly on the existing Basic (B1B1) App Service plan to scale out based on CPU usage.

Cevap

Scale up the App Service plan to the Standard (S1S1) tier or higher, and configure a scale-out rule to increase the instance count when CPU usage exceeds 80%80\%, and a scale-in rule to decrease the instance count when CPU usage drops below 60%60\%.
Scaling out (horizontal scaling) and autoscale features require at least the Standard (S1S1) tier of Azure App Service, as the Basic (B1B1) tier only supports manual scale-up/down. Additionally, to prevent autoscale flapping, the scale-in metric threshold must be sufficiently lower than the scale-out threshold so that scaling in does not immediately trigger another scale-out event.

Adım Adım Çözüm

1
Evaluate the current App Service pricing tier.
The current plan is Basic (B1B1), which does not support autoscale or horizontal scaling (scale-out).
Autoscale features require a Standard (S1S1) tier or higher.
2
Determine the scaling rule thresholds to prevent flapping.
The scale-out rule triggers when CPU usage is high (80%80\%) and the scale-in rule triggers when CPU usage is low (60%60\%) with a significant buffer in between.
If the scale-in threshold is too close to or higher than the scale-out threshold, the reduction in per-instance load after scaling out will immediately trigger a scale-in, creating a flapping loop.

Anahtar Kavram

Azure App Service Scaling Tiers and Autoscale Flapping Prevention
Bu soruyu puanla

Konular

Scale Azure App Service Web Apps

Bu konudan daha fazla soru