A developer hosts a lightweight web API on an Azure App Service web app that currently runs on the Free () pricing tier. The API is experiencing minor CPU spikes due to an increase in user requests. The developer wants to configure manual scale-out to run the web app on instances to distribute the load. Which action should the developer perform first?
- Scale up the App Service plan to the Basic () pricing tier or higher.Cevap
- BConfigure the Instance count setting to in the scale-out settings of the Azure portal while remaining on the Free () tier.
- CConfigure an Azure Monitor autoscale rule to increase the instance count to when CPU usage exceeds .
- DCreate a second App Service plan in the same region on the Free () tier and bind the web app to both plans.
Cevap
Scale up the App Service plan to the Basic () pricing tier or higher.
Scaling up the App Service plan to the Basic () tier or higher is correct because the Free () tier only supports a single instance. The Basic () tier is the minimum tier that supports manual scale-out (up to instances).
Adım Adım Çözüm
Anahtar Kavram
Azure App Service scaling capabilities are restricted by the pricing tier. The Free () and Shared () tiers do not support scaling out. Upgrading (scaling up) to the Basic () tier is the minimum requirement to enable manual scale-out.