grceng.academy
Review lab 40 bonus XP

Re-file a governance library

Start labRead the room

Objectives

The governance library has been reorganised by someone who filed by tone of voice: anything that sounded firm went in the policy, anything with numbers went in the standard, anything with steps went in the procedure.

Accept the statements that sit in the right document. Reject the ones that were filed by tone rather than by function, and name where they belong.

Verdicts are accept or reject. Every rejection needs one reason code from: belongs-in-policy | belongs-in-standard | belongs-in-procedure.

Library after the reorganisation

P-1  POLICY: The organisation protects production systems from unauthorised access.
P-2  POLICY: Passwords must be at least 14 characters and rotated every 180 days.
P-3  STANDARD: TLS 1.2 or higher is required on all external endpoints.
P-4  STANDARD: The CISO owns this policy and reviews it annually.
P-5  PROCEDURE: To onboard a vendor, raise a ticket, attach the DPA and await security sign-off.
P-6  PROCEDURE: All staff shall act in the interests of customer confidentiality at all times.

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

    The test is not how the sentence sounds; it is what breaks when the sentence changes. A number that changes every year should not force a board-approved document through re-approval.

  2. Step 2

    Judge every line, including the boring ones

    All six lines need a verdict, including the ones that are already in the right place. Half a re-filing is worse than none: it implies the rest was checked.

    Every line in the fixture carries a verdict

  3. Step 3

    Separate what is wrong from what is merely ugly

    For each line ask: who approves a change to this, and how often will it change? Intent changes rarely and is approved high. Thresholds change with technology. Steps change with tooling.

    One line is a governance statement about ownership and review: decide which document is supposed to carry that kind of statement.

    Accept and reject land on the right lines

  4. Step 4

    Say why, in the vocabulary the programme uses

    Your reason code is a destination, not an insult. Say where the statement should live, and the fix becomes a move rather than a debate.

    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.