A systems administrator is unable to log on to a new DHCP server with Active Directory credentials. What is the likely cause of the issue?

A systems administrator is unable to log on to a new DHCP server with Active Directory credentials. What is the likely cause of the issue?

• A. The server is not joined to the domain
• B. The DHCP service is not enabled
• C. The network cable is disconnected
• D. The OS installation is corrupted

Answer: (A)

The most likely cause of the issue is that the server is not joined to the domain. When a system administrator attempts to log on to a server using Active Directory credentials, the server must be part of the domain where those credentials are managed. If the server is not joined to the domain, it cannot communicate with the domain controller to authenticate the credentials, resulting in a failed login attempt. In a domain environment, user authentication relies on trust relationships established between the server and the domain. Only domain-joined machines can leverage Active Directory for authentication, making this the key reason for the inability to log on given the scenario described. The other options relate to different operational aspects of the server but do not directly address the domain-related authentication problem. The DHCP service not being enabled does not impact login credentials. A disconnected network cable would affect connectivity to the domain, but the root problem in this case pertains to server domain membership. Lastly, while a corrupted OS could cause various issues, including login failures, it is less likely the immediate root cause in a setup context where domain membership is the primary concern for using Active Directory credentials.

The most likely cause of the issue is that the server is not joined to the domain. When a system administrator attempts to log on to a server using Active Directory credentials, the server must be part of the domain where those credentials are managed. If the server is not joined to the domain, it cannot communicate with the domain controller to authenticate the credentials, resulting in a failed login attempt.

In a domain environment, user authentication relies on trust relationships established between the server and the domain. Only domain-joined machines can leverage Active Directory for authentication, making this the key reason for the inability to log on given the scenario described.

The other options relate to different operational aspects of the server but do not directly address the domain-related authentication problem. The DHCP service not being enabled does not impact login credentials. A disconnected network cable would affect connectivity to the domain, but the root problem in this case pertains to server domain membership. Lastly, while a corrupted OS could cause various issues, including login failures, it is less likely the immediate root cause in a setup context where domain membership is the primary concern for using Active Directory credentials.