You need to monitor CPU on a small set of VMs while keeping ingestion costs low. Which two actions are the best choices? Select two.

Enable verbose guest logging on every server

Verbose logging creates more data than needed and works against a low-cost monitoring goal.

Collect all Windows event logs from every VM

Collecting everything increases ingestion volume and is not cost-aware for simple CPU monitoring.

Create a separate workspace for each VM

Multiple workspaces add management overhead and usually do not reduce telemetry cost.

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 Azure Monitor platform metrics for CPU instead of collecting guest logs — For a small VM fleet, Azure Monitor platform metrics are the most cost-efficient way to track CPU because they are already available without collecting extra guest logs. Limiting diagnostic categories and performance counters further reduces ingestion and storage cost. Together, these choices provide the needed operational visibility while avoiding unnecessary log volume and workspace clutter. Why others are wrong: Collecting all Windows event logs or enabling verbose logging creates more data than this simple monitoring task requires. A separate workspace per VM adds complexity and usually does not improve cost efficiency. These choices are common mistakes when teams overcollect telemetry instead of using built-in metrics first.

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.