A team wants to monitor average CPU on a small set of Linux VMs and OS disk free space, but they want the lowest telemetry ingestion cost possible. Which two actions should they take? Select two.

Enable full VM Insights for every guest performance counter.

Full VM Insights adds more telemetry than needed and increases ingestion cost for a small monitoring requirement.

Stream all syslog and event logs to a workspace before creating any alert.

Collecting all logs is broader than necessary and does not align with the goal of minimizing ingestion cost.

Rely on Azure Resource Health to measure guest OS disk free space.

Resource Health reports Azure platform status, not guest operating system disk usage inside the virtual machine.

What does this AZ-104 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Use a metric alert for the VM CPU metric. — The least expensive design is to use platform metrics where Azure already provides them and collect only the guest data that is missing. CPU monitoring should use a metric alert directly on the VM metric, avoiding log ingestion. For OS disk free space, Azure Monitor Agent with a narrowly scoped data collection rule lets you collect just that performance counter instead of ingesting a broad set of logs. This keeps telemetry targeted and cost-aware while still supporting both checks. Why others are wrong: Full VM Insights and sending every syslog or event log entry both increase ingestion volume and are unnecessary for the stated requirement. Azure Resource Health is about Azure service and platform availability, not guest operating system capacity. The objective is to monitor only what is needed, so broad telemetry collection is the wrong tradeoff here.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.