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

Connection Monitor requires both the source (VM1) and destination (DC1) to be reachable and monitored. Since DC1 is on-premises, it must be onboarded to Azure using Azure Arc. The Azure Connected Machine agent enables Azure Arc and allows DC1 to be used as a monitoring endpoint in Connection Monitor.

The answer is A. The question says nothing about the on prem vms being Arc enabled. You cannot use AMA without Arc enablement. Monitoring connectivity from on-premises hosts: #1 To monitor connectivity from the on-premises host, it must be enabled with Arc agent. To learn more about enabling the Arc agent, see Connect hybrid machines with Azure Arc-enabled servers. The agent is supported on both Windows and Linux machines. #2 Once the Azure Arc agent is enabled, proceed to enable the Azure Monitor Agent. For more information, see Install and manage Azure Monitor Agent.

It is option A: The Azure Connected Machine agent enables you to manage your Windows and Linux machines hosted outside of Azure on your corporate network or other cloud providers. https://learn.microsoft.com/en-us/azure/azure-arc/servers/agent-overview

Can't be amy of the other options

All I can say is three different AI engines say B and give an explaination why not the rest of the options. And on this bombshell and lack of affirmative result from the despute I say B.

Trick question, it's the Azure Monitor agent that can be installed on an on-premises server, with the Azure Arc agent. The answer is D.

Letra A

A. the Azure Connected Machine agent for Azure Arc-enabled servers To use Connection Monitor to identify network latency between VM1 (in Azure) and DC1 (on-premises), you need to install the Azure Connected Machine agent for Azure Arc-enabled servers on DC1

To make Connection monitor recognize your on-premises machines as sources for monitoring, install the Log Analytics agent on the machines. https://learn.microsoft.com/en-us/azure/network-watcher/connection-monitor-overview#agents-for-on-premises-machines

Azure Network Watcher Agent because it is the only agent that enables Connection Monitor to perform latency tests between a resource in Azure and an on-premises server.

MMA (Log Analytics Agent) is deprecated. You have to install AMA (Azure Monitor Agent) BUT for DC1 (onprem) you have to install first the Azure Connected Machine for Azure Arc-enabled servers. So the answer is A and then D.

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.

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).

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