In rollback strategies, how do feature flags relate?

In rollback strategies, how do feature flags relate?

• A. They delete the database changes automatically.
• B. They allow toggling features without rolling back schema changes.
• C. They are unrelated to deployment.
• D. They slow down releases.

Answer: (B)

Feature flags let you turn features on or off without changing code or rolling back database migrations. In rollback strategies, that matters because if something goes wrong, you can disable the feature with a quick flag flip while leaving all code and migrations in place. The database changes stay deployed, but the feature’s behavior is hidden behind the flag, so users don’t experience the problem. This minimizes risk, reduces downtime, and supports safer, faster rollbacks and more controlled releases. Deleting database changes automatically isn’t what flags do, and flags are a deployment tool used to manage releases rather than something unrelated to deployment; they don’t inherently slow down releases.

Feature flags let you turn features on or off without changing code or rolling back database migrations. In rollback strategies, that matters because if something goes wrong, you can disable the feature with a quick flag flip while leaving all code and migrations in place. The database changes stay deployed, but the feature’s behavior is hidden behind the flag, so users don’t experience the problem. This minimizes risk, reduces downtime, and supports safer, faster rollbacks and more controlled releases. Deleting database changes automatically isn’t what flags do, and flags are a deployment tool used to manage releases rather than something unrelated to deployment; they don’t inherently slow down releases.