grceng.academy
Triage lab 40 bonus XP

Triage a week of control runs

Start labRead the room

Objectives

Your first automated control has been live for a week. The run log shows eight days of results and the dashboard is green.

Raise the runs that mean the control did not actually do its job. Leave the ones that are noisy but sound.

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

Control run log

C-1  Mon: run completed, 0 records evaluated: source returned an empty list, result recorded as PASS.
C-2  Tue: run completed, 214 records, 3 violations, ticketed.
C-3  Wed: run errored on API timeout; job caught the exception and recorded PASS.
C-4  Thu: run completed, 214 records, 0 violations.
C-5  Fri: run skipped: scheduler holiday calendar suppressed it; no record written at all.
C-6  Sat: run completed, 214 records, 1 violation, ticketed, closed same day.
C-7  Sun: run completed against a cached snapshot from Thursday because the live call failed.
C-8  Mon: run completed, 215 records, 0 violations.

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

    A green dashboard is an assertion about the control, not about the systems it watches. Read each run for whether it could have detected a violation had one existed.

  2. Step 2

    Decide what actually qualifies

    Four runs are healthy and four are not, but the unhealthy ones are not the ones with violations: violations found and ticketed are the control working.

    The right findings are raised

  3. Step 3

    Resist the loud lines

    Do not raise the runs that found something. Raise the runs that could not have found anything.

    Benign lines are left out

  4. Step 4

    Grade the exposure, not the wording

    A failure recorded as a pass is worse than a failure recorded as a failure, and a run with no record at all is worse than a run that recorded stale data, because nothing downstream can even see it.

    Stale-source runs sit below silent passes: the answer is wrong, but the log tells you why.

    Severity matches the actual exposure

  5. Step 5

    Rank so the first line is the one you act on

    Lead with the run whose result is most confidently wrong.

    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.