1 / 5
A flag that instantly disables a risky feature in production is a ___ switch.
-
-
-
-
A kill switch lets you turn off a feature immediately without a deploy, a key safety mechanism for risky launches.
2 / 5
Turning a feature on for 5%, then 25%, then 100% of users is a gradual ___.
-
-
-
-
A gradual ramp exposes the feature to a growing share of users so issues surface at limited blast radius.
3 / 5
Naming a responsible person per flag establishes flag ___.
-
-
-
-
Clear ownership ensures someone is accountable for ramping, monitoring, and eventually removing each flag.
4 / 5
Flags left in the codebase long after launch become ___ flags that add complexity.
-
-
-
-
Stale (zombie) flags clutter code and create risky branching logic; coordinated cleanup is part of healthy flag hygiene.
5 / 5
Coordinating dependent flags so feature A isn't enabled before feature B avoids a ___.
-
-
-
-
When flags depend on each other, teams must coordinate enable order to prevent users hitting an inconsistent, half-enabled state.