grceng.academy
YAML lab 40 bonus XP

Build the operating systems specification

Start labRead the room

Objectives

The control owner calls the current summary complete because every field has a label. Several labels confuse a technical mechanism with assurance, and missing observations have been treated as passing.

Use the fixture as the authoritative requirement. Replace the empty fields with typed, testable values and identify the evidence needed to substantiate the claim. Do not copy the owner's optimistic summary.

Approved requirement and measured facts

Worker must use a dedicated account without interactive login. Maximum process count is 64. Capture runtime process identity and start time after maintenance.

Checks the server runs (4)

  • Service account meets the incident requirement
  • Interactive login meets the incident requirement
  • Max processes meets the incident requirement
  • Runtime evidence meets the incident requirement

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

    Check service account

    Find the corresponding requirement in the fixture, distinguish an observed fact from an approved limit, and verify the field type and units before submitting. For narrative evidence, name both the technical observation and its independent supporting record.

    Service account meets the incident requirement

  2. Step 2

    Check interactive login

    Find the corresponding requirement in the fixture, distinguish an observed fact from an approved limit, and verify the field type and units before submitting. For narrative evidence, name both the technical observation and its independent supporting record.

    Interactive login meets the incident requirement

  3. Step 3

    Check max processes

    Find the corresponding requirement in the fixture, distinguish an observed fact from an approved limit, and verify the field type and units before submitting. For narrative evidence, name both the technical observation and its independent supporting record.

    Max processes meets the incident requirement

  4. Step 4

    Check runtime evidence

    Find the corresponding requirement in the fixture, distinguish an observed fact from an approved limit, and verify the field type and units before submitting. For narrative evidence, name both the technical observation and its independent supporting record.

    Runtime evidence meets the incident requirement

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.