hardDesignScenarioSeniorStaffLead
Your pipeline gates every code change. What else reaches production without passing through it?
6 min readUpdated 2026-08-15Target archetype: Big Tech, Enterprise Captive, Product Startup
Answer
Short answer
Configuration, feature flags, content and reference data, schema migrations, infrastructure definitions and dependency updates all change production behaviour, and most organisations ship them through channels that were designed to be faster than the release pipeline.
Was this answer helpful?
Likely follow-ups
- How would you test a feature flag combination when there are twenty flags?
- A schema migration is the change. What gate is meaningful for it, and what is theatre?
- Which of these channels would you deliberately leave ungated, and how would you justify it?
- Your gate makes an urgent configuration fix take forty minutes. How do you resolve that tension?
Related questions
- How would you design a deployment pipeline that can be rolled back safely?hardAlso on ci-cd and feature-flags7 min
- Which tests should run on every commit and which should run nightly, and how do you decide?mediumAlso on ci-cd and quality-gates7 min
- A release goes out and afterwards users can see records they were never entitled to. How would you find out, and how long would it take?hardAlso on change-management6 min
- A maintenance script updates your permissions table and every user in one tenant can suddenly edit everything. What should have stopped that, and how would you have found out?hardAlso on change-management6 min