Review the protection claims

Objectives

Review six independent claims for Halcyon's restricted-export service. Accept only claims supported by the stated facts. The reviewer insists that an encryption setting settles every compliance question; do not inherit that assumption.

For rejection choose the root failing: hop-gap for an uncovered network hop, rotation-confusion for treating rotation as migration, deletion-dependency for destroying a required key, and jurisdiction-gap for ignoring legal authority. Accepted claims need no reason.

Verdicts are accept or reject. Every rejection needs one reason code from: hop-gap | rotation-confusion | deletion-dependency | jurisdiction-gap.

CDP-1 | Claim: all transport hops are encrypted. Facts: public TLS is valid; gateway-to-worker traffic is plaintext.
CDP-2 | Claim: stored exports use envelope encryption. Facts: payloads use data keys; a separately controlled wrapping key protects those data keys; wrapped keys and metadata accompany ciphertext.
CDP-3 | Claim: rotation migrated all old exports. Facts: only new writes use the new version; old wrapped keys remain unchanged.
CDP-4 | Claim: old key deletion is safe today. Facts: an archive under retention still needs that key; no replacement wrapper exists.
CDP-5 | Claim: sovereignty obligations are settled by disk location alone. Facts: copies stay in J1 but the operator is subject to compulsory-access law in J2; no legal assessment exists.
CDP-6 | Claim: routine readers lack destructive key authority. Facts: an effective-policy review and denied deletion test show readers may unwrap for their dataset but cannot disable or delete keys or change grants.

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 as a proposition to prove, not an invitation to approve the whole service.

2. Step 2

   Judge every line, including the boring ones

   Account for every identifier once, including claims whose supporting facts are sufficient.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Trace connections, payload wrappers, retained dependencies, and legal authority separately. Do not demand facts unrelated to the actual claim.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   For each unsupported claim choose the code for its direct logical failure; leave the reason blank when the facts support the claim.

   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.