Question 640
A Linux administrator evaluates: A new deployment adds a listener but the server zone still denies required traffic from a specific application subnet. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A new deployment adds a listener but the server zone still denies required traffic from a specific application subnet), the acceptance evidence is: The service listens on the intended interface and a permitted remote connection succeeds while an unapproved source remains blocked. This verifies the action (Confirm service socket state with ss, test local and remote TCP reachability, and inspect nftables or firewalld rules to isolate the blocking layer.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Opening a port cannot help if the daemon only binds loopback or is stopped, and a listening socket alone cannot prove external access.
The observed Linux condition is: A new deployment adds a listener but the server zone still denies required traffic from a specific application subnet. The recommended direct administrative response is: Confirm service socket state with ss, test local and remote TCP reachability, and inspect nftables or firewalld rules to isolate the blocking layer. The relevant failure or security risk is: Opening a port cannot help if the daemon only binds loopback or is stopped, and a listening socket alone cannot prove external access. Validate success with: The service listens on the intended interface and a permitted remote connection succeeds while an unapproved source remains blocked.
Incorrect Answers
Mount failure and filesystem integrity diagnosis (5.2) would demonstrate or implement: The intended volume mounts cleanly after a supported recovery process, and integrity and application checks pass. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The service listens on the intended interface and a permitted remote connection succeeds while an unapproved source remains blocked.
Disk IO wait and throughput bottleneck diagnosis (5.5) would demonstrate or implement: Scaling CPUs or changing network MTU does not resolve sustained disk latency and queue depth on a saturated device. The required paired action and test concerns Listener and firewall differentiation on Linux; a passing result for this alternative could leave that requirement unresolved.
CPU saturation versus load-average analysis (5.5) addresses another technical failure: A high load average alone does not prove CPUs are busy, because tasks in uninterruptible I/O wait may contribute. The paired-answer requirement concerns Listener and firewall differentiation on Linux; this alternative does not provide the matching intervention and separate acceptance evidence.