Question 600
A production support team notices: A server's DNS queries intermittently go to an unexpected resolver after network reconfiguration. What is the correct interpretation?
Explanation
Correct Answer
The decisive distinction is that a static glance at resolv.conf may not show link-specific DNS routing. Confirm with a targeted check: queries consistently select the approved resolver.
Incorrect Answers
An SSH daemon restart cannot fix SYN packets dropped upstream. That can explain why a server can reach a peer by IP but SSH times out after an outbound filter change, whereas the current evidence supports per-link DNS selection can change after NetworkManager or systemd-resolved updates.
It would account for a Linux system has the wrong default gateway after DHCP renewal, not the current evidence. For this incident, a static glance at resolv.conf may not show link-specific DNS routing; the alternative mechanism leaves that distinction unexplained.
A public resolver cannot answer private corporate namespace records. That can explain why a VPN client cannot reach private names because only corporate DNS domains should use the tunnel, whereas the current evidence supports per-link DNS selection can change after NetworkManager or systemd-resolved updates.





CompTIA Linux+ (XK0-006) Practice Tests