Microsoft Exam MS-102 Topic 1 Question 28 Discussion

Actual exam question for Microsoft's MS-102 exam

Question #: 28
Topic #: 1

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 Na at Jul 12, 2024, 02:50 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Boris

4 months ago

Personally, I'd go with option C. Automatic startup is the way to go, unless you want your server to be as reliable as a politician's promise.

upvoted 0 times

...

Gilbert

4 months ago

Option A - Connect-AzureAD? Really? That's like using a bazooka to swat a fly.

upvoted 0 times

Laurel

3 months ago

Option A - Connect-AzureAD? Really? That's like using a bazooka to swat a fly.

upvoted 0 times

...

Murray

3 months ago

E) From Server1, reinstall the Azure AD Connect Health agent

upvoted 0 times

...

Laura

3 months ago

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

upvoted 0 times

...

Hyman

3 months ago

A) From Azure Cloud shell, run the Connect-Azure AD cmdlet.

upvoted 0 times

...

Johnna

4 months ago

I'm tempted to go with option D, but I don't know if that will work. Maybe I should just call the IT helpdesk and let them handle it.

upvoted 0 times

...

Zona

4 months ago

Hmm, I'm not sure about these options. Wouldn't it be easier to just ask the other admin what they did?

upvoted 0 times

Leslie

3 months ago

That's true, but sometimes it's faster to just fix the issue ourselves.

upvoted 0 times

...

Dorinda

3 months ago

It's always good to communicate with other admins.

upvoted 0 times

...

Magdalene

4 months ago

I'd go with option E. Reinstalling the agent seems like the most straightforward way to get Server1 back on the list.

upvoted 0 times

Yvonne

3 months ago

Let's go with option E then. Reinstalling the agent is the way to go.

upvoted 0 times

...

Selma

3 months ago

I agree, it's probably the quickest way to get Server1 back on the list.

upvoted 0 times

...

Julie

4 months ago

Option E seems like the best choice. Reinstalling the agent should do the trick.

upvoted 0 times

...

Arthur

4 months ago

Option C looks good to me. Changing the startup type to Automatic should do the trick.

upvoted 0 times

Raymon

3 months ago

I agree, using the Register-AzureADConnectHealthsyncAgent cmdlet from Windows PowerShell might also be a good solution.

upvoted 0 times

...

Staci

4 months ago

Running the Connect-AzureAD cmdlet from Azure Cloud shell could help in re-establishing the connection.

upvoted 0 times

...

Elin

4 months ago

I think reinstalling the Azure AD Connect Health agent on Server1 might also solve the issue.

upvoted 0 times

...

Gretchen

4 months ago

Option C looks good to me. Changing the startup type to Automatic should do the trick.

upvoted 0 times

...

Vincent

4 months ago

I'm not sure about option B. Maybe reinstalling the Azure AD Connect Health agent on Server1 (option E) could also fix the issue.

upvoted 0 times

...

Sabrina

5 months ago

I agree with Julio. Option B seems like a good solution to ensure Server1 is listed on the Azure AD Connect Servers list.

upvoted 0 times

...

Julio

5 months ago

I think option B could work. Changing the startup type to Automatic (Delayed Start) might help.

upvoted 0 times

...