A maple cooperative hosts its public storefront and an overnight import site on the same small App Service plan to save money. During imports the storefront becomes CPU-starved. What should the developer explain?
Select an answer to reveal the explanation.
Short Explanation
One small plan is one shared engine—two sites take turns on the same cylinders. When the overnight import floors the gas pedal, the storefront stalls in traffic. Give the noisy job its own plan if the public site must stay snappy.
Full Explanation
Multiple web apps can run on a single App Service plan and therefore share that plan’s CPU and memory. Density saves cost until a noisy neighbor consumes the shared workers. Isolating the import workload onto a separate plan is a developer-facing hosting decision; subscription quota administration and unrelated Container Apps environments do not remove plan-level contention by themselves.