What is a feature flag and how is it used in deployments?

What is a feature flag and how is it used in deployments?

• A. A flag stored in Git to track features.
• B. A security flag that disables features permanently.
• C. A design pattern unrelated to deployments.
• D. A runtime switch to enable/disable features without code changes; allows staged exposure and quick rollback.

Answer: (D)

Feature flags are runtime switches that let you enable or disable a feature without changing code or redeploying. They live in the running application and are controlled by a feature-management system so you can adjust exposure in real time, often targeting specific users or environments. This makes staged rollouts possible—turn the feature on for internal testers, then gradually open it to more users—and supports quick rollback if something goes wrong, simply by flipping the flag off. The other options miss this dynamic, in-production control: storing a flag in Git is just version control and doesn’t affect runtime behavior without a rebuild; a security flag that disables features permanently removes functionality rather than providing reversible, controlled exposure; and a design pattern that isn’t tied to deployments wouldn’t capture how flags are used to release software safely and iteratively.

Feature flags are runtime switches that let you enable or disable a feature without changing code or redeploying. They live in the running application and are controlled by a feature-management system so you can adjust exposure in real time, often targeting specific users or environments. This makes staged rollouts possible—turn the feature on for internal testers, then gradually open it to more users—and supports quick rollback if something goes wrong, simply by flipping the flag off. The other options miss this dynamic, in-production control: storing a flag in Git is just version control and doesn’t affect runtime behavior without a rebuild; a security flag that disables features permanently removes functionality rather than providing reversible, controlled exposure; and a design pattern that isn’t tied to deployments wouldn’t capture how flags are used to release software safely and iteratively.