220-1102 Question 184
Single answerProxy settingsA technician is troubleshooting a Windows 11 laptop that can browse internal company websites but cannot open any external websites. Other users on the same Wi-Fi network can access the internet normally. The user recently returned from working at a client site. In Settings, the technician notices a manually configured proxy server is enabled. Which action should the technician take FIRST to restore normal web access while preserving the ability to reconnect to the client environment later?
- A
Disable the manual proxy setting and document the previous proxy address and port for later reconfiguration if needed
- B
Run ipconfig /flushdns to clear cached name resolution issues caused by the proxy
- C
Change the laptop's DNS servers to public DNS addresses such as 8.8.8.8 and 1.1.1.1
- D
Disable Windows Defender Firewall because it may be blocking outbound HTTPS traffic
Show answer and explanation
Correct answer: A
Explanation
This question tests practical troubleshooting of proxy settings in Windows. A manual proxy configured for one environment commonly causes web access issues when a device is moved to another network. In Windows, proxy settings can be managed under Settings > Network & internet > Proxy, where a manual proxy can be turned off or automatic setup can be used if required by the organization. The best first action is to disable the incorrect manual proxy and document the prior settings so they can be restored later if the user returns to the client site. This follows common troubleshooting methodology used in A+ scenarios: verify the obvious configuration issue first, make the least disruptive change, and document any settings before modifying them. Microsoft documentation for Windows proxy configuration supports managing manual proxy server settings through the Proxy settings page, including address and port fields.
- A. Correct.
Correct. A manually configured proxy from the client site can prevent access to external websites when the laptop is no longer on that network. Disabling the proxy is the most direct first troubleshooting step. Documenting the proxy address and port preserves the user's ability to reconnect later without losing configuration details. This aligns with standard troubleshooting practice: identify what changed, test the most likely cause first, and avoid unnecessary changes.
- B. Incorrect.
Incorrect. Flushing DNS may help if name resolution is stale or corrupted, but the scenario specifically identifies a manually configured proxy as a likely cause. If the browser is attempting to send traffic to an unreachable or inappropriate proxy, DNS cache is not the primary issue.
- C. Incorrect.
Incorrect. Changing DNS servers is a plausible troubleshooting step when external sites do not resolve, but it does not address the stated problem of a manual proxy configuration. If web traffic is being directed to the wrong proxy, changing DNS will not restore normal browsing and introduces an unnecessary configuration change.
- D. Incorrect.
Incorrect. A local firewall can affect connectivity, but the symptoms point much more directly to the enabled manual proxy setting, especially since internal sites work and other users on the same network have normal internet access. Disabling the firewall is not an appropriate first step and is contrary to security best practices.