Azure App Service Autoscale: Scale Out Based on CPU Usage with Cool-Down Periods
You have an Azure App Service web app that experiences fluctuating traffic. During peak hours, the CPU usage reaches 90% and response times increase. You want to automatically scale out the number of instances when CPU usage exceeds 75% and scale in when it drops below 25%. The scaling should be gradual to avoid thrashing. Which configuration should you use?
Quick Answer
The answer is to configure autoscale rules on the App Service plan scale-out setting using CPU percentage as the metric with appropriate thresholds and cool-down periods. This is correct because Azure App Service autoscale allows you to define a scale-out rule that triggers when CPU usage exceeds 75% and a scale-in rule when it drops below 25%, while cool-down periods (typically 5–10 minutes) ensure gradual scaling by preventing rapid, repeated scaling actions that cause thrashing. On the AZ-204 exam, this scenario tests your understanding of scaling policies within App Service plans, often appearing as a scenario where you must distinguish between rule-based autoscale and manual scaling or Azure Functions scale controllers. A common trap is forgetting to set cool-down periods, leading to instability, or confusing the metric source (App Service plan vs. individual app). Memory tip: think “75 out, 25 in, cool down to win” — the thresholds and a pause prevent the yo-yo effect.
⚠ Common exam trap
Many exam-takers confuse 'Always On' (which keeps the app warm) with autoscaling, or mistakenly think Azure Functions or Container Instances are drop-in replacements for App Service autoscale, ignoring the specific requirements for gradual, metric-based scaling with cool-down periods.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure autoscale rules on the App Service plan scale-out setting, using CPU percentage as the metric with appropriate thresholds and cool-down periods.
Azure App Service autoscale rules allow you to scale out (increase instance count) when CPU percentage exceeds 75% and scale in (decrease instance count) when it drops below 25%, with configurable cool-down periods (e.g., 5–10 minutes) to prevent thrashing. This directly addresses the fluctuating traffic pattern and gradual scaling requirement using the App Service plan's scale-out blade.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable 'Always On' and configure manual scale based on scheduled times.
Why it's wrong here
Manual scale on scheduled times fixes instance counts to a timetable, so it cannot react to CPU crossing 75% or 25%; autoscale rules with cool-down periods do. It is tempting when traffic patterns are predictable and known in advance, where scheduled scaling is genuinely the correct configuration.
- ✓
Configure autoscale rules on the App Service plan scale-out setting, using CPU percentage as the metric with appropriate thresholds and cool-down periods.
Why this is correct
Autoscale rules on the App Service plan add or remove instances based on CPU percentage, with thresholds of 75% out and 25% in plus cool-down periods preventing rapid oscillation. This satisfies the fluctuating-traffic and gradual-scaling constraints, since scale-out and scale-in are metric-driven rather than manual.
- ✗
Use Azure Functions with the Consumption Plan to handle the web app logic.
Why it's wrong here
Azure Functions Consumption Plan runs event-driven code and does not host the App Service web app or scale its instances on CPU; App Service autoscale rules do. It is tempting for offloading background or burst workloads, where serverless execution is genuinely the correct choice.
- ✗
Deploy the web app to Azure Container Instances and use the scale-on-CPU feature.
Why it's wrong here
Azure Container Instances lacks a native scale-on-CPU feature and does not host App Service web apps; App Service autoscale evaluates CPU percentage rules with cool-down. It is tempting for short-lived containerised tasks, where ACI's per-second billing and rapid startup are genuinely the correct fit.
Go deeper
Related to this question
About these practice questions
This AZ-204 question is part of Courseiva's 883-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
3 more ways this is tested on AZ-204
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You have an Azure App Service web app that experiences high CPU usage during peak hours. You need to scale out automatically based on CPU load. What should you configure?
medium- A.Manually increase the instance count during peak hours.
- B.Configure an autoscale rule to scale up the App Service plan.
- ✓ C.Configure an autoscale rule to scale out based on CPU percentage.
- D.Use Azure Front Door to distribute load across multiple instances.
Why C: Azure App Service autoscale rules allow you to scale out (increase instance count) based on a metric like CPU percentage. This automatically adds more instances when CPU exceeds a threshold, distributing the load and reducing CPU usage per instance during peak hours.
Variation 2. You have an Azure App Service web app that experiences high CPU usage during peak hours. You need to scale out automatically based on CPU load. Which scaling solution should you use?
medium- A.Manual scaling
- B.Traffic Manager
- ✓ C.Autoscale with a CPU percentage rule
- D.Scale sets autoscale
Why C: Autoscale with a CPU percentage rule is the correct solution because Azure App Service supports built-in autoscaling that can automatically increase or decrease the number of instances based on a metric like CPU percentage. This allows the web app to handle peak-hour traffic by scaling out when CPU usage exceeds a defined threshold, ensuring performance without manual intervention.
Variation 3. Your Azure App Service web app experiences slow response times during peak hours. You suspect the App Service plan is under-provisioned. You need to scale out the app automatically based on CPU usage. What should you configure?
medium- A.Configure scheduled scaling in the app
- B.Manually increase instance count
- C.Configure scale up in the App Service plan
- ✓ D.Configure autoscale rules in the App Service plan
Why D: Autoscale rules in the App Service plan allow you to automatically scale out (increase instance count) based on metrics like CPU usage. This is the correct solution because it dynamically adjusts capacity in response to demand during peak hours without manual intervention.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.