Challenge the trust claims

Objectives

Review six independent assertions against Bracken's baseline. Reject only the stated failures; do not invent missing facts for evidence that satisfies its narrow claim.

The baseline requires behavioral evidence beyond completion, leaver revocation at departure, tiering by data and access, and assurance scoped to the actual service including material downstream dependencies. Use one closest reason for each rejection.

Verdicts are accept or reject. Every rejection needs one reason code from: coverage-not-effectiveness | late-revocation | fee-based-tiering | assurance-scope-gap.

PPT-1 | The effectiveness claim cites only 100% annual course completion; no behavior or skill evidence exists.
PPT-2 | A leaver's access and sessions remained usable for 45 minutes after effective departure. The ticket was eventually closed and called timely.
PPT-3 | A supplier reading sensitive participant records is classified low tier solely because its annual fee is small.
PPT-4 | A report covers a different service and carves out a material hosting provider. Procurement claims it fully assures the purchased processing service and host without further evidence.
PPT-5 | The improvement claim compares the same exercise difficulty and recipient population: reporting rises from 15% to 35% and median reporting time falls from 90 to 20 minutes. The team records limitations and targeted follow-up.
PPT-6 | The exit claim links the termination date to disabled integrations, revoked tokens, verified return and deletion records, and documented backup expiry and legal-hold restrictions.

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 the baseline, then assess each claim within its stated scope.

2. Step 2

   Judge every line, including the boring ones

   Include each row once; some rows are valid evidence rather than defects.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Compare described operations and evidence with the claim. Do not reject an explicitly supported narrow claim because it does not prove every possible control.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Select the root failure category for rejected rows. Leave the reason empty for accepted rows.

   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.