220-1102 Question 164
Single answer1.7 Given a scenario, configure Microsoft Windows networking features on a client/desktop.A remote employee is using a Windows 11 laptop at home and can browse the internet, but cannot access file shares on the company network by hostname after connecting to the corporate VPN. The user can successfully reach the file server by IP address after the VPN connects. You verify that the VPN tunnel is active and that general internet access still works. Which Windows networking configuration should the technician update on the client to most likely resolve this name-resolution problem?
- A
Configure the VPN connection to use the company's DNS servers
- B
Enable Metered connection on the user's Wi-Fi adapter
- C
Disable IPv6 on the Ethernet and Wi-Fi adapters
- D
Set the network profile to Public after the VPN connects
Show answer and explanation
Correct answer: A
Explanation
This scenario tests practical Windows networking configuration on a client desktop, specifically VPN and DNS behavior. When a user can reach a resource by IP address but not by hostname, the issue is usually name resolution rather than routing or basic connectivity. In Windows, VPN connections commonly need to obtain or be manually configured with the organization's internal DNS servers so internal hostnames, domains, and file servers can be resolved correctly. This aligns with Microsoft best practices for remote access and VPN client configuration, where DNS settings for the VPN interface are critical for accessing internal resources. Network profile changes, metered connection settings, and disabling IPv6 may affect other aspects of connectivity or system behavior, but they do not directly address the core symptom in this case.
- A. Correct.
Correct. If the user can access the file server by IP address but not by hostname, the most likely issue is DNS name resolution. In a corporate VPN scenario, the VPN connection should typically provide or use the organization's internal DNS servers so internal hostnames can be resolved. In Windows, this can be configured through the VPN adapter's TCP/IP settings or delivered automatically by the VPN configuration. This is a common client-side networking fix for remote access scenarios.
- B. Incorrect.
Incorrect. A metered connection setting affects how Windows handles background data usage, updates, and synchronization behavior. It does not solve internal DNS resolution over a VPN. Someone might choose this if they associate home Wi-Fi troubleshooting with connectivity settings, but it does not address the symptom of hostname failure with successful IP connectivity.
- C. Incorrect.
Incorrect. Disabling IPv6 is not an appropriate first-line fix for this scenario and is not likely to resolve a straightforward internal DNS issue. Microsoft generally recommends against disabling IPv6 unless there is a specific, documented reason. The problem described points to DNS configuration for the VPN rather than an IPv6 protocol conflict.
- D. Incorrect.
Incorrect. Setting the network profile to Public changes firewall and discovery behavior, but it does not make Windows use the correct internal DNS servers for company resources. A candidate might pick this because network profile settings do affect sharing and discovery, yet the user is specifically failing to resolve hostnames while direct IP access works, which is much more indicative of DNS configuration.