1. Policy as Code advanced

    A platform team's policy-as-code library has 240 rules. 190 are warn-only because teams objected to blocking. Pipeline output runs to 300 lines and nobody reads it. Two recent incidents were caused by conditions that rules 14 and 87 had been warning about for months. Review this. What would you remove, what would you change, and what would you keep?

    3 min answer policy-as-codegovernancealert-fatigueadmission-control
  2. Policy as Code advanced

    An admission policy requires that every image have a vulnerability scan with no critical findings, and the admission controller calls the scanner's API at admission time to check. The control works. What has the team bought, what are they paying, and when does the bill arrive?

    3 min answer policy-as-codeadmission-controlattestationcoupling
  3. Policy as Code advanced

    Review this. An admission policy blocks any image lacking a signed provenance attestation, verified against a key held in the cluster's secret store. 94% of deployments pass on the first attempt, no attestation has been rejected in two quarters, and teams may register self-hosted build runners with the same build system. What would you change, what would you remove, and what would you leave alone?

    3 min answer provenanceadmission-controlslsabuilder-identity
  4. Policy as Code advanced Multiple choice

    Your admission-time policy engine becomes unavailable during a deployment window. Should admission fail open - allow the change - or fail closed - block it?

    3 min answer policy-as-codeadmission-controlavailabilityfail-safe