Exam MS-100 topic 1 question 34 discussion

Answer is correct. This cmdlet available after you install AzureAD Connect https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#manually-register-azure-ad-connect-health-for-sync

I think AD Connect server is the correct one. The command is "Register-AzureADConnectHealthSyncAgent" and not "Register-AzureADConnectHealthADDSAgent or Register-AzureADConnectHealthADFSAgent". Also Register-AzureADConnectHealthSyncAgent is recommended when the registration fails after you install AD Connect ( see here https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#manually-register-azure-ad-connect-health-for-sync) Also, we can see the difference in prerequisites when it's clearly distinguished the agent for Sync, for ADDS and ADFS: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#install-the-agent I would go for C too.

Your AD FS server should be separate from your sync server. Don't install the AD FS agent on your sync server.

You must audit ADFS logs, so you install the agent on the ADFS server. AD Connect is not installed at all. So you start the command from the ADFS server. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-health-agent-install

Vote C - You will need to install the Azure AD Connect Health Sync Agent on the server that is running the Azure AD Connect tool.

Guess D is the valid option: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#install-the-agent-for-ad-fs Later the article refers to manual registration.

The Register-AzureADConnectHealthSyncAgent cmdlet is used to register the Azure AD Connect Health Sync Agent with Azure AD. It should be run on the server that is hosting the Azure AD Connect Health Sync Agent. Therefore, the correct answer is C, "an Azure AD Connect server". A. A member server or domain controller is not the correct server to run the cmdlet on as they are not the servers hosting the Azure AD Connect Health Sync Agent. B. While it is possible to install the Azure AD Connect Health Sync Agent on a domain controller, it is not recommended for security reasons. Therefore, it is not recommended to run the cmdlet on a domain controller. D. AD FS is a separate service from Azure AD Connect and is not directly related to the Azure AD Connect Health Sync Agent. Therefore, it is not recommended to run the cmdlet on an AD FS server.

C. An Azure AD Connect server. D. An AD FS server. The Register-AzureADConnectHealthSyncAgent cmdlet should be run from an Azure AD Connect server and an AD FS server. Azure AD Connect is the tool that enables you to synchronize your on-premises Active Directory with Azure AD. To monitor the health of AD FS and Azure AD Connect synchronization, you can use Azure AD Connect Health. By running the Register-AzureADConnectHealthSyncAgent cmdlet on the Azure AD Connect server and AD FS server, you can register these servers with Azure AD Connect Health and enable auditing and monitoring of user authentication.

answer is : C. tested

Cmdlet is only for a AADC.

You are preparing to run the Register-AzureADConnectHealthSyncAgent cmdlet. Register-AzureADConnectHealthADFSAgent -> ADFS Register-AzureADConnectHealthADDSAgent -> ADDS Register-AzureADConnectHealthSyncAgent -> Azure Ad Connect https://learn.microsoft.com/es-es/azure/active-directory/hybrid/how-to-connect-health-agent-install#register-the-agent-by-using-powershell Answer is correct C

AD Connect automatically installs health agent, so there's no need to run the register cmdlet like the question states. In the other hand, you can manually install the healthagent in ADFS and thus have the need to run the register cmdlet.

I do find the sources slightly confusing, but I believe that C (Azure AD Connect server) is the correct answer. The agent is normally configured during the installation of Azure AD Connect - on the server where that installation takes place. In case things don't work properly after installation, it is possible to manually register the health agent afterwards. Any other context apart from the Azure AD Connect server to run this cmd doesn't make sense then, I think. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#manually-register-azure-ad-connect-health-for-sync

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#manually-register-azure-ad-connect-health-for-sync

The Azure AD Connect Health agent is installed on each targeted server. Health agents must be installed and configured on targeted servers so that they can receive data and provide monitoring and analytics capabilities. For example, to get data from your Active Directory Federation Services (AD FS) infrastructure, you must install the agent on the AD FS server and the Web Application Proxy server. https://learn.microsoft.com/es-es/azure/active-directory/hybrid/how-to-connect-health-agent-install#install-the-agent-for-ad-fs

According to the documentation, it's possible to deploy the agent to an ADFS Server. But in this scenario, the cmdlet is slightly different: Register-AzureADConnectHealthADFSAgent. Therefore, the Register-AzureADConnectHealthSyncAgent cmdlet only apply to an Azure AD Connect Server. Answer is C. Source: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#install-the-agent-for-ad-fs

https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install states: "Your AD FS server should be different from your Sync server. Don't install the AD FS agent on your Sync server."