You plan to standardize guest monitoring for all Azure Virtual Desktop session hosts across three subscriptions. Requirements: collect Windows Event logs for AVD agent and RDP, capture CPU, memory, disk, and network performance, and centralize to a single Log Analytics workspace using the Azure Monitor Agent only. What two configurations should you implement? (Choose two.)

The problem specifies using the Azure Monitor Agent (AMA) only. Therefore, you must deploy the Azure Monitor Agent extension (AzureMonitorWindowsAgent) to all session hosts. This agent collects data from the guest operating system. To define what data AMA collects and where it sends it, you need a Data Collection Rule (DCR). Creating one DCR that includes the specified Windows event channels and performance counters, and associating it with all session hosts, centralizes the configuration and ensures consistent data collection to the single Log Analytics workspace. Incorrect options: Enabling the Log Analytics agent (MMA) is incorrect because the requirement explicitly states using the Azure Monitor Agent only. MMA is the legacy agent. Enabling guest-level diagnostics or configuring Diagnostic settings on each VM are incorrect as these methods typically send data to Azure Storage or Event Hubs, and while they can integrate with Log Analytics, they don't exclusively use the AMA and DCR model for comprehensive guest monitoring as required.