300-445 Question 187
Single answerA user reports that they are unable to access a company’s internal web application hosted on a private server. Upon investigation, you find the user is connected to the corporate network via VPN. Using collected network data, you notice the following:
- The user’s device has the correct IP address and subnet mask for the VPN network.
- A ping to the application server’s IP address times out.
- A traceroute to the application server stops at the VPN gateway.
- DNS resolution for the application’s URL is successful.
What is the most likely cause of the issue?
- A
The default gateway on the user's device is misconfigured.
- B
There is a routing issue between the VPN gateway and the private server.
- C
The DNS server is not resolving the application's URL correctly.
- D
The user’s VPN client is not properly authenticating to the VPN gateway.
Show answer and explanation
Correct answer: B
Explanation
The traceroute stopping at the VPN gateway strongly indicates a routing issue between the VPN gateway and the private server. Since the user has the correct IP address and DNS resolution is working, the problem is not with the user's device or the DNS server but lies within the network path between the VPN gateway and the private server. Diagnosing such issues typically involves verifying routing configurations and connectivity beyond the VPN gateway.
- A. Incorrect.
The default gateway is correctly configured since the user can connect to the VPN and has the correct IP address for the VPN network.
- B. Correct.
The traceroute stopping at the VPN gateway indicates that the issue lies between the VPN gateway and the private server, likely due to a routing problem.
- C. Incorrect.
DNS resolution is successful as the application’s URL resolves correctly, ruling out DNS issues.
- D. Incorrect.
The user is connected to the VPN, which means the VPN client has authenticated successfully. This is not the cause of the issue.