Challenge six test conclusions
Objectives
An internal tester has closed six control tests as "effective" and wants your review before the pack goes to the audit committee.
Accept the conclusions the evidence actually supports. Reject the ones where the test proves something other than what was claimed: the wrong period, the design rather than the operation, a sample that cannot represent the population, or a conclusion with no stated pass criterion.
Verdicts are accept or reject. Every rejection needs one reason code from: tests-design-not-operation | sample-not-representative | no-pass-criterion | evidence-outside-period.
Test log (tester's own words)
T-1 Change approval: sampled 25 of 8,142 merges at random; 25 had a recorded approver. Criterion: zero unapproved merges. Effective. T-2 Access review: confirmed the review procedure document exists and is signed by the CISO. Effective. T-3 Backup restore: full population of 12 monthly restores; 12 completed within RTO. Criterion: all restores within RTO. Effective. T-4 MFA enforcement: sampled 10 admins the platform lead selected as representative; all had MFA. Effective. T-5 Log retention: evidence exported on 14 Jan for a period ending 31 Dec. Effective. T-6 Vulnerability remediation: reviewed 40 findings; "most were closed promptly". Effective.
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 line as a claim plus the evidence offered for it, and ask whether the evidence could have produced a different answer. A test that cannot fail has not been run.
- Step 2
Judge every line, including the boring ones
Six conclusions, six verdicts. The two sound ones matter: an unreviewed pass is how a weak pack gets waved through on the strength of the strong entries around it.
Every line in the fixture carries a verdict
- Step 3
Separate what is wrong from what is merely ugly
Check three things per line in order: was the population defined, was the selection independent of the control owner, and was there a criterion stated before the result.
Then check the dates. Evidence pulled after the period closes describes the state on the day it was pulled, not the state during the period.
Accept and reject land on the right lines
- Step 4
Say why, in the vocabulary the programme uses
One code per rejection, naming the defect that would survive fixing the others. If a test both tests design only and lacks a criterion, the deeper failing is that it never touched the operation.
Each rejection cites a valid reason code
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.