Exam AZ-104 topic 6 question 56 discussion

Connection monitor supports the Azure Monitor agent extension, which eliminates any dependency on the legacy Log Analytics agent. See here: https://learn.microsoft.com/en-us/azure/network-watcher/azure-monitor-agent-with-connection-monitor The following (older) link talks about setting up the Log Analytics agent: https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-overview#agents-for-on-premises-machines

Oh boy! that was very tricky! Its C guys. Log analytics agent. So for connection monitor to work on Azure machines you need NEtwork watcher extension but for on prem machines you need Log analytic agent. From MS learn " To make Connection monitor recognize your on-premises machines as sources for monitoring, install the Log Analytics agent on the machines. Then, enable the Network Performance Monitor solution. These agents are linked to Log Analytics workspaces, so you need to set up the workspace ID and primary key before the agents can start monitoring." https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-overview

D is correct https://learn.microsoft.com/en-us/azure/network-watcher/azure-monitor-agent-with-connection-monitor

A. First you install the azure connected machine agent, then after that you install the Azure monitor agent.

D is correct

A is correct. Everyone got it wrong. The question asks what to install on DC1... Connection Monitor from Azure Network Watcher requires both endpoints to be monitored for network performance. To monitor an on-premises machine (DC1), you must first enable management of that machine via Azure Arc. This process involves installing the Azure Connected Machine agent, which essentially "connects" your on-premises machine to Azure, allowing it to be treated like an Azure resource for monitoring purposes. Azure Arc is specifically designed to manage and monitor resources that are not natively in Azure (such as on-premises servers like DC1). Once DC1 is connected through Azure Arc, you can use Connection Monitor to assess network latency and connection reliability between VM1 (in Azure) and DC1 (on-premises).

D. https://azure.microsoft.com/en-us/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/

LAA is set to be deprecated 8/31. AMA is the only other agent listed here. Answer is D.

Well this is tricky... B is the necessary step before D, as per this documentation: https://learn.microsoft.com/en-us/azure/network-watcher/azure-monitor-agent-with-connection-monitor#:~:text=Agents%20for%20on%2Dpremises%20machines So it could either be B or D. I think I'll go with D, unless the question ask for the first step, then it would be B

GPT4 says C: Based on the latest guidance, C. the Log Analytics agent remains the most appropriate choice for ensuring compatibility and functionality with Connection Monitor to measure network latency between an Azure VM and an on-premises domain controller.

Both C and D are correct. However we will need Azure Connected Machine agent first before even installing either. Connection Monitor now supports the Azure Monitor Agent extension. This support eliminates any dependency on the legacy Log Analytics agent. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-create-using-portal#:~:text=Connection%20Monitor%20now%20supports%20the%20Azure%20Monitor%20Agent%20extension.%20This%20support%20eliminates%20any%20dependency%20on%20the%20legacy%20Log%20Analytics%20agent.

C is correct To make Connection monitor recognize your on-premises machines as sources for monitoring, install the Log Analytics agent on the machines. Then, enable the Network Performance Monitor solution. These agents are linked to Log Analytics workspaces, so you need to set up the workspace ID and primary key before the agents can start monitoring.

The correct answer is: D. An Azure Monitor agent virtual machine extension Explanation: You need to identify the network latency between an Azure virtual machine (VM1) and an on-premises domain controller (DC1) connected to Azure via ExpressRoute. Connection Monitor, a feature of Azure Network Watcher, helps you achieve this by monitoring network connectivity between Azure endpoints and endpoints outside Azure, including on-premises data centers. To leverage Connection Monitor for this scenario, you need an agent installed on DC1 that can communicate with Azure Monitor and report network connectivity data.

Log analytics agent need to install on DC1

C is correct

To make Connection Monitor recognize your on-premises machines as sources for monitoring, install the Log Analytics agent on the machines. Then, enable the Network Performance Monitor solution. These agents are linked to Log Analytics workspaces, so you need to set up the workspace ID and primary key before the agents can start monitoring. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-overview

"To make connection monitor recognize your on-premises machines as sources for monitoring, follow these steps: Enable your hybrid endpoints to Azure Arc-enabled servers. Connect hybrid machines by installing the Azure Connected Machine agent on each machine. This agent doesn't deliver any other functionality, and it doesn't replace Azure Monitor agent. The Azure Connected Machine agent simply enables you to manage the Windows and Linux machines that are hosted outside of Azure on your corporate network or other cloud providers. Install Azure Monitor agent to enable the Network Watcher extension. The agent collects monitoring logs and data from the hybrid sources and delivers them to Azure Monitor." https://learn.microsoft.com/en-us/azure/network-watcher/azure-monitor-agent-with-connection-monitor#agents-for-on-premises-machines