Question

Difficulty: HardConfigure Azure App Services

You manage an Azure App Service web app named App1 that is hosted on a Basic (B1) App Service plan named ASP1. You need to configure App1 to automatically scale out up to a maximum of 8 instances when the average CPU utilization exceeds 80%. What should you do first?

  1. Scale up ASP1 to the Standard (S1) pricing tier.Answer
  2. B
    Configure an autoscale setting for ASP1 based on CPU utilization.
  3. C
    Increase the manual scale instance count of ASP1 to 8.
  4. D
    Scale up ASP1 to the Shared (D1) pricing tier.

Answer

Scale up ASP1 to the Standard (S1) pricing tier.
Scaling up the App Service plan to the Standard (S1) pricing tier is required because the current Basic (B1) tier does not support autoscaling and is restricted to a maximum of 3 instances under manual scaling. The Standard tier is the lowest-cost tier that supports autoscale rules and up to 10 instances, making it the correct first action.

Step-by-Step Solution

1
Analyze the current tier capabilities.
The web app is hosted on a Basic (B1) App Service plan, which is limited to manual scaling up to 3 instances.
To determine if the current plan can meet the requirements of autoscaling and scaling up to 8 instances.
2
Determine the requirements for autoscaling and instance count.
The requirements are: 1) automatic scaling based on CPU, and 2) a maximum instance count of 8.
To evaluate which App Service pricing tiers support these specific configurations.
3
Select the lowest-cost tier that meets all requirements.
The Standard (S1) tier supports autoscale and up to 10 instances, while Basic (B1) and Shared (D1) do not.
To satisfy the scaling needs at the minimum possible cost.

Key Concept

App Service Plan scaling tiers and resource limits
Rate this question