Question 490
An IT support team must respond to this situation: A Linux desktop can ping the gateway but fails name lookups after a manual change to a resolver configuration. Which action is most appropriate within an authorized support workflow?
Explanation
Correct Answer
Restore the approved resolver through the supported network configuration service. This response addresses the exact facts of the case: A Linux desktop can ping the gateway but fails name lookups after a manual change to a resolver configuration. The governing technical principle is: /etc/resolv.conf and distro networking services govern configured DNS resolvers. Confirm the diagnosis using: Check resolver config, active network manager, dig results and lease information. Then test success against: Internal and external DNS queries succeed across reboot. Remaining exposure: Editing a generated resolv.conf directly may be overwritten automatically.
Incorrect Answers
Clear or relocate verified safe data based on the full filesystem analysis. That addresses a different mechanism; this question turns on Restore the approved resolver through the supported network configuration.
Use approved apt update and upgrade procedures, validating dependency changes. In the present case the governing issue is Restore the approved resolver through the supported network configuration, which this does not resolve.
Set only the necessary execute mode or group ownership under change control. It does not verify the requested outcome; here the decisive check concerns Restore the approved resolver through the supported network configuration.