A compost-lab public dashboard on App Service spikes CPU every weekday at 08:00 when sensors flush. Which autoscale approach should the developer implement?
Select an answer to reveal the explanation.
Short Explanation
When the sensors all shout at once, CPU climbs—so teach the plan to add instances when that metric crosses a line, then shed them when it cools. That is App Service metric autoscale, not an Application Insights ping or a Cosmos RU dial.
Full Explanation
App Service autoscale rules evaluate host metrics such as CPU percentage or HTTP queue length and adjust instance count against scale-out and scale-in thresholds. Application Insights alerts observe the app but do not scale the plan. Slot swaps and Cosmos autoscale address different resources.