A council IT slide lists virtual machines, containers, and serverless. How should serverless be placed relative to always-on VMs?
Select an answer to reveal the explanation.
Short Explanation
Line the options up like layers of packaging. A VM is a whole computer you still tend. Containers trim some of that work. Serverless is the meal-kit delivery—you bring the recipe (code), and the kitchen (platform) handles the stove time, often charging per cook rather than for a stove left on all night.
Full Explanation
Virtual machines provide infrastructure you manage at the OS level. Containers package applications with fewer OS duties but still involve capacity you reason about. Serverless raises the abstraction further: the cloud executes code on demand and the customer does not manage servers, with billing commonly tied to executions or consumed resources rather than a continuously running VM. Placing serverless correctly on that spectrum is the describe-level skill.