Soru

Zorluk: KolayScale Azure App Service Web Apps

You host a company's internal portal on an Azure App Service Web App that currently runs on a Basic (B1) App Service plan. The portal experiences performance degradation due to sudden CPU utilization spikes during lunchtime. You need to ensure the system automatically increases instances to handle these spikes and scales back down when the load decreases. Which two actions should you perform to implement this scaling configuration?

  1. Scale up the App Service plan to the Standard (S1) pricing tier.Cevap
  2. Configure an autoscale rule that uses the CPU Percentage metric to adjust the instance count.Cevap
  3. C
    Configure autoscale rules directly on the existing Basic (B1) App Service plan.
  4. D
    Configure an autoscale rule that uses the CPU Core Count metric to adjust the instance count.

Cevap

Scale up the App Service plan to the Standard (S1) pricing tier and configure an autoscale rule that uses the CPU Percentage metric to adjust the instance count.
To support autoscaling, the hosting plan must first be scaled up to at least the Standard (S1) tier. Once on a supported tier, a valid dynamic workload metric, such as CPU Percentage, must be selected to monitor the resource consumption and trigger scaling operations.

Adım Adım Çözüm

1
Evaluate the current App Service plan tier capabilities for scaling.
Identify that the Basic (B1) plan only supports manual scaling and cannot support autoscale rules.
Before configuring rules, the hosting environment must support the autoscale feature.
2
Change the App Service plan pricing tier.
Scale the plan up to the Standard (S1) pricing tier.
Standard (S1) is the entry-level tier that supports autoscale rules.
3
Define the scaling rule metric.
Create a rule based on CPU Percentage to trigger when CPU load spikes.
CPU Percentage is a dynamic load metric that directly corresponds to the performance degradation scenario.

Anahtar Kavram

Azure App Service scaling tiers and autoscale metrics
Bu soruyu puanla