Question 120
A Linux administrator evaluates: A system analyst must verify the top repeated HTTP status codes from a known access-log format. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A system analyst must verify the top repeated HTTP status codes from a known access-log format. The recommended direct administrative response is: Use a bounded grep, awk, cut or sort pipeline to select the required log or delimited-data fields without changing the source file. The relevant failure or security risk is: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields. Validate success with: The pipeline returns the expected test rows and field values on representative input, leaving source data unchanged.
For the specific observation (A system analyst must verify the top repeated HTTP status codes from a known access-log format), the acceptance evidence is: The pipeline returns the expected test rows and field values on representative input, leaving source data unchanged. This verifies the action (Use a bounded grep, awk, cut or sort pipeline to select the required log or delimited-data fields without changing the source file.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Grepping an entire unfiltered log or using a wrong delimiter can silently miscount events or report unrelated fields.
Incorrect Answers
Software RAID health and rebuild with mdadm (1.3) would demonstrate or implement: The array reaches the expected healthy state with the replacement member synchronized and no new device I/O errors. This choice can be useful for that problem, but it does not establish the Shell text processing pipelines control being assessed here.
DNS resolver diagnosis with dig and hosts precedence (1.4) would demonstrate or implement: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. The required paired action and test concerns Shell text processing pipelines; a passing result for this alternative could leave that requirement unresolved.
Route and socket inspection with IP and ss (1.4) addresses another technical failure: A locally listening service and a reachable default gateway are separate prerequisites; one cannot prove the other. The paired-answer requirement concerns Shell text processing pipelines; this alternative does not provide the matching intervention and separate acceptance evidence.