Examkin

Question

Difficulty: EasyScale Azure App Service Web Apps

A startup hosts a promotional website on an Azure App Service Web App that is currently running on the Shared (D1D1) pricing tier. The company expects a temporary increase in web traffic during an upcoming product launch and wants to scale out the application to multiple instances to distribute the load. What must you do first to enable scaling out for this App Service Web App?

  1. Scale up the App Service plan to a pricing tier that supports scale-out, such as Basic or Standard.Answer
  2. B
    Configure an autoscale rule based on CPU Percentage within the current Shared (D1D1) plan settings.
  3. C
    Increase the instance count limit of the Shared (D1D1) plan using the Azure Portal manual scale-out slider.
  4. D
    Associate the Web App with a secondary App Service plan in the Shared (D1D1) tier to distribute the load.

Answer

Scale up the App Service plan to a pricing tier that supports scale-out, such as Basic or Standard.
Scaling up the App Service plan to a tier like Basic or Standard is the correct first step. The Shared (D1D1) tier runs on shared virtual machines and does not support horizontal scaling (scaling out) to multiple instances. To increase the instance capacity, the hosting plan must first be scaled up to at least the Basic tier (which supports manual scale-out up to 33 instances) or Standard/Premium tiers (which support automated and larger scale-out options).

Step-by-Step Solution

1
Analyze the current App Service pricing tier and target scaling requirement.
The current plan is on the Shared (D1D1) tier, and the requirement is to scale out (increase the number of VM instances).
Different Azure App Service pricing tiers support different scaling capabilities.
2
Determine scaling limitations of the Shared tier.
The Free and Shared tiers run on shared infrastructure and do not support horizontal scaling (scaling out). Only scaling up (changing to a higher tier) is allowed.
Azure enforces pricing tier constraints where scale-out capabilities start from the Basic tier (for manual scale) and Standard tier (for autoscale).
3
Select the correct action to enable scale-out capabilities.
You must first scale up the plan to at least the Basic tier (for manual scale-out) or Standard tier (for autoscale).
Scaling up unlocks the scale-out features required to handle the traffic spike across multiple instances.

Key Concept

Azure App Service scaling constraints, specifically that Free and Shared tiers do not support scaling out (horizontal scaling) and require scaling up to at least the Basic tier to enable multiple instances.
Rate this question

Topics

Scale Azure App Service Web Apps

More questions from this topic