Linux · Memory · Intermediate
The kernel chooses a victim
A service disappears without a normal application shutdown.
INITIAL ALERT
A service disappears without a normal application shutdown.
You are primary on-call. Establish the failure domain, protect healthy capacity, and choose the safest next action.
Systemd restart policy and executable configuration are valid.
The decisive evidence and solution remain locked inside the simulation.WHAT THIS TESTS
Production judgment across Linux · Memory.
Linux failures often surface as application symptoms. The fastest path is reading the operating system's evidence before changing networking, code, or cloud resources.
- 01Use host evidence to narrow failure domains
- 02Interpret systemd, memory, and filesystem signals
- 03Repair services without destroying evidence
SIMULATION STRUCTURE
Four evidence layers. No answer shown here.
The full exercise unlocks each layer as you commit to decisions.
Alert
Confirm the reported symptom and customer impact.
Baseline
Compare the failing path with a known-good condition.
Finding
Identify the evidence that separates plausible causes.
Change
Choose a controlled recovery and a durable prevention step.
Can you make the call without seeing the solution?
Try three incidents free. Paid incidents unlock only after Stripe confirms lifetime access.