What is the best practice for handling feature flags after their rollout?

• A. Maintain flags indefinitely to keep rollback options.
• B. Remove flags before production rollout.
• C. Remove flags after rollout to avoid debt.
• D. Hide flags from the team to prevent confusion.

Answer: (C)

Feature flags are a control mechanism you use during a release to turn features on or off without redeploying. They’re essential for safe gradual rollout and quick rollback, but they also add complexity the longer they stay in the codebase. Keeping flags indefinitely creates ongoing technical debt: every flag adds extra conditional logic, more code branches to test, and more configuration to track, which can drift from the real behavior and complicate future changes. Removing the flag after the rollout cleans up the code path, simplifies testing and monitoring, and reduces maintenance burden. The other options miss this balance: removing flags before rollout takes away the safety net needed during release; keeping flags forever preserves rollback but piles up debt; and hiding flags from the team reduces visibility and increases confusion. So the best practice is to remove flags after rollout to avoid debt.