Specify a controlled replacement release

Objectives

Halcyon Clinics wants a replacement release for its application tier. The release lead says the plan is already an approval and suggests committing state beside configuration because output values are masked. Neither claim satisfies the release policy.

Complete the policy using the fixture's fixed values and safeguards. This is an executable policy specification exercise, not infrastructure provisioning: the evaluator checks the declared release controls, while real enforcement would require a deployment pipeline and backend configuration.

environment: production
replicas: exactly 3
module_revision: tier-4
image_digest: sha256:8a61c4
state: shared protected backend; encryption and locking required; never in source history
approval: independent reviewer; bind approval to saved plan digest
change: replace running instances; do not patch in place
drift: check every 60 minutes; investigate differences before remediation

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

   Identify the release inputs

   Read the required capacity and reusable component revision from the fixture; preserve their types and exact identity rather than using a floating release label.

   Use the exact replica count and pinned module revision

2. Step 2

   Bind the build artifact

   Use the content identity supplied for the approved build, not a human-friendly image nickname.

   Pin the approved image digest

3. Step 3

   Protect the resource map

   Consider confidentiality, concurrent writers, and historical exposure separately. Fill each backend safeguard with an explicit boolean consistent with the policy.

   Protect and serialize state outside source history

4. Step 4

   Connect authorization to execution

   Require separation from the author and identify the content-bound calculation artifact a reviewer must authorize.

   Bind independent approval to the saved plan

5. Step 5

   Choose the update lifecycle

   Describe whether the running units survive the update or are retired in favor of newly built units.

   Use replacement rather than in-place repair

6. Step 6

   Close the comparison loop

   Transfer the mandated cadence in the requested units and state what must happen to an unexpected difference before repair.

   Schedule comparison and investigate differences

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.