YAML lab 60 bonus XP

Build the estate evidence index

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. This is project step one: reconcile scope, recovery targets and evidence ownership before issuing conclusions.

Approved requirement and measured facts

Northwind Freight expects 12 nodes; 11 distinct nodes reported. Missing evidence is unknown, not pass. Recovery targets: RPO 60 minutes, RTO 240 minutes. Index needs protected manifest and owner.

Checks the server runs (6)

  • Expected assets meets the incident requirement
  • Observed assets meets the incident requirement
  • Rpo minutes meets the incident requirement
  • Rto minutes meets the incident requirement
  • Evidence meets the incident requirement
  • Missing state 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 expected assets

    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.

    Expected assets meets the incident requirement

  2. Step 2

    Check observed assets

    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.

    Observed assets meets the incident requirement

  3. Step 3

    Check rpo minutes

    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.

    Rpo minutes meets the incident requirement

  4. Step 4

    Check rto minutes

    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.

    Rto minutes meets the incident requirement

  5. Step 5

    Check 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.

    Evidence meets the incident requirement

  6. Step 6

    Check missing state

    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.

    Missing state meets the incident requirement

Rules summary

  • XP on pass

    60 bonus XP the first time every check goes green.

  • Paid hints

    2 available. Each costs 25% of the lab XP (about 15 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.