A backend service named ReportRunner handles report generation and is deployed to an Azure App Service Web App. The App Service is currently running on the Basic (B1) tier. During peak monthly billing cycles, report generation jobs stall because of resource constraints, and you must configure autoscale to automatically add instances when CPU utilization exceeds .
Which of the following actions should you perform first to support this requirement?
- Scale up the App Service plan to the Standard (S1) tier.Cevap
- BEnable autoscale rules directly on the Basic (B1) App Service plan using the CPU Percentage metric.
- CScale out the Basic (B1) App Service plan to its maximum capacity of three instances to activate autoscale settings.
- DScale up the App Service plan to the Standard (S1) tier, and configure a scale-out rule when CPU is above and a scale-in rule when CPU is below .
Cevap
Scale up the App Service plan to the Standard (S1) tier.
Scaling up the App Service plan to the Standard (S1) tier is correct because autoscale features, including rule-based scaling on metrics such as CPU Percentage, are not available in the Basic (B1) tier. The Basic tier only supports manual scaling up to three instances. Upgrading to the Standard tier is a prerequisite for configuring autoscale.
Adım Adım Çözüm
Anahtar Kavram
App Service Plan Tiers and Autoscale Configurations