Question 560
A Linux administrator evaluates: A reliability team needs evidence that its log aggregation and webhook notifications identify a sustained outage. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A reliability team needs evidence that its log aggregation and webhook notifications identify a sustained outage), the acceptance evidence is: A controlled service degradation crosses the documented threshold and produces an actionable alert with the relevant host and timestamp. This verifies the action (Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach.
The observed Linux condition is: A reliability team needs evidence that its log aggregation and webhook notifications identify a sustained outage. The recommended direct administrative response is: Define appropriate service-level indicators and objectives, collect representative metrics and logs, and alert on meaningful sustained symptoms. The relevant failure or security risk is: An alert based only on an arbitrary single CPU spike can create noise while missing a real service availability breach. Validate success with: A controlled service degradation crosses the documented threshold and produces an actionable alert with the relevant host and timestamp.
Incorrect Answers
DNS versus connectivity diagnostic sequence (5.3) would demonstrate or implement: A working route to a server cannot compensate for a stale hosts entry or unresponsive name server. This choice can be useful for that problem, but it does not establish the SLO-based monitoring and actionable alert thresholds control being assessed here.
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 required paired action and test concerns SLO-based monitoring and actionable alert thresholds; a passing result for this alternative could leave that requirement unresolved.
ACL mask and directory traversal permission failures (5.4) addresses another technical failure: Granting world access to the final file may not fix a missing execute permission on a parent directory and exposes unnecessary data. The paired-answer requirement concerns SLO-based monitoring and actionable alert thresholds; this alternative does not provide the matching intervention and separate acceptance evidence.