A legacy permitting application needs full guest operating-system control for custom drivers, while a small webhook should run only when a form is submitted. Which compute pairing fits those needs?
Select an answer to reveal the explanation.
Short Explanation
Old software that demands the whole OS belongs on a VM. A little “run when this happens” webhook is classic Functions territory. Match control needs to the compute style instead of forcing one size on both.
Full Explanation
Workloads that require full operating-system control are a common fit for Azure Virtual Machines (IaaS). Short-lived, event-driven logic is a common fit for Azure Functions (serverless compute). Choosing compute by how much infrastructure the team must manage—and how the code is triggered—is the fundamentals comparison, not deep Kubernetes administration.