A team wants to release a new checkout flow to five percent of users and turn it off within minutes if errors rise, without another build. Which practice enables this?
Show answer and explanation
Answer: C
Feature flags let code ship in a disabled or partially enabled state and be switched on at runtime through configuration. That supports progressive delivery to a percentage of users, targeted rollouts, A/B tests and fast rollback without rebuilding or redeploying. The flag controls exposure to code that is already running in production.
Why the other options are wrong
- A. Dead-code scanning helps remove code that is never used. It does not expose or hide a live feature for a subset of users.
- B. Cost attribution reports spending by feature. It does not control whether users see the feature or allow a quick rollback.
- D. Security labels document risk in code. They do not switch features on or off for users.