220-1102 Practice Question: A company deploys a new remote access solution…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The VPN client is using an incorrect DNS server

  Why it's wrong here

  If the VPN client were using an incorrect DNS server, users would likely experience issues resolving hostnames for various services, not just the file server. Since email access, which also relies on name resolution, is functional, it indicates that DNS resolution is generally working correctly for the VPN client. The problem is specific to the file server, suggesting a network connectivity issue rather than a universal name resolution failure.

• ✗

  The file server is not on the same VLAN as the VPN concentrator

  Why it's wrong here

  Network devices like file servers and VPN concentrators do not inherently need to reside on the same VLAN to communicate. Communication between different VLANs is a standard network design practice achieved through routing. A router or Layer 3 switch can facilitate traffic flow between distinct VLANs, provided the necessary routes are correctly configured. Therefore, their separation by VLAN is not, by itself, the cause of a connectivity problem.

• ✓

  The VPN concentrator lacks a route to the file server's subnet

  Why this is correct

  For VPN clients to access resources on an internal network subnet, the VPN concentrator must have a defined route specifying how to reach that particular subnet. If the concentrator lacks a route to the file server's subnet, it will not know where to forward traffic destined for the file server's IP address. Consequently, packets from the VPN clients will be dropped or sent to an incorrect destination, preventing any successful connection to the file server. This is a fundamental layer 3 networking requirement.

• ✗

  The users do not have permission to log on locally to the file server

  Why it's wrong here

  User permissions, such as the ability to log on locally or access shared folders, are application-layer or operating system-level controls. These permissions are only evaluated *after* a successful network connection has been established between the client and the server. If users cannot even *reach* the file server, it indicates a fundamental network connectivity problem at a lower layer (e.g., Layer 3 routing), not an access control issue that would manifest later in the connection process.

Go deeper

Related to this question