Microsoft Exam MS-102 Topic 2 Question 26 Discussion

Actual exam question for Microsoft's MS-102 exam

Question #: 26
Topic #: 2

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.

AFrom Azure Cloud shell, run the Connect-Azure AD cmdlet.

BFrom Server1, change the Azure AD Connect Health Services Startup type to Automatic (Delayed Start)

CFrom Server1, change the Azure AD Connect Health Services Startup type to Automatic

DFrom Windows PowerShell, run the Rejister-ArureADConnectHealthsyncAgent cmdlet.

EFrom Server1, reinstall the Azure AD Connect Health agent

Show Suggested Answer

Suggested Answer: D, E

by Ettie at Jun 28, 2024, 05:20 PM

Limited Time Offer

25%

Off

Get Premium MS-102 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Breana

4 months ago

Why don't we just go for the Azure PowerShell option? That's always a good fallback plan, right? *winks*

upvoted 0 times

Cruz

3 months ago

That could be a good idea to ensure everything is working properly.

upvoted 0 times

...

Slyvia

3 months ago

Maybe we should also consider reinstalling the Azure AD Connect Health agent on Server1.

upvoted 0 times

...

Izetta

3 months ago

I agree, it's a good fallback plan.

upvoted 0 times

...

Wilda

4 months ago

Yeah, Azure PowerShell is a reliable option.

upvoted 0 times

...

Mattie

5 months ago

Haha, I bet the other admin just wanted to mess with you. But seriously, option E sounds like the most reliable solution here.

upvoted 0 times

...

Mireya

5 months ago

Hmm, I'm not too sure about that. Option C seems more straightforward to me - just changing the startup type on Server1 should make it visible again.

upvoted 0 times

Flo

3 months ago

I agree, reinstalling the agent on Server1 could ensure that it is listed on the Azure AD Connect Servers list again.

upvoted 0 times

...

Desirae

4 months ago

That could work, but Option E) From Server1, reinstall the Azure AD Connect Health agent might be a more foolproof solution.

upvoted 0 times

...

Corrinne

4 months ago

Option C) From Server1, change the Azure AD Connect Health Services Startup type to Automatic

upvoted 0 times

...

Sherron

4 months ago

Let's go ahead and try that then.

upvoted 0 times

...

Nickolas

4 months ago

I agree, that sounds like the simplest solution.

upvoted 0 times

...

Mitzie

4 months ago

Option C) From Server1, change the Azure AD Connect Health Services Startup type to Automatic

upvoted 0 times

...

Fabiola

5 months ago

I would also consider option E. Reinstalling the Azure AD Connect Health agent on Server1 could potentially fix the issue.

upvoted 0 times

...

Christiane

5 months ago

I agree with Nakisha. Option B seems like a logical solution to ensure the health status of Server1 is visible.

upvoted 0 times

...

Nakisha

5 months ago

I think option B is a good choice. Changing the startup type to Automatic (Delayed Start) might help.

upvoted 0 times

...

Erasmo

6 months ago

I think option E is the way to go. Reinstalling the Azure AD Connect Health agent should do the trick.

upvoted 0 times

Marci

5 months ago

I think running the Connect-Azure AD cmdlet from Azure Cloud shell could also help.

upvoted 0 times

...

Jacquline

5 months ago

I agree, reinstalling the agent might solve the issue.

upvoted 0 times

...