220-1101 Question 447
Single answerLimited connectivityA technician is troubleshooting a Windows laptop that connects to the office Wi-Fi but shows "Limited connectivity." The user can reach the local printer by IP address, but cannot browse websites or access cloud-based email. Other users on the same wireless network are working normally. Running ipconfig shows the laptop has a valid IPv4 address, subnet mask, and default gateway. Which of the following is the MOST likely cause of the problem?
- A
The laptop has an incorrect DNS server configured
- B
The wireless access point is using the wrong SSID
- C
The laptop has a faulty NIC and must be replaced
- D
The DHCP server is offline
Show answer and explanation
Correct answer: A
Explanation
This question tests a common real-world support scenario: distinguishing between general network failure and limited connectivity caused by DNS issues. The key clues are that the laptop is connected to Wi-Fi, has a valid IP configuration, and can access a local device by IP address. That means the device can communicate on the local network and likely reach the default gateway. However, failure to browse websites and access cloud email points to a problem resolving domain names. In practice, technicians should verify this by pinging a known public IP address such as a DNS resolver, then testing name resolution with tools like nslookup. If IP connectivity works but hostname resolution fails, the next step is to check DNS server settings, whether obtained from DHCP or configured statically. This approach aligns with standard TCP/IP troubleshooting methodology and common Microsoft networking best practices for isolating DNS versus general connectivity problems.
- A. Correct.
Correct. The system has a valid IP configuration and can communicate on the local network, which means basic Layer 2 and Layer 3 connectivity is working. The inability to browse websites or reach cloud services while local IP-based resources remain accessible strongly suggests a name resolution problem. An incorrect or unreachable DNS server can cause Windows to report limited or partial connectivity because the client cannot resolve hostnames even though it can still reach local devices.
- B. Incorrect.
Incorrect. If the access point were using the wrong SSID, the laptop would typically fail to connect to the intended wireless network at all, or it would join a different network entirely. In this scenario, the laptop is already connected, has a valid IP configuration, and can reach a local printer, so the SSID is not the most likely issue.
- C. Incorrect.
Incorrect. A faulty NIC would more likely cause intermittent disconnections, failure to obtain a link, poor signal stability, or complete loss of connectivity. Since the laptop can successfully connect to Wi-Fi and access a local printer by IP address, the NIC is functioning well enough to pass traffic. Replacing hardware would be premature without stronger evidence of a hardware fault.
- D. Incorrect.
Incorrect. If the DHCP server were offline, the laptop would usually self-assign an APIPA address in the 169.254.x.x range or fail to receive proper network settings. The scenario specifically states that ipconfig shows a valid IPv4 address, subnet mask, and default gateway, which indicates DHCP likely worked or the device otherwise has valid network settings. DHCP is therefore not the most likely cause.