Why are feature flags useful in multi-environment configurations?

• A. They allow enabling or disabling features without code changes per environment.
• B. They increase coupling between environments.
• C. They replace the need for environment-specific settings.
• D. They are only used in production.

Answer: (A)

Feature flags give you runtime control over which features are active without changing code or redeploying. In multi-environment configurations, this means you can tailor what’s enabled in each environment independently—turn a feature on in staging for testers, keep it off in production until it’s ready, and flip it on for a region without a new deployment. This separation of release decisions from code changes makes rollouts safer and faster, and it makes rollback simple if something goes wrong. It also supports gradual rollout and experimentation as part of the same mechanism. They aren’t a blanket replacement for environment-specific settings, and they don’t inherently increase coupling between environments; flags are managed per environment and can apply across development, testing, and production as needed.