Exercises › Progressive Delivery Language › Feature Flags Vocabulary

Feature Flags Vocabulary

5 questions · Progressive Delivery Language

1. A product engineer says: "We use a release toggle to deploy the new checkout flow to production without making it visible to users." What is the purpose of a release toggle?

To control which version of the application is deployed to each environment (dev, staging, production) To decouple code deployment from feature release — the code ships to production but the feature remains hidden until the flag is turned on To toggle between A and B variants of a feature for experimentation purposes

2. An engineer complains: "We have dozens of stale flags in the codebase." What is a stale flag and why is it a problem?

A flag that has been set to 'off' for more than 30 days, wasting evaluation overhead A feature flag whose original purpose is complete (the feature is fully rolled out or permanently disabled) but which has not been removed from the codebase, creating technical debt A flag controlled by a deprecated feature flag service that needs to be migrated

3. A DevOps engineer mentions implementing a kill switch for a new payment integration. What is a kill switch in this context?

A circuit breaker that automatically disables a service when error rates exceed a threshold An operational feature flag that can instantly disable a specific feature or integration in production without a code deployment A security mechanism that terminates all active user sessions when a breach is detected

4. A product manager describes: "We show the new onboarding flow only to users who signed up in the last 30 days and are on a Pro plan." What feature flag concept enables this?

A/B testing with random user assignment Targeting rules — conditions that evaluate user or context attributes to determine whether the flag is on or off for that specific user A permission toggle that restricts feature access based on user roles

5. An engineer explains the flag lifecycle: "We go from create → test → rollout → cleanup." What does the cleanup phase involve?

Archiving the flag configuration in the feature management system for audit purposes Removing the flag from the feature management system and deleting the conditional code branches from the codebase, leaving only the enabled code path Setting the flag to 100% rollout and leaving it in place permanently as documentation

Exercise complete!

out of 5 questions

← Back to Progressive Delivery Language All exercises