1. Guardrails vs Gates intermediate

    A platform has a policy check that warns when a service lacks resource limits, readiness probes or an owner label. 140 of 200 services fail at least one check. The security team asks for it to become blocking next week. What happens if you do, and what would you do instead?

    2 min answer policyenforcementmigrationexemptions
  2. Guardrails vs Gates intermediate

    A platform team must ensure services meet security and observability requirements. Should that be a gate or a guardrail?

    2 min answer hasuraguardrailsgatesdefaults
  3. Guardrails vs Gates advanced

    An interviewer gives you this - "Every service has to propagate W3C trace context. You have 200 services across 6 languages and no authority to mandate anything. Get me to full coverage, and tell me how you would know you got there." Walk through it.

    3 min answer guardrailstracingadoptiondefaults
  4. Guardrails vs Gates advanced

    Shopify's engineering blog introduced Packwerk as a static-analysis gem that enforces package boundaries inside its Rails monolith. Its README states that Packwerk only cares about static constant references and that method calls and objects passed around the application are completely ignored. What does that design buy a platform team that wants to run the check as a blocking gate, and where would copying it be a mistake?

    3 min answer shopifypackwerkguardrailsstatic analysis
  5. Guardrails vs Gates advanced

    When should a platform prevent an action automatically, and when should it require a human decision?

    2 min answer guardrailsgatespreventionscale
  6. Guardrails vs Gates intermediate

    Your architecture review board is a three-week queue. Half the submissions are checking things like region, encryption and tagging. Redesign the process.

    2 min answer governanceautomationreview