Judge service and continuity evidence

Objectives

Judge each independent claim only against the stated baseline. Accept sufficient evidence for its limited claim, not blanket certification.

Baseline: service availability uses all agreed service-window downtime with no exclusions. Emergency changes require on-call authorization and later review. Booking targets are RTO 4 hours at 50 percent capacity and RPO 15 minutes. A BCMS recovery claim needs measured exercise results. Joint reviews are allowed if both systems' required topics and decisions are covered.

Verdicts are accept or reject. Every rejection needs one reason code from: invalid-measurement | unauthorized-change | unproven-recovery | data-loss-breach.

EV-1 | Monthly availability is declared compliant after the analyst removes a two-hour in-window outage from the calculation without an agreed exclusion.
EV-2 | A production emergency patch has no on-call authorization and no later review; the team says emergencies need neither.
EV-3 | A signed continuity plan is offered as proof that booking recovery met four hours. No exercise or actual recovery measurements exist.
EV-4 | A restore completes within two hours, but the latest recoverable data point is 60 minutes before disruption. The team claims it meets the 15-minute RPO.
EV-5 | A booking exercise records disruption at 09:00, usable service at 50 percent throughput at 12:30, data recovered to 08:50 and successful transaction reconciliation. The claim is that this exercise met booking RTO and RPO.
EV-6 | A joint management review records required SMS and BCMS inputs, scope-specific results, decisions, owners and follow-up. The claim is that a combined review can cover both systems.

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

   Read each claim independently against the baseline.

2. Step 2

   Judge every line, including the boring ones

   Give every EV identifier exactly one verdict.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Compare the measured outcome with the specific claim. Accept the scoped successful exercise and adequately covered joint review.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Use invalid-measurement for altered SLA denominators, unauthorized-change for bypassed change authority, unproven-recovery for a plan without performance evidence, and data-loss-breach for an excessive restore-point gap.

   Each rejection cites a valid reason code

Rules summary

• XP on pass

  50 bonus XP the first time every check goes green.

• Paid hints

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