Remote staff at a SaaS company can reach their default gateway, yet the collaboration app on the laptop resolves to the wrong address. Which setting should be corrected?
Select an answer to reveal the explanation.
Short Explanation
The laptop already found the front door and is calling the wrong directory for the room number. You correct DNS on the device, because the gateway answers and the name does not. A new circuit or a routing alert does not fix a resolver that returns the wrong address.
Full Explanation
The laptop can reach its default gateway, so the local next hop is working, and the collaboration application still resolves to the wrong address. Name lookup is a separate step from forwarding, and the bad answer is coming from the DNS resolver configured on that device. Correcting the resolver on the laptop fixes the address the application receives without replacing a path that already forwards. Replacing the WAN circuit between the user and the SaaS edge would fit a loss or reachability problem on the path, not a resolver that hands back the wrong address while the gateway is reachable. A BGP alert on the collaboration prefix watches whether that prefix is advertised and stable, which does not correct a laptop that is querying the wrong resolver or accepting a bad answer. Moving the data-center Enterprise Agent closer to the application tier changes a probing point inside the data center and does not change the resolver setting on the remote laptop. Exam caveat: a reachable gateway only proves the laptop can forward; it says nothing about which address a name resolved to. Operational check: compare the resolver and the address returned on a failing laptop with the resolver and address on a laptop where the collaboration app is correct.