grceng.academy
Triage lab 40 bonus XP

Triage the quarter's incident review

Start labRead the room

Objectives

Eight lines came out of the quarterly incident review. The responder rotation wants the systemic failures ranked for the next engineering cycle, not the one-off bad days.

Separate the failures of the system from the failures of the week.

List only the lines that qualify, worst first. Severity is one of: critical | high | medium | low. Add or delete rows as needed.

incident review notes

I-1  restricted customer data exposed; severity felt 'low-key' on the call, so the regulatory clock started two days late
I-2  vendor breach notice sat in an unmonitored inbox for three days before anyone read it
I-3  two runbooks contradicted each other on rollback; the wrong guess doubled the outage
I-4  eleven SEV1s last quarter, three of them single-team tooling outages and one a marketing typo
I-5  a new engineer asked excellent questions during the SEV2 bridge
I-6  the incident wiki got record page views this quarter
I-7  the facilitator called the last exercise 'the most engaged session yet'
I-8  the coffee machine on floor four was broken during the SEV1

Checks the server runs (4)

  • The right findings are raised
  • Benign lines are left out
  • Severity matches the actual exposure
  • Ranked worst first

Check names are all you see here: the expectations that decide pass or fail, and the reference solution, stay on the server.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

  1. Step 1

    Read the fixture as a population, not a list

    Read the notes as a population: four are defects in the response machinery, four are texture. The rotation can only fix machinery.

  2. Step 2

    Decide what actually qualifies

    A line qualifies if the system produced the wrong outcome: a clock that started late, a notice nobody saw, a runbook that misled, a severity label that means nothing.

    The right findings are raised

  3. Step 3

    Resist the loud lines

    Good questions, page views and engaged sessions are good weeks, not failures. Leave them out even though they feel relevant.

    Benign lines are left out

  4. Step 4

    Grade the exposure, not the wording

    The late regulatory clock carries legal exposure: that is the worst line. An unread breach notice is the same class of failure without the clock. A contradictory runbook costs minutes; a meaningless SEV1 costs the next real SEV1.

    Severity matches the actual exposure

  5. Step 5

    Rank so the first line is the one you act on

    Rank so the first line is the one with regulatory or customer-data exposure.

    Ranked worst first

Rules summary

  • XP on pass

    40 bonus XP the first time every check goes green.

  • Paid hints

    2 available. Each costs 25% of the lab XP (about 10 XP).

  • Reveal solution

    Scores 0 XP and unlocks only after 3 check runs.

  • Attempt cap

    60 check runs per learner. The runner warns you in the last 10.

  • Drafts

    Your editor content is saved in this browser, so a reload will not lose work.

  • Walkthrough

    Always free and never penalised: use it before spending a hint.