Review obligation claims
Objectives
Assess six independent claims against the facts given. Reject each flawed claim using its closest reason code; accept the two supported claims.
The baseline requires correct source classification, justified scope, parallel notification assessment, and evidence of operation rather than policy alone.
Verdicts are accept or reject. Every rejection needs one reason code from: source-confusion | unsupported-scope | deadline-confusion | missing-evidence.
Independent register review claims
OB-1 | An analyst classifies PCI DSS itself as a statute solely because a payment agreement requires compliance. OB-2 | A merchant declares all payment responsibilities out of scope solely because checkout is outsourced; no integration or responsibility review exists. OB-3 | A signed addendum requires notice within 24 hours of discovery. The lead waits 72 hours solely because GDPR supposedly allows that for every recipient. OB-4 | A row claims timely customer notice occurred. Its only support is an escalation policy, with no incident-specific delivery record. OB-5 | For appointment processing, the clinic determines purposes and essential means; the vendor acts only on instructions. The reviewed role map labels clinic controller and vendor processor. OB-6 | A scoped contract row links section 4, its 24-hour discovery trigger, incident lead, and IR-4 to a timestamped receipt showing notice 6 hours after discovery. This supports the claim of timely contractual notice only.
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
Compare the claim with its stated supporting facts, not its confident wording.
- Step 2
Judge every line, including the boring ones
Account for all six rows once, including supported claims.
Every line in the fixture carries a verdict
- Step 3
Separate what is wrong from what is merely ugly
Reject contradictions or unsupported conclusions; do not invent defects outside a claim's stated scope.
Accept and reject land on the right lines
- Step 4
Say why, in the vocabulary the programme uses
Choose the root failure category. Accepted claims need no rejection reason.
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.