Specify workforce and supplier gates
Objectives
Bracken's manager proposes waiting for monthly account reviews to remove old rights and treating every inexpensive vendor as low tier. Translate the mandatory baseline below into a policy artifact instead.
Fill the YAML using the exact fixture values. This evaluates a declared specification, not live identity systems or supplier enforcement.
Mandatory local baseline
awareness: measure reporting_rate and median_reporting_minutes, not completion alone joiner activation: approved_start mover old-right removal: role_change leaver revocation: departure_time privileged access: separate_identity and time_limited must both be true supplier: participant-record processor has high tier; review every 90 days supplier exit: revoke_access and verify_data_disposition must both be true
Checks the server runs (5)
- Measure reporting behavior and speed
- Bind workforce changes to effective event times
- Separate and time-limit elevated access
- Assign the data-driven tier and review cadence
- Verify access and data disposition at exit
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.
- Step 1
Select outcome measures
Find the two measures that reflect recipients' actions and response speed rather than attendance. Represent them as a list.
Measure reporting behavior and speed
- Step 2
Map the workforce clocks
For each event, identify the effective point when authorization begins, changes, or ends. Use the baseline's machine-readable labels.
Bind workforce changes to effective event times
- Step 3
Constrain elevation
Separate the identity used for routine work from elevated work and decide whether elevation can remain indefinitely. Express safeguards as booleans.
Separate and time-limit elevated access
- Step 4
Scope supplier oversight
Use the sensitivity of the entrusted records to select the tier, then transfer the required cadence in the requested units.
Assign the data-driven tier and review cadence
- Step 5
Close both exit paths
Check that the departing supplier cannot still connect and that retained information has an evidenced disposition. Neither safeguard substitutes for the other.
Verify access and data disposition at exit
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.