MENU
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.
Suggested Answer: D, E
Get Premium MS-102 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
EU
Eulah
11 months ago
Changing the startup type to Automatic is a must!
LU
Luisa
11 months ago
Option D seems a bit off to me. Why would you need to register the sync agent again?
BR
Brandee
11 months ago
Wait, is it really that simple? I thought it would be more complicated.
MA
Marion
12 months ago
I agree, but I also think reinstalling the agent (option E) could work too.
ED
Edgar
12 months ago
I think option C is definitely one way to get Server1 back on the list.
MI
Micheline
1 year ago
I definitely remember that the Connect-Azure AD cmdlet is used for connecting to Azure AD, but I’m not sure if it helps with viewing health status directly.
PR
Providencia
1 year ago
I’m a bit confused about the cmdlets. I feel like I need to run a specific command to register the server again, but I can't recall the exact syntax.
LE
Lezlie
1 year ago
I think I saw a practice question where reinstalling the Azure AD Connect Health agent was one of the solutions. That might be a good option here too.
GL
Glenn
1 year ago
I remember something about the Azure AD Connect Health Services needing to be set up correctly, but I'm not sure if changing the startup type is enough.
LI
Lindsey
1 year ago
I'm a bit confused by this question. What's the difference between options B and C? I'll need to double-check the details to make sure I understand the right approach.
CA
Cassie
1 year ago
Alright, I've got this. The key is to make sure the Azure AD Connect Health Services are set to start automatically on Server1. Option C should do the trick.
GR
Gracia
1 year ago
Okay, let's see here. Seems like we need to find a way to get Server1 back on the Azure AD Connect Servers list. I'm thinking option C or E might be the way to go.
KE
Kenny
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully read through the details and think through the possible solutions.
RE
Reita
1 year ago
Hmm, I'm not sure if running the Connect-AzureAD cmdlet from Azure Cloud Shell would actually solve the issue here. I think I'll go with either option C or E to get Server1 back on the list.
GE
Georgeanna
1 year ago
Okay, I think I've got this. The first part will return a memory address, and the second part will return an array with the values 10 and 15.
EZ
Ezekiel
1 year ago
Hmm, I'm a bit confused by the nested functions here. I'll need to review my understanding of local vs. global variables.
GE
Genevieve
1 year ago
I'm pretty confident that option C is the right answer here. Reconfiguring the route policy to pass should resolve the label allocation problem.
BA
Bambi
3 years 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.
GL
Glen
3 years 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.
GL
Glory
3 years 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.
MA
Mable
3 years ago
I agree. It's worth trying both options to ensure we can view the health status of Server1.
LA
Lang
3 years ago
Great idea. Let's go ahead and change the startup type to Automatic on Server1 as well.
TU
Tuyet
3 years ago
Let's try reinstalling the Azure AD Connect Health agent on Server1.
MA
Mattie
3 years ago
I think either option C or E would be the best bet to get Server1 back on the list.
VI
Vincent
3 years ago
I've had success with option E before, so that could work for Server1.
NG
Ngoc
3 years ago
Yeah, that's a good point. Reinstalling the agent might also solve the issue.
NA
Nan
3 years ago
I agree, I think changing the startup type to Automatic could help.
ER
Erick
3 years 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.