Why is a serverless agent inappropriate for a long-running virtual machine workload?
Select an answer to reveal the explanation.
Short Explanation
Different lifecycle entirely. Function invocations appear and vanish; virtual machines sit there needing host metrics. You need a resident agent, not a serverless one.
Full Explanation
Serverless agents are built for short-lived function invocations with no persistent host, whereas virtual machines need an agent that runs continuously and collects host-level telemetry. The serverless model instruments ephemeral executions where nothing persists between invocations. Virtual machines require a resident agent that discovers processes and reports host metrics over time. Backend choice is not the distinction, so inability to report to self-hosted backends is wrong. Volume is not the issue; the collection model is, so collecting more data than a VM can transmit is wrong. Serverless support spans providers, so single-cloud limitation is wrong. For the exam, match agent mode to workload lifecycle.