Q: 10
A systems administrator is setting up a new server that will be used as a DHCP server. The
administrator installs the OS but is then unable to log on using Active Directory credentials.The
administrator logs on using the local administrator account and verifies the server has the correct IP
address, subnet mask, and default gateway. The administrator then gets on another server and can
ping the new server. Which of the following is causing the issue?
Options
Discussion
Probably D. . Had something like this in a mock, couldn't use AD creds until the server was joined to the domain.
Not seeing how B could be it, since network connectivity is fine (ping works). D is the more common trap here if you can't log in with AD creds.
Seen similar on practice labs, official guide also covers domain join issues like this. D
Don’t think it’s B, since network’s working and you can ping. D fits better in this scenario.
A, Firewall port 443 being closed could block some authentication traffic, I think. Not 100% sure here, but that's my pick.
Probably D here. If you can't log in with AD credentials but local works, that's usually a sign the server isn't joined to the domain. A and B are common traps, but network seems fine since the other server can ping it.
Does the question specify if "best" or "first" action is needed? That changes my pick, maybe D.
Feels like D - if you can't use AD credentials but can log in locally and ping works, the server's just not domain joined yet. Similar scenario was on another practice test, pretty sure that's what they want.
Don’t think C would cause that, D is the main issue here.
D
Be respectful. No spam.
