Question 110
A Linux administrator evaluates: A host has two NICs and the chosen egress route does not match the intended application source network. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A host has two NICs and the chosen egress route does not match the intended application source network), the acceptance evidence is: The route lookup selects the intended next hop and ss shows the service listening on the required address and port. This verifies the action (Use ip route get, ip address and ss to distinguish destination routing, local interface configuration and listening sockets before changing access policies.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: A locally listening service and a reachable default gateway are separate prerequisites; one cannot prove the other.
The observed Linux condition is: A host has two NICs and the chosen egress route does not match the intended application source network. The recommended direct administrative response is: Use ip route get, ip address and ss to distinguish destination routing, local interface configuration and listening sockets before changing access policies. The relevant failure or security risk is: A locally listening service and a reachable default gateway are separate prerequisites; one cannot prove the other. Validate success with: The route lookup selects the intended next hop and ss shows the service listening on the required address and port.
Incorrect Answers
Ext4 and XFS filesystem repair and growth distinctions (1.3) addresses another technical failure: Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The route lookup selects the intended next hop and ss shows the service listening on the required address and port.
LVM physical volume to logical volume capacity growth (1.3) would demonstrate or implement: pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact. This choice can be useful for that problem, but it does not establish the Route and socket inspection with IP and ss control being assessed here.
Kernel module dependencies with modprobe (1.2) would demonstrate or implement: Directly inserting a module file without resolving its dependencies may fail or leave a driver nonfunctional. The paired-answer requirement concerns Route and socket inspection with IP and ss; this alternative does not provide the matching intervention and separate acceptance evidence.