grceng.academy
Review lab 40 bonus XP

Review the evidence architecture

Start labRead the room

Objectives

A team presents the evidence architecture for one SOC 2 control family ahead of the readiness assessment. The demo works and the diagram is excellent.

Accept the design decisions that will survive an auditor. Reject the ones that only survive a demo.

Verdicts are accept or reject. Every rejection needs one reason code from: mutable-store | period-gap | not-reperformable | no-control-id.

Architecture review packet: decisions under review

J-1  The catalog control id is written into collector output, monitor records and every row of the report.
J-2  Collectors hold write and delete permissions on the evidence bucket so bad runs can be re-collected over the top.
J-3  Each stored payload carries run metadata: run id, query issued, window covered and records evaluated.
J-4  Automation goes live 1 May for a January-December period; no bridge is planned for January to April.
J-5  Report figures are produced by a notebook on one engineer's laptop joining four sources with local credentials.
J-6  The monitor identifies checks by an internal numeric key; nothing maps it to the catalog.

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.

  1. Step 1

    Read the request before the artefact

    Judge each decision against one question: given a control id and a date, could someone who has never met this team reach the artefact and re-derive the number?

  2. Step 2

    Judge every line, including the boring ones

    Six decisions, six verdicts. The two accepts are the join key and the run metadata; leaving them unremarked invites a refactor that quietly drops them.

    Every line in the fixture carries a verdict

  3. Step 3

    Separate what is wrong from what is merely ugly

    A store the collector can overwrite cannot support a claim about the past, no matter how good the hashing is around it.

    Separate the two coverage failures: one is about a period nothing evidences, the other about a number nobody but its author can produce.

    Accept and reject land on the right lines

  4. Step 4

    Say why, in the vocabulary the programme uses

    Use the join-key code for the layer that names things its own way, and the reperformance code for the figure trapped in a personal notebook.

    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.