grceng.academy
YAML lab 40 bonus XP

Repair the migration responsibility map

Start labRead the room

Objectives

Halcyon deploys its own portal code onto a managed runtime. The migration note calls the destination 'SaaS' and marks all controls inherited. The contract actually assigns the operating system and runtime to the provider, while Halcyon maintains application dependencies and tenant accounts.

Complete the map using the fixture, not the migration note. Use customer or provider for owner fields. Name a concrete customer access-review artefact and record whether the provider report alone proves that control. Retain the required review cadence as a number of days.

Contract extract and internal control requirement

service: consumer deploys portal code; provider operates OS and runtime
use: exclusive to Halcyon Clinics
application_dependencies: consumer patches libraries bundled with portal
accounts: consumer approves and revokes tenant access
access_review: every 90 days; retain dated decisions or a dated signed user review
provider_report: physical facilities and managed runtime controls only
migration_note: SaaS; everything inherited

Checks the server runs (6)

  • Service model follows the code deployment boundary
  • Deployment model follows exclusive use
  • Operating-system maintenance follows the contract
  • Dependencies and tenant access keep explicit owners
  • Customer evidence records a dated access decision
  • Cadence and assurance limits match the 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

    Read capability and consumer scope separately

    Ask what the consumer deploys and who may consume this environment. Use those two independent observations rather than treating the migration label as evidence.

    Service model follows the code deployment boundaryDeployment model follows exclusive use

  2. Step 2

    Trace each maintenance action

    For each component, find the contractual actor who can change it. Do not extend a lower-layer maintenance obligation upward to bundled code or account approvals.

    Operating-system maintenance follows the contractDependencies and tenant access keep explicit owners

  3. Step 3

    Choose an artefact with a decision and a date

    An account list alone does not establish that anyone evaluated access. Describe a retained record that shows when an authoriser reviewed the population and decided what should remain.

    Customer evidence records a dated access decision

  4. Step 4

    Check timing and scope

    Copy the interval from the internal requirement using its stated unit. Then compare the report's scope with the tenant control before deciding whether that report could be sufficient by itself.

    Cadence and assurance limits match the 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.