exam questions

Exam MS-100 All Questions

View all questions & answers for the MS-100 exam

Exam MS-100 topic 2 question 18 discussion

Actual exam question from Microsoft's MS-100
Question #: 18
Topic #: 2
[All MS-100 Questions]

Your company has on-premises servers and a Microsoft Azure Active Directory (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 Active Directory 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.

  • A. From Windows PowerShell, run the Register-AzureADConnectHealthSyncAgent cmdlet.
  • B. From Azure Cloud shell, run the Connect-AzureAD cmdlet.
  • C. From Server1, change the Azure AD Connect Health services Startup type to Automatic (Delayed Start).
  • D. From Server1, change the Azure AD Connect Health services Startup type to Automatic.
  • E. From Server1, reinstall the Azure AD Connect Health agent.
Show Suggested Answer Hide Answer
Suggested Answer: AE 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
[Removed]
Highly Voted 4 years, 9 months ago
Answer: A E Explanation question states that another administrator removed Server1 from the list. To view the health status of Server1, you need to re-register the AD Connect Health Sync Agent. You can do this manually by running theRegister-AzureADConnectHealthSyncAgentcmdlet. Alternatively, you can reinstall the Azure AD Connect Health agent. The Azure AD Connect Health agent is registered as part of the installation.
upvoted 29 times
...
Jokke71
Highly Voted 5 years, 2 months ago
After deleting a service instance from Azure AD Connect Health service, if you want to start monitoring the same server again, uninstall, reinstall, and register the Health Agent on that server. https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-operations
upvoted 9 times
...
Amir1909
Most Recent 1 year, 2 months ago
A and E is correct
upvoted 1 times
...
Don123
2 years, 2 months ago
A. From Windows PowerShell, run the Register-AzureADConnectHealthSyncAgent cmdlet. E. From Server1, reinstall the Azure AD Connect Health agent.
upvoted 1 times
...
Moderator
2 years, 8 months ago
Selected Answer: AE
Still a valid question (July 30th 2022).
upvoted 4 times
mikl
2 years, 8 months ago
Thank you :)
upvoted 1 times
...
...
spg987
3 years, 7 months ago
It is my exam today
upvoted 5 times
...
mikl
4 years, 1 month ago
A and E seems correct.
upvoted 4 times
...
mkoprivnj
4 years, 4 months ago
A & E for sure!
upvoted 6 times
...
Tarek
5 years ago
There are various reasons why AAD Connect Health monitoring agent doesn’t work anymore. Potential reasons are: Server has been deleted Server has been marked as inactive in AAD Connect Data Retention Policy There are two options to fix this problem Install newest version of monitoring agent Re-register monitoring agent https://samilamppu.com/2019/04/15/how-to-fix-unmonitored-azure-ad-connect-health-status/
upvoted 4 times
...
VP11
5 years, 1 month ago
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago