Review the change-control evidence

Objectives

The release manager labels every entry compliant because all six mention code or images. Review each entry as a separate claim against the control baseline; do not infer missing safeguards from another entry.

The baseline requires confidential state, approval of the exact applied plan, investigation of unauthorized drift, and replacement-based immutable updates. Reject violations using the single closest reason code; accept evidence that explicitly satisfies its claim.

Verdicts are accept or reject. Every rejection needs one reason code from: state-exposure | approval-mismatch | drift-adoption | mutable-update.

CI-1 | State download is open to all staff; generated credentials remain in the file. Terminal masking is cited as protection.
CI-2 | Plan digest A was approved. New inputs produced digest B, which was applied without another review.
CI-3 | A public administration rule appeared without approval. The team copied it into configuration solely to silence the comparison alert.
CI-4 | The immutable-update claim relies on operators patching every running instance in place while keeping the original image label.
CI-5 | The authorization claim links a reviewed source revision and saved plan digest to an independent approver and matching deployment receipt; logs show no bypass.
CI-6 | The replacement claim links a scanned image digest to new healthy instances, traffic cutover, and retirement of old instances; durable data stayed external.

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 before judging the claims. Treat each row as a separate evidence assertion with its own scope.

2. Step 2

   Judge every line, including the boring ones

   Account for every fixture row once, including rows that provide convincing evidence rather than a defect.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Compare actual operations with the baseline. A familiar artifact name cannot compensate for a contradictory operation, while explicit matching evidence should not be rejected for hypothetical omissions outside its claim.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Choose the root failure category rather than a downstream consequence. Leave the explanation field empty for a claim that meets its stated control.

   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.