Question 660
A Linux administrator evaluates: A deployment service sees permission denied although the target file owner is correct and a parent path is protected. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A deployment service sees permission denied although the target file owner is correct and a parent path is protected), the acceptance evidence is: An authorized process reaches the intended path, while unrelated users still fail read or execute tests. This verifies the action (Inspect id, namei -l, stat and getfacl to diagnose effective file access, including parent directory traversal and ACL masks.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Granting world access to the final file may not fix a missing execute permission on a parent directory and exposes unnecessary data.
The observed Linux condition is: A deployment service sees permission denied although the target file owner is correct and a parent path is protected. The recommended direct administrative response is: Inspect id, namei -l, stat and getfacl to diagnose effective file access, including parent directory traversal and ACL masks. The relevant failure or security risk is: Granting world access to the final file may not fix a missing execute permission on a parent directory and exposes unnecessary data. Validate success with: An authorized process reaches the intended path, while unrelated users still fail read or execute tests.
Incorrect Answers
CPU saturation versus load-average analysis (5.5) would demonstrate or implement: Comparable workload samples isolate the actual runnable or blocked bottleneck and show improved response after a measured correction. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: An authorized process reaches the intended path, while unrelated users still fail read or execute tests.
IP route and asymmetric next-hop analysis (5.3) addresses another technical failure: Incorrect default routes or overlapping prefixes can send traffic to an unreachable next hop even with healthy interfaces. This choice can be useful for that problem, but it does not establish the ACL mask and directory traversal permission failures control being assessed here.
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. This case instead tests ACL mask and directory traversal permission failures; the choice measures or changes another part of the system.