Practice feature flag cleanup vocabulary: stale flags, technical debt, flag lifecycle management, 100% rollout cleanup, and flag cleanup sprints.
0 / 10 completed
1 / 10
'We have 47 flags older than 6 months.' These are referred to as _____ flags.
'Stale flags' are feature flags that have not been updated or removed after their purpose was served, accumulating as technical debt in the codebase.
2 / 10
'The flag has 100% rollout — _____ it.' What should be done with a fully rolled-out flag?
When a flag is at 100% rollout and has been stable, the flag and its conditional code should be removed from the codebase — it's no longer needed.
3 / 10
What is a 'flag cleanup sprint'?
A flag cleanup sprint is a focused engineering effort to identify and remove stale, fully-rolled-out, or abandoned feature flags to reduce codebase complexity.
4 / 10
'Stale flag technical _____' — what problem does flag accumulation cause?
'Technical debt' is the correct term — accumulating stale flags makes code harder to read, test, and maintain, and can hide conditional logic bugs.
5 / 10
Which concept describes the full lifecycle of a feature flag from creation to removal?
'Feature flag lifecycle management' covers the entire flag journey: creation, rollout stages, full enablement, and eventual removal from code.
6 / 10
Review Comment: 'Hey team, I'm seeing a lot of these feature-flag-v1 flags lingering around. They haven't been touched in months! It's making it harder to track active experiments and could be causing confusion for new developers joining the project.' What is the primary concern highlighted here regarding these older feature flags?
The comment focuses on the *lack of maintenance* and *reduced visibility* caused by stale feature flags. The concern isn't about performance (though it could be a secondary issue) or the flag's name itself; instead, it's about whether the team is actively utilizing them and understanding their purpose. This highlights the importance of regular flag cleanup to maintain clarity and efficiency.
7 / 10
Slack Message: '@john_doe Just checked the dashboard – we're still seeing a small percentage of users (around 5%) impacted by the old beta-payment-integration flag. It's fully rolled out, but it seems like the rollout wasn't properly deactivated.' What action should Sarah take immediately after receiving this message?
Even though the flag is 'fully rolled out,' it's still impacting users. The crucial step is to *deactivate* the flag – this removes any residual effects and ensures that no further users are affected by an outdated configuration. Simply reverting users would be a dangerous workaround and doesn't address the root cause.
8 / 10
PR Description: 'This PR removes all feature flags associated with the 'Project Phoenix' initiative. These flags were used for A/B testing and have now been superseded by the final product release. The flag cleanup process has been completed.' What does the term 'flag cleanup process' refer to in this context?
The description explicitly states that the flags are being 'removed.' 'Flag cleanup' therefore refers to the systematic process of identifying and deleting feature flags that are no longer needed or actively used – a core part of managing experimentations and preventing technical debt.
9 / 10
Standup Update: 'Yesterday, the team completed a flag cleanup sprint focused on removing flags from the 'User Onboarding' module. We identified and removed 15 stale flags, reducing our total number of active flags by 8%.' What is the primary goal of this 'flag cleanup sprint'?
The standup update clearly indicates that the sprint was *focused on removing stale flags*. This is the core purpose – reducing technical debt and improving code maintainability by eliminating unnecessary complexity. The percentage reduction in active flags is a metric of success for this effort.
10 / 10
API Response:GET /api/feature-flags/{flagId} returns the following data (simplified): { "name": "user_segmentation", "status": "inactive", "rolloutPercentage": 100, "lastTouched": "2021-10-27"}. The `lastTouched` date is over a year old. What does this indicate about the state of this flag?
The `lastTouched` date (over a year ago) definitively indicates that this feature flag is *stale* and no longer relevant. Even though it's fully rolled out, the lack of recent activity makes it a prime candidate for removal as it's contributing to technical debt.
What will I practice in "Feature Flag Cleanup Vocabulary"?
This is a Progressive Delivery Language exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of progressive delivery language 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 10 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 progressive delivery language 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 Progressive Delivery Language exercises?
See the Progressive Delivery Language 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 — progressive delivery language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.