Question 620
A Linux administrator evaluates: A remote client receives SYN replies on the wrong interface because routing policy is inconsistent. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A remote client receives SYN replies on the wrong interface because routing policy is inconsistent), the acceptance evidence is: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source. This verifies the action (Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces.
The observed Linux condition is: A remote client receives SYN replies on the wrong interface because routing policy is inconsistent. The recommended direct administrative response is: Inspect ip route get, addressing, source routing and gateway reachability to isolate the incorrect forwarding path before changing firewall rules. The relevant failure or security risk is: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. Validate success with: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source.
Incorrect Answers
Degraded md RAID and storage I/O failure isolation (5.2) addresses another technical failure: Assuming an array is healthy because its mount still works can hide loss of redundancy and imminent data unavailability. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: Route lookup and a bounded traceroute show the intended egress path, and return traffic reaches the correct source.
Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Under a comparable transaction workload, measured await, utilization and application latency improve without new I/O errors. This case instead tests IP route and asymmetric next-hop analysis; the choice measures or changes another part of the system.
SLO-based monitoring and actionable alert thresholds (5.1) would demonstrate or implement: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. The paired-answer requirement concerns IP route and asymmetric next-hop analysis; this alternative does not provide the matching intervention and separate acceptance evidence.