Judge corrective action closure evidence
Objectives
Judge each closure claim independently. Accept only evidence meeting its own stated closure rule.
F01 requires reviews of E01-E12, a controlled gate release and independent testing of five subsequent emergency CDE changes reviewed within two business days. F02 requires H07 impact review, approval-gate repair and independent testing of ten subsequent hosting changes approved before deployment by different people. Training alone, incomplete correction and failed retests cannot support closure.
Verdicts are accept or reject. Every rejection needs one reason code from: no-effectiveness-evidence | failed-retest | original-correction-missing | risk-acceptance-only.
Independent closure claims
CA-1 | F01: training attendance and an owner signature only. No original correction or operating retest. CA-2 | F01: E01-E12 reviewed and a controlled gate released. Five subsequent changes independently checked, but one review occurred after four business days. CA-3 | F01: E01-E12 reviewed, controlled gate release verified, and an independent auditor checked five subsequent changes against source logs; all had reviews within two business days. CA-4 | F01: controlled gate release and five successful independent subsequent retests, but E01-E12 were never reviewed. CA-5 | F02: H07 impact reviewed, approval gate repaired, and an independent auditor checked ten subsequent hosting changes; each had a different human approver before deployment. CA-6 | F02: management signed risk acceptance instead of repairing the gate or performing the required tests.
Checks the server runs (3)
- Every line in the fixture carries a verdict
- Accept and reject land on the right lines
- Each rejection cites a valid reason code
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.
- Step 1
Read the request before the artefact
Read each claim against its finding-specific closure baseline.
- Step 2
Judge every line, including the boring ones
Judge all six independent claims exactly once.
Every line in the fixture carries a verdict
- Step 3
Separate what is wrong from what is merely ugly
Accept a claim only if original correction, preventive action and required operating tests are all supported.
Accept and reject land on the right lines
- Step 4
Say why, in the vocabulary the programme uses
Use the closest stated defect for rejection. Accepted claims need no reason code.
Each rejection cites a valid reason code
Rules summary
XP on pass
60 bonus XP the first time every check goes green.
Paid hints
1 available. Each costs 25% of the lab XP (about 15 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.
