Which issue is most likely causing an administrator to only log on to a server with a local account even though the server is joined to a domain?

Which issue is most likely causing an administrator to only log on to a server with a local account even though the server is joined to a domain?

• A. Firewall configuration
• B. DNS misconfiguration
• C. Network cable disconnection
• D. Incorrect local policy settings

Answer: (B)

A situation where an administrator can only log on to a server with a local account, despite the server being joined to a domain, is most likely due to DNS misconfiguration. When a server is part of a domain, it relies on the domain’s DNS for locating the necessary resources, including domain controllers for authentication and group policy objects. If the DNS settings are incorrect, the server would be unable to resolve the domain name or locate the domain controllers, which prevents domain credentials from being validated. As a result, the administrator may be forced to use local accounts instead, as the server cannot communicate with the domain effectively. The other options primarily affect connectivity or server configuration in a different manner. Firewall configuration may prevent certain types of network traffic but wouldn't specifically hinder login with domain accounts if the necessary ports were open. Network cable disconnection would lead to a lack of network connectivity, making it impossible to interact with anything on the network, including domain authentication; however, it is less specific to why local accounts would still be usable. Incorrect local policy settings typically wouldn't prevent domain login functioning unless they specifically block domain access, which is less common in a standard configuration.

A situation where an administrator can only log on to a server with a local account, despite the server being joined to a domain, is most likely due to DNS misconfiguration. When a server is part of a domain, it relies on the domain’s DNS for locating the necessary resources, including domain controllers for authentication and group policy objects. If the DNS settings are incorrect, the server would be unable to resolve the domain name or locate the domain controllers, which prevents domain credentials from being validated. As a result, the administrator may be forced to use local accounts instead, as the server cannot communicate with the domain effectively.

The other options primarily affect connectivity or server configuration in a different manner. Firewall configuration may prevent certain types of network traffic but wouldn't specifically hinder login with domain accounts if the necessary ports were open. Network cable disconnection would lead to a lack of network connectivity, making it impossible to interact with anything on the network, including domain authentication; however, it is less specific to why local accounts would still be usable. Incorrect local policy settings typically wouldn't prevent domain login functioning unless they specifically block domain access, which is less common in a standard configuration.