5 exercises on feature flag management vocabulary.
0 / 5 completed
1 / 5
What is a kill switch in feature flag terminology?
Kill switch (ops toggle): a permanent feature flag designed for rapid response. Unlike release toggles (temporary, removed after graduation), kill switches live indefinitely. They protect system stability. Examples: disable a new payment integration if the third-party service degrades; disable a resource-intensive recommendation algorithm during peak load; switch ML model from v2 back to v1 if v2 shows quality degradation. Kill switch vs circuit breaker: circuit breaker triggers automatically on error thresholds; kill switch is manual. Both are essential resilience tools.
2 / 5
What is flag debt and how does it accumulate?
Flag debt: every flag in the codebase at 100% rollout is dead code waiting to be removed. Costs: Dead code paths: the false branch of a fully-enabled flag is never executed, never tested. Bugs can hide there. Cognitive overhead: every developer reading the code must parse "what is this flag, is it on, what happens if off?". Testing complexity: N flags = 2^N possible code paths. Evaluation failures: if the flag service is unreachable and defaults are wrong, production behavior may be unexpected. Prevention: assign an owner and removal date when creating the flag. Create the removal ticket in the same sprint as the 100% rollout. Treat flag removal as a maintenance task with positive code health ROI.
3 / 5
What is sticky assignment in A/B testing with feature flags?
Sticky assignment: without it, a user might see "new checkout" on Monday and "control" on Wednesday. Their behavior data is polluted. You cannot attribute their conversion to either variant. Implementation: hash(userId + flagKey) → value in [0, 100]. Same inputs = same output. Deterministic without storing per-user state. Assignment is consistent across devices if tied to user ID (not cookie/device ID). Pitfall: if you change the flag key or bucketing logic mid-experiment, existing users get reassigned — experiment is invalidated. A/B testing requirements: sticky assignment, sufficient sample size (power analysis), minimum runtime (2 weeks for weekly seasonality), metric guardrails (ensure no regressions on secondary metrics), statistical significance before calling a winner.
4 / 5
What does trunk-based development have to do with feature flags?
Trunk-based development (TBD): all engineers commit to one main branch, ideally daily. Problem: features take weeks to build — incomplete code cannot be in main if it affects users. Flags solve this: create flag (default off), wrap all new code in flag check, commit daily to main (CI passes because flag is off everywhere), enable in dev/staging when testable, gradual production rollout when complete, remove flag after graduation. Benefits: no long-lived branches (no merge conflicts), CI always runs against integration point, main is always deployable. Complementary: short-lived branches (hours/days for review) are still used. Branch by abstraction: for large-scale refactoring without flags — create abstraction layer, implement new version behind it.
5 / 5
What is progressive delivery and how do feature flags enable it?
Progressive delivery: deployment (code on servers) is separated from release (users see the feature). Techniques: Feature flags: 0% → 1% → 10% → 100% user exposure. Canary release: deploy new version to a subset of servers; route percentage of traffic there. Metric-gated rollout: automated hold at each percentage if error rate or latency regresses. Tools: Argo Rollouts (automated canary analysis), Flagger (GitOps-integrated), LaunchDarkly (flag-based). Dark launch: execute new code path in production, discard the result — test performance without user impact. Ring-based deployment: internal users → beta users → production east → production global. Each ring is a checkpoint.
These modules build the same on-the-job skills as Feature Flag Lifecycle
— work through them together for a fuller vocabulary set.
Feature Flags— useful for Feature flags & parallel development (Full-Stack Developer)
Frequently Asked Questions
What does the "Feature Flag Lifecycle" vocabulary exercise cover?
This exercise tests real IT vocabulary related to feature flag lifecycle through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 1 other vocabulary module. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.