Kill switch, gradual rollout, canary release, flag lifecycle vocabulary for controlled feature releases. Intermediate
0 / 14 completed
1 / 14
A senior engineer says: "The team uses a kill switch for the payment redesign feature."
What does "kill switch" mean in feature flag vocabulary?
A kill switch is a feature flag specifically designed for fast disablement — flipping it to "off" immediately stops the feature for all users without needing a deployment. This is different from a rollback, which reverts code.
Term
Meaning
kill switch
Feature flag with a fast disable path — turns off a feature instantly without deployment
flag toggle
The act of switching a feature flag on or off
kill switch vs. rollback
Kill switch disables the feature; rollback reverts the entire code version
flag management service
Tools like LaunchDarkly, Unleash, or Flagsmith that manage flag state and targeting
2 / 14
A release engineer says: "We're doing a percentage-based rollout — the flag is enabled for 5% of users."
What is the key benefit of a percentage-based (gradual) rollout compared to an immediate full release?
A gradual rollout (percentage-based) limits blast radius — if the feature causes errors, only the small exposed cohort is affected. The team can observe metrics (error rate, latency, conversion) before increasing exposure.
Term
Meaning
exposure percentage
The fraction of users receiving the new feature (e.g. 5%, 20%, 100%)
rollout cohort
The subset of users selected for each rollout increment
blast radius
Scope of impact if the feature fails — gradual rollout minimises this
full general availability (GA)
The point when the feature is enabled for 100% of users
3 / 14
A feature flag has a targeting rule: user.plan === 'enterprise'.
What is this type of flag targeting called?
Flag targeting rules allow you to direct a feature to specific user segments based on attributes: plan type, region, user ID, email domain, or custom properties. This is different from a percentage rollout (random sample) or a canary (traffic percentage).
Term
Meaning
targeting rule
A condition that determines which users receive a feature (attribute-based)
user segment
A group of users sharing common attributes used for targeting
cohort targeting
Enabling a feature for a pre-defined named group or cohort
gradual rollout by segment
Combining segmentation with a percentage rollout within a specific segment
4 / 14
A product manager asks the team to "dark launch" the new search service before the official release.
What does "dark launch" mean in feature flag vocabulary?
A dark launch means the feature code runs in production and processes real requests — but results are not shown to users. The purpose is to test performance, correctness, and production load without any user-facing risk.
Term
Meaning
dark launch
Feature runs in production on real traffic but output is hidden from users
shadow traffic
Real production traffic mirrored to the new service for testing without user impact
traffic mirroring
Duplicating live requests to a new service to validate behaviour under real load
production readiness testing
Validating that a feature handles real-world load and scale before user exposure
5 / 14
A tech lead announces: "The stale flag cleanup sprint removed 47 feature flags from the codebase."
Why is managing the lifecycle of feature flags important?
Flag debt is a real risk: old flags create dead code paths, create conflicting interactions, and nobody knows their original purpose. Security risks arise when old flags bypass access controls that were later added.
Term
Meaning
flag lifecycle
The stages of a feature flag: created → enabled → rolled out → permanent or removed
flag obsolescence
A flag that is no longer needed but remains in the codebase — a source of confusion
temporary vs. permanent flags
Release flags (temporary, remove after full rollout) vs. ops flags (permanent kill switches)
flag cleanup
Removing the flag and the associated conditional code once the rollout is complete
6 / 14
Sarah (a junior developer) mentions to the team that they're using a 'feature flag' to control access to the new analytics dashboard. 'We need to decouple deployment from release,' she explains. Which of the following best describes the primary purpose of this feature flag in this context?
Feature flags aren't just about 'on/off' switches; they enable *controlled release*. Sarah's explanation highlights decoupling deployment from release – allowing for testing and experimentation without impacting all users. The core purpose is to manage risk and facilitate phased rollouts.
7 / 14
Mark (a release manager) sends a Slack message: 'Okay team, we're going to use a feature flag to enable the new UI for users in Europe. We'll monitor performance closely and roll it back immediately if anything goes wrong.' What does Mark likely mean by 'roll it back immediately'?
'Roll it back' in this context refers to reverting to a previous state—typically a stable baseline. This is crucial for mitigating risk when deploying new features through feature flags, allowing rapid rollback if issues arise without disrupting all users. It's not about simple disabling or deployment.
8 / 14
David (a code reviewer) comments on a PR: 'This flag targeting rule is great – `user.plan === 'enterprise'`. But how are we going to ensure it's *actually* removed when the feature is no longer needed?'. What is David raising as a key consideration regarding feature flag lifecycle management?
David highlights the importance of feature flag *cleanup*. Simply creating a flag isn't enough; it must eventually be removed when no longer required. Failing to do so leads to technical debt and increased complexity – this is a core principle of effective feature flag management.
9 / 14
Emily (a product manager) asks the team: 'Can we do a dark launch of the new recommendation engine?'. What does 'dark launch' mean in this context?
A 'dark launch' is a deliberate release of a feature to a limited audience (often internal users or a small percentage of customers) *before* it's formally announced. It allows for real-world testing and monitoring without impacting the majority of your user base – minimizing risk.
10 / 14
John, a senior developer, says: 'We're using a feature flag to control access to the new payment processing API for beta testers. It's crucial that we can quickly disable it if there are any issues.' What does 'feature flag' primarily enable in this scenario? It allows us to decouple deployment from release and manage risk during testing.
Feature flags are fundamentally about controlling access and risk. They allow developers to deploy code changes without immediately making them available to all users. This is particularly important during testing phases like beta releases when rapid rollback capabilities are essential for mitigating potential issues. The option accurately reflects this core functionality.
11 / 14
Maria, a release engineer, announces: 'We're implementing a feature flag with a 20% rollout – meaning it's initially enabled for just 20% of our user base. What is the main advantage of this approach compared to releasing the feature to all users at once? It allows us to gather real-world data and identify potential issues before widespread adoption
A percentage-based rollout, or gradual release, minimizes the impact of bugs and performance issues. By initially enabling the feature for only a small subset of users, you can gather valuable feedback, monitor performance metrics, and identify potential problems before they affect your entire user base. This significantly reduces risk.
12 / 14
A code review comment reads: 'The feature flag is controlled by the expression `request.headers['user-agent'] === 'chrome'`. This seems overly specific – how will we handle future changes to Chrome's user agent string? This makes it difficult to maintain and update in the long term
While targeting based on `request.headers['user-agent'] === 'chrome'` might seem convenient initially, it creates a brittle and difficult-to-maintain solution. User agent strings can change frequently (due to browser updates), requiring constant code modifications. A more robust approach would use broader targeting criteria or a configuration system.
13 / 14
During a standup meeting, David says: 'We're using a feature flag to enable the new experimental UI for users in Japan. We'll monitor user engagement and A/B test against the old design.' What does 'feature flag' facilitate in this scenario? It allows us to run controlled experiments and gather data on different UI designs
Feature flags are central to A/B testing and controlled experimentation. By enabling a feature flag for a specific segment (like Japanese users), you can compare the new UI against the existing one, collect user engagement data, and make informed decisions about which design to adopt. This allows for iterative improvements based on real-world feedback.
14 / 14
A Slack message from a tech lead reads: 'Okay team, we're using a feature flag to enable the new search indexing service. We'll monitor query latency and adjust the flag based on performance metrics.' What is the primary purpose of this approach? It allows us to dynamically manage the feature based on its impact on system performance
Using a feature flag to control indexing services enables dynamic management based on performance. By monitoring metrics like query latency and adjusting the flag accordingly, you can ensure that the new service doesn't negatively impact overall system performance – allowing for controlled scaling and optimization.
What will I practice in "Feature Flag Vocabulary Exercises"?
This is a Release Management exercise set. It walks through 14 scenario-based multiple-choice questions built around real usage of release management terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 14 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the release management vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Release Management exercises?
See the Release Management exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — release management vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.