220-1102 Question 175
Single answerDomain Name System (DNS) settingsA technician is troubleshooting a Windows 11 workstation that can reach internet sites by IP address, but users report that websites fail to load when they enter names such as www.example.com. The technician confirms the network cable is connected, the PC has a valid IPv4 address and default gateway, and the issue affects only this workstation. Which action is the BEST next step to restore normal connectivity?
- A
Change the workstation's DNS server setting to a valid internal or public DNS server
- B
Replace the default gateway with the ISP's router address
- C
Disable DHCP and assign a static APIPA address
- D
Flush the browser cache and clear saved cookies
Show answer and explanation
Correct answer: A
Explanation
This scenario reflects a classic DNS troubleshooting pattern: successful connectivity by IP address but failure by hostname usually indicates a DNS configuration or resolution problem. On A+ Core 2, candidates should recognize that DNS translates human-readable hostnames into IP addresses. If routing and addressing are working, the next logical step is to verify the configured DNS servers using tools such as ipconfig /all and then test name resolution with nslookup. In Windows and standard TCP/IP troubleshooting best practice, confirming DNS server settings is one of the first steps when only name-based access fails. Microsoft networking documentation and common enterprise support procedures both emphasize checking adapter DNS settings, DHCP-provided DNS values, and local overrides before moving to more advanced troubleshooting.
- A. Correct.
Correct. If the workstation can access resources by IP address but not by hostname, the most likely problem is name resolution. Verifying and correcting the DNS server setting is the best next step. A wrong DNS server address, an unreachable DNS server, or a manually entered incorrect DNS value can prevent hostname resolution while leaving basic IP connectivity intact.
- B. Incorrect.
Incorrect. The default gateway is used to reach remote networks, and the scenario already states the workstation has a valid gateway and can reach internet sites by IP address. That indicates routing is functioning. Changing the gateway would not address a hostname resolution problem and could create a broader connectivity issue.
- C. Incorrect.
Incorrect. APIPA addresses in the 169.254.0.0/16 range are self-assigned when DHCP fails and do not provide normal routed internet access. The workstation already has a valid IPv4 address and can reach external resources by IP, so assigning an APIPA address would make connectivity worse, not better.
- D. Incorrect.
Incorrect. Browser cache and cookies can affect webpage behavior, logins, or stale content, but they do not typically prevent all hostname resolution across the system. Since the symptom is that names do not resolve while IP-based access works, the issue is at the DNS layer rather than within the browser's cached content.