Review six storage assurance claims

Objectives

A storage owner submits six claims for audit sign-off. She says a surviving copy, an encrypted object, and a completed snapshot are all sufficient evidence of safe storage.

Accept only claims supported by the stated evidence. Reject each faulty claim with its root reason code; assess only the claim made, not unstated implementation details.

Verdicts are accept or reject. Every rejection needs one reason code from: metric-confusion | no-history | public-exposure | untested-recovery.

CS-1 | Claim: the private export access boundary is tested. Evidence: approved reader reads its prefix, is denied a neighbouring prefix; unsigned anonymous reads are denied for both, including historical versions.
CS-2 | Claim: eleven nines of annual durability guarantees eleven nines of read uptime. Evidence: durability design target only.
CS-3 | Claim: the replica provides a pre-overwrite restore point. Evidence: overwrites synchronously replace both copies; no history or separate backup exists.
CS-4 | Claim: encryption at rest makes anonymous reads confidential. Evidence: public read policy allows anyone to download the plaintext through the service.
CS-5 | Claim: a completed live snapshot proves application recovery. Evidence: job success only; no quiescing, database restart, or transaction validation has been tested.
CS-6 | Claim: the cold-tier restore meets the four-hour RTO in the tested scenario. Evidence: timed isolated recovery including retrieval and database validation completed in 95 minutes.

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 assertion. A useful test must measure the property being claimed.

2. Step 2

   Judge every line, including the boring ones

   Include every fixture identifier once, even when its evidence is adequate.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Compare the stated assurance with the exact test performed. Do not infer historical content from duplicate current copies or application correctness from a job status.

   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 describing the immediate gap: mismatched measurement, absent historical state, anonymous disclosure, or missing restore validation. Leave reasons empty on 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.