What is the recommended approach to deploying new features using feature flags?

• A. Enable features without flags to avoid debt.
• B. Test only in production and ignore flag states.
• C. Gate new features behind flags; test both states, roll out gradually, and remove flags after rollout to avoid debt.
• D. Keep flags forever to allow quick toggles.

Answer: (C)

Feature flags let you gate a new feature behind a toggle, so you can control who sees it and how it behaves without redeploying. Testing both states—when the feature is off and when it’s on—helps verify that the existing system remains stable with the feature disabled and that the new behavior works correctly when enabled. Rolling out the feature gradually to a limited set of users lets you observe real-world impact, metrics, and potential issues before a full release. Removing the flags after the rollout avoids technical debt, because lingering flags add complexity and potential confusion in the codebase. Keeping the feature behind a flag forever defeats the purpose of a clean, maintainable deployment process.