Build fluency in the vocabulary of extracting an interchangeable algorithm behind a common interface swappable at runtime.
0 / 5 completed
1 / 5
At standup, a dev mentions extracting an interchangeable algorithm into its own object behind a common interface, so calling code can swap in a different algorithm at runtime without changing the code that uses it. What is this design pattern called?
The strategy pattern is exactly this: the strategy pattern extracts an interchangeable algorithm into its own object behind a common interface, so calling code depends only on that interface and can swap in a different concrete algorithm at runtime without changing the code that uses it. A hash collision is an unrelated hash-table concept about two keys sharing a bucket. This extract-the-algorithm-behind-a-common-interface approach is exactly why the strategy pattern lets new algorithm variants be added without touching the code that selects and uses them.
2 / 5
During a design review, the team applies the strategy pattern to a feature that must support several interchangeable algorithms chosen at runtime, specifically because swapping algorithm objects behind a common interface avoids a long conditional branch selecting behavior by type. Which capability does this provide?
The strategy pattern here provides Runtime-swappable algorithms without conditional branching, since calling code depends only on the common interface, and adding a new algorithm variant means adding a new implementation of that interface instead of adding another branch to a growing conditional. A long conditional branch selecting behavior by type must be edited every time a new algorithm variant is added, and tends to grow unwieldy. This swap-behind-a-common-interface behavior is exactly why the strategy pattern is favored whenever several interchangeable algorithms must be selected at runtime.
3 / 5
In a code review, a dev notices a feature that must support several interchangeable algorithms selects behavior through a long conditional branch checking a type flag, instead of extracting each algorithm into its own object behind a common interface. What does this represent?
This is a missed strategy-pattern opportunity, since extracting each algorithm into its own object behind a common interface would let a new variant be added without touching the growing conditional branch. A cache eviction policy is an unrelated concept about discarded cache entries. This long-conditional-branch pattern is exactly the kind of maintenance risk a reviewer flags once several interchangeable algorithms are selected by a type check.
4 / 5
An incident report shows adding a new algorithm variant required editing a long, growing conditional branch and accidentally broke an unrelated existing branch, because behavior was selected through that conditional instead of extracting each algorithm behind a common interface. What practice would prevent this?
Introducing the strategy pattern lets a new algorithm variant be added as an independent implementation of the common interface, without touching existing branches. Continuing to select behavior through a long, growing conditional branch regardless of how many interchangeable algorithm variants the feature ends up supporting is exactly what caused the issue described in this incident. This strategy-based approach is the standard fix once a conditional branch selecting algorithm variants grows large enough to be risky to edit.
5 / 5
During a PR review, a teammate asks why the team reaches for the strategy pattern instead of simply adding another branch to the existing conditional whenever a new algorithm variant is needed. What is the reasoning?
The strategy pattern extracts each algorithm behind a common interface, so a new variant is added independently without touching existing code, while extending a conditional branch is simpler for one or two variants but grows unwieldy and riskier to edit as more variants are added. This is exactly why the strategy pattern is favored once several interchangeable algorithms are expected, while a simple conditional remains fine for just one or two fixed variants.
What does the "Strategy Pattern Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to strategy pattern vocabulary 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 7 other vocabulary modules. 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.