Review the operating evidence
Objectives
A release coordinator marks all six records compliant because the deployment completed. Review each record against the room's controls; a successful deployment does not waive authority, credential or evidence requirements.
Accept records that demonstrate a safe practice. Reject each unsafe record using the single best reason code: self-approval, irreversible-recovery, credential-exposure, or silent-monitoring.
Verdicts are accept or reject. Every rejection needs one reason code from: self-approval | irreversible-recovery | credential-exposure | silent-monitoring.
Release and runtime review records
AR-1: Release author is the only production approver; approval precedes deployment. AR-2: Independent reviewer approved digest D42; the deployment record contains D42 and the staging test reference. AR-3: Recovery relies only on deploying old code after deleting a column that old code requires; no compatibility test or alternate recovery exists. AR-4: Diagnostic events contain full bearer tokens so support can replay failing requests. AR-5: Service retrieves its scoped production credential at runtime; rotation verifies consumer cutover before revoking the old credential. AR-6: Collector has sent no events for two hours; zero errors is treated as healthy and no telemetry-loss alert exists.
Checks the server runs (3)
- Every line in the fixture carries a verdict
- Accept and reject land on the right lines
- Each rejection cites a valid reason code
Check names are all you see here: the expectations that decide pass or fail, and the reference solution, stay on the server.
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.
- Step 1
Read the request before the artefact
Read each record as a complete claim. Do not assume an omitted compensating control exists.
- Step 2
Judge every line, including the boring ones
Keep one row for every record, including sound practices; check for duplicates or omissions.
Every line in the fixture carries a verdict
- Step 3
Separate what is wrong from what is merely ugly
Ask whether each practice constrains authority, preserves recovery, protects credentials or verifies collection health. Distinguish a tested linkage from an unsupported assurance.
Accept and reject land on the right lines
- Step 4
Say why, in the vocabulary the programme uses
For each rejected record, identify the violated control and choose the corresponding code from the provided vocabulary. Do not reject merely because a record is brief.
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.