Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam MS-102 Topic 8 Question 15 Discussion

Actual exam question for Microsoft's MS-102 exam
Question #: 15
Topic #: 8
[All MS-102 Questions]

Your company has on-premises servers and an Azure AD tenant.

Several months ago, the Azure AD Connect Hearth 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.

Show Suggested Answer Hide Answer
Suggested Answer: D, E

Contribute your Thoughts:

Bambi
8 months ago
Option D seems a little sketchy to me. I'm not sure I'd want to be running some random PowerShell cmdlet that I'm not familiar with. Better to stick with the more standard options like C or E.
upvoted 0 times
...
Glen
8 months ago
I'm leaning towards option E - reinstalling the agent. That seems like the most straightforward way to get the server back on the list and visible again. Plus, it's always a good idea to make sure you have a fresh install of the agent.
upvoted 0 times
...
Glory
8 months ago
Yeah, that's a good point. I'm thinking either option C or E could work - changing the startup type to Automatic or reinstalling the agent. But I'm not sure if the other options would be effective here.
upvoted 0 times
Mable
7 months ago
I agree. It's worth trying both options to ensure we can view the health status of Server1.
upvoted 0 times
...
Lang
8 months ago
Great idea. Let's go ahead and change the startup type to Automatic on Server1 as well.
upvoted 0 times
...
Tuyet
8 months ago
Let's try reinstalling the Azure AD Connect Health agent on Server1.
upvoted 0 times
...
Mattie
8 months ago
I think either option C or E would be the best bet to get Server1 back on the list.
upvoted 0 times
...
Vincent
8 months ago
I've had success with option E before, so that could work for Server1.
upvoted 0 times
...
Ngoc
8 months ago
Yeah, that's a good point. Reinstalling the agent might also solve the issue.
upvoted 0 times
...
Nan
8 months ago
I agree, I think changing the startup type to Automatic could help.
upvoted 0 times
...
...
Erick
8 months ago
Hmm, this is an interesting one. I'm not sure why the server would have been removed from the list, but it sounds like we need to get it back on there so we can view the health status.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77