MS-102 · Question #83
Your company has on-premises servers and an Azure AD tenant. Several months ago, the Azure AD Connect Health agent was installed on all the servers. You review the health status of all the servers…
The correct answer is A. From Windows PowerShell, run the Register-AzureADConnectHealthSyncAgent cmdlet. C. From Server1, reinstall the Azure AD Connect Health agent. To ensure Server1's health status is viewable, you must either re-register the Azure AD Connect Health Sync agent or reinstall the agent if it was removed.
Question
Your company has on-premises servers and an Azure AD tenant. Several months ago, the Azure AD Connect Health agent was installed on all the servers. You review the health status of all the servers regularly. Recently, you attempted to view the health status of a server named Server1 and discovered that the server is NOT listed on the Azure AD Connect Servers list. You suspect that another administrator removed Server1 from the list. You need to ensure that you can view the health status of Server1. What are two possible ways to achieve the goal? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Options
- AFrom Windows PowerShell, run the Register-AzureADConnectHealthSyncAgent cmdlet.
- BFrom Azure Cloud shell, run the Connect-AzureAD cmdlet.
- CFrom Server1, reinstall the Azure AD Connect Health agent.
- DFrom Server1, change the Azure AD Connect Health services Startup type to Automatic.
- EFrom Server1, change the Azure AD Connect Health services Startup type to Automatic (Delayed
How the community answered
(32 responses)- A84% (27)
- B3% (1)
- D6% (2)
- E6% (2)
Why each option
To ensure Server1's health status is viewable, you must either re-register the Azure AD Connect Health Sync agent or reinstall the agent if it was removed.
The Register-AzureADConnectHealthSyncAgent cmdlet explicitly registers the server's health agent with the Azure AD Connect Health service, making it visible in the monitoring portal.
The Connect-AzureAD cmdlet establishes a connection to Azure AD but does not register a health agent or restore its monitoring status.
Reinstalling the Azure AD Connect Health agent on Server1 will ensure all necessary components are present and will initiate a fresh registration with the Azure AD Connect Health service, allowing its health status to be monitored again.
Changing the startup type to Automatic ensures the service starts automatically, but if the agent is unregistered or not installed, simply changing the startup type won't make it appear in the health list.
Similar to D, changing the startup type to Automatic (Delayed Start) ensures the service starts automatically, but it doesn't address an unregistered or missing agent.
Concept tested: Azure AD Connect Health agent registration and troubleshooting
Source: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-operations#reinstall-the-azure-ad-connect-health-agent
Topics
Community Discussion
No community discussion yet for this question.