Review the resilience evidence

Objectives

Evaluate six independent claims. The baseline requires a fifteen-minute RPO, a measured four-hour service RTO, supplier capability or tested fallback within that target, and exercise labels that match execution.

Reject each failing claim using its single closest reason code. Accept scoped claims backed by explicit evidence; do not assume one row repairs another.

Verdicts are accept or reject. Every rejection needs one reason code from: data-loss-gap | exercise-mislabel | supplier-gap | unmeasured-recovery.

RE-1 | Recovery-point compliance is claimed using only nightly backups. The measured outage loses 9 hours of orders; the approved RPO is 15 minutes.
RE-2 | A full interruption test is claimed from a facilitated scenario discussion. No recovery actions ran and production remained live.
RE-3 | Four-hour end-to-end recovery is claimed although the required courier interface has 12-hour recovery and no tested alternate path exists.
RE-4 | Four-hour recovery capability is claimed solely from an approved plan and an attendance list. No elapsed recovery or business validation was recorded.
RE-5 | A scoped restore test records outage at 10:00, usable minimum order service validated at 13:00, and restored records through 09:50. The approved RTO is 4 hours and RPO 15 minutes; both measured objectives are claimed met for this test.
RE-6 | A supplier-fallback claim links an approved manual booking procedure to a joint timed rehearsal delivering minimum dispatch service in 3 hours, with capacity and reconciliation validated against the 4-hour target.

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

   Treat each row as an independent scoped assertion against the baseline.

2. Step 2

   Judge every line, including the boring ones

   Account for each of the six identifiers once.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   A document can establish an objective without proving its achievement. Explicit scoped measurements can support acceptance.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Choose the direct defect, not a hypothetical secondary problem; leave reasons empty for accepted claims.

   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.