Challenge proposed interpretations

Objectives

Judge six independent proposed interpretations. Accept sound readings and reject flawed ones using the closest reason code.

Baseline: shall is mandatory and may permits in these fixture sources. Review all production administrators quarterly. A backup policy is not evidence of completed testing. Scope exclusions require supporting facts. Conflicting applicable legal duties require legal clarification rather than automatically picking the longest retention.

Verdicts are accept or reject. Every rejection needs one reason code from: weakened-duty | unsupported-exclusion | design-not-operation | unresolved-conflict.

IR-1 | The source says the owner shall review access. Proposal: shall means a suggestion because the owner is busy.
IR-2 | The source covers all production administrators. Proposal: exclude outsourced administrators solely because a supplier employs them; no source exception exists.
IR-3 | The source requires monthly restore testing. Proposal: the backup policy proves every monthly test succeeded, without test results.
IR-4 | Two applicable legal duties appear to conflict on retention. Proposal: always choose the longest period without legal analysis.
IR-5 | The source says records may be electronic and access shall be reviewed quarterly. Proposal: electronic format is permitted; the quarterly review remains mandatory.
IR-6 | Two contracts require the same full-population access review, one monthly and one quarterly, with identical criteria and no timing conflicts. Proposal: perform a monthly review, retain dated decisions, and map its periods and evidence to both contracts.

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 request before the artefact

   Compare the proposal with the baseline, not with a preferred product or process.

2. Step 2

   Judge every line, including the boring ones

   Include each IR identifier exactly once.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Accept supported readings. Reject changes that lose scope, force, or evidence requirements.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   For a rejection, choose the code identifying the primary flaw. Accepted rows need no rejection reason.

   Each rejection cites a valid reason code

Rules summary

• XP on pass

  45 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 11 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.