10 exercises — choosing the right wh-word after "no matter" (how for degree/manner, what for open things, who for people, which for a bounded choice), word order, and comma placement.
Quick reference
No matter how + adjective/adverb — degree or manner ("how carefully," "how fast")
No matter what — open-ended thing or action ("whatever")
No matter who — a person, open-ended ("whoever")
No matter which — a choice from a known, bounded set ("whichever")
Word order: statement order after the wh-word, never question inversion
-ever equivalents: however, whatever, whoever, whichever
0 / 24 completed
1 / 24
A senior engineer gives advice in a mentoring session: "___ carefully you review a PR, some bugs will still slip through." Which word correctly completes this concessive structure?
No matter how + adjective/adverb is used when the varying element is a degree or manner ("how carefully," "how fast," "how thorough") — it means "regardless of the degree to which." "No matter how carefully you review a PR, some bugs will still slip through" concedes that even at maximum care, the outcome (bugs slipping through) still holds. "No matter what" pairs with a noun clause or open-ended thing ("no matter what you do"). "No matter which" pairs with a choice among specific options. "No matter who" pairs with a person. Only "how" fits before an adverb of manner/degree like "carefully."
2 / 24
Which sentence uses "no matter what" correctly as a concessive free relative (meaning "regardless of what happens/is chosen")?
"No matter what database we choose, we still need a migration strategy" is correct: "what" here stands in for the open-ended thing being varied (which database), functioning as a determiner before the noun "database." Options B and C wrongly use "what" before an adjective/adverb of degree ("carefully," "fast"), where "how" is required instead ("no matter how carefully," "no matter how fast"). Option D stacks two question words together ("what who"), which is never grammatical — only one wh-word belongs directly after "no matter."
3 / 24
A runbook note reads: "___ deploys the hotfix, they must notify the on-call channel first." Which word fits, since the varying element here is a person?
"No matter who deploys the hotfix, they must notify the on-call channel first" — "who" is the correct choice when the varying element is a person, regardless of their identity. This differs subtly from "no matter which," which implies a choice from a known, often smaller or more defined set: "no matter which engineer is on call, the escalation policy is the same" (implying a defined roster) versus "no matter who deploys" (open-ended, any person at all). "How" and "what" don't fit a person as the varying element.
4 / 24
Which sentence best illustrates the subtle difference between "no matter what" and "no matter which"?
"No matter which" implies a selection from a bounded, often explicitly named set of options ("no matter which cloud provider we pick — AWS, GCP, or Azure"). "No matter what" is more open-ended and doesn't presuppose a fixed list ("no matter what we build," "no matter what happens"). Neither is restricted by animacy (people vs. things) — both can apply to either, though "which" more often implies a countable, listable set. Formality is not the distinguishing factor between them.
5 / 24
Which sentence correctly places the concessive "no matter" clause AFTER the main clause instead of before it?
"The service will keep retrying, no matter how many times the connection drops." When the concessive clause follows the main clause, a comma precedes "no matter" to separate the two clauses — this mirrors the comma rule for other subordinators used post-main-clause ("..., although X" / "..., even though X"). Option B inserts a stray comma inside the fixed phrase itself. Option C fronts the clause but is missing the required comma after it, before the main clause begins. Option D misplaces the comma after "times" instead of before "no matter," breaking the clause boundary.
6 / 24
Which sentence correctly uses "however" as a near-synonym of "no matter how" before an adjective (a more formal, single-word alternative)?
"However carefully you test, edge cases remain" is a correct, more formal alternative to "no matter how carefully..." — in this concessive use (distinct from "however" as a contrast connector meaning "but"), "however" directly precedes the adjective/adverb it modifies, exactly like "no matter how": however + adjective/adverb + subject + verb. Option B breaks this word order by separating "however" from "carefully." Option C wrongly inserts "that." Option D scrambles the phrase entirely with "careful test."
7 / 24
Which sentence contains a grammatical error in the "no matter" structure?
"No matter how thorough is the test suite" is wrong: after "no matter how + adjective," the clause must follow normal statement word order (subject before verb) — "no matter how thorough the test suite is," not inverted question order. This is a common error for learners transferring question-formation instincts into this concessive structure, which never uses subject-verb inversion. The other three sentences all keep correct statement word order after their respective wh-words.
8 / 24
Which sentence correctly uses "no matter" with a full noun clause introduced by "how much" (quantity of an uncountable noun)?
"No matter how much documentation we write..." is correct: "documentation" is an uncountable noun, so it takes "how much," not "how many" (reserved for countable nouns, as in "no matter how many tickets we close"). Option B wrongly pairs the uncountable noun with "how many." Option C additionally and incorrectly pluralizes "documentation" ("documentations"), which is not standard in English. Option D scrambles the word order of "how much" itself.
9 / 24
A postmortem summary reads: "___ we do to harden the retry logic, we cannot fully eliminate duplicate event delivery in a distributed system — it is an inherent trade-off." Which correctly opens this concessive statement?
"No matter what we do to harden the retry logic, we cannot fully eliminate duplicate event delivery..." — "what" fits because the varying element is an open-ended set of actions ("whatever we might do"), not a degree ("how"), a specific bounded choice ("which"), or a person ("whom"). This is a common rhetorical move in postmortems: conceding that no amount of effort changes an inherent architectural trade-off (here, at-least-once delivery implying possible duplicates).
10 / 24
Which explanation of "no matter" + wh-word structures as a family is most accurate?
"No matter how/what/who/which" forms a family that closely parallels the "-ever" compounds: no matter how ≈ however; no matter what ≈ whatever; no matter who ≈ whoever; no matter which ≈ whichever. Each selects its wh-word based on what kind of variable is being conceded: degree/manner (how), open thing/action (what), person (who), or bounded choice (which). These structures are common in both spoken and written technical English — postmortems, runbooks, and architecture docs all use them freely. They are not restricted to negative sentences, and no "that" clause follows "no matter" — the wh-clause itself is the object.
11 / 24
Senior Engineer: 'No matter how many times you test this function, it's going to throw an exception eventually.' What word best completes the sentence, reflecting a realistic code review comment?
This scenario tests understanding of 'no matter how' in a common code review context. The phrase highlights an unavoidable issue, regardless of the effort invested. 'Although' and 'despite' are often confused with 'no matter how'; 'even if' is too conditional, and 'unless' implies a specific condition for failure.
12 / 24
API Response: 'The system will automatically roll back the changes no matter which user initiates the deployment.' What does this response indicate about the system's behavior?
This tests understanding of 'no matter which' in an API context. The response emphasizes that the rollback action is independent of *who* triggers the deployment. It's a crucial detail when designing resilient systems. Options 1 and 3 imply conditional behavior; option 4 is grammatically incorrect.
13 / 24
Mark: 'I'm working on the database migration no matter how much data we lose during the process.' What does Mark mean in this stand-up update?
This tests 'no matter how much' with a full noun clause. Mark acknowledges that some data loss is inevitable regardless of the *quantity* lost during the migration. This highlights an inherent trade-off in database operations and demonstrates appropriate technical vocabulary for a standup discussion.
14 / 24
Senior Engineer: 'No matter how many times you test this function, it's going to throw an exception eventually.' What word best completes the sentence, reflecting a realistic code review comment?
This scenario tests understanding of 'no matter how' in a common code review context. The phrase highlights an unavoidable issue, regardless of the effort invested. 'Although' and 'despite' are often confused with 'no matter how'; 'even if' is too conditional, and 'unless' implies a specific condition for failure.
15 / 24
API Response: 'The system will automatically roll back the changes no matter which user initiates the deployment.' What does this response indicate about the system's behavior?
This tests understanding of 'no matter which' in an API context. The response emphasizes that the rollback action is independent of *who* triggers the deployment. It's a crucial detail when designing resilient systems. Options 1 and 3 imply conditional behavior; option 4 is grammatically incorrect.
16 / 24
Mark: 'I'm working on the database migration no matter how much data we lose during the process.' What does Mark mean in this stand-up update?
This tests 'no matter how much' with a full noun clause. Mark acknowledges that some data loss is inevitable regardless of the *quantity* lost during the migration. This highlights an inherent trade-off in database operations and demonstrates appropriate technical vocabulary for a standup discussion.
17 / 24
Senior Engineer: 'No matter how many times you test this function, it's going to throw an exception eventually.' What word best completes the sentence, reflecting a realistic code review comment?
This scenario tests understanding of 'no matter how' in a common code review context. The phrase highlights an unavoidable issue, regardless of the effort invested. 'Although' and 'despite' are often confused with 'no matter how'; 'even if' is too conditional, and 'unless' implies a specific condition for failure.
18 / 24
API Response: 'The system will automatically roll back the changes no matter which user initiates the deployment.' What does this response indicate about the system's behavior?
This tests understanding of 'no matter which' in an API context. The response emphasizes that the rollback action is independent of *who* triggers the deployment. It's a crucial detail when designing resilient systems. Options 1 and 3 imply conditional behavior; option 4 is grammatically incorrect.
19 / 24
Mark: 'I'm working on the database migration no matter how much data we lose during the process.' What does Mark mean in this stand-up update?
This tests 'no matter how much' with a full noun clause. Mark acknowledges that some data loss is inevitable regardless of the *quantity* lost during the migration. This highlights an inherent trade-off in database operations and demonstrates appropriate technical vocabulary for a standup discussion.
20 / 24
Reviewer: 'No matter how many times you refactor this code, it's going to have performance bottlenecks.' What does the reviewer intend to convey about the codebase's inherent characteristics? Consider the nuance of the 'no matter' clause.
The reviewer isn't suggesting a simple fix; they acknowledge that *despite* potential improvements (refactoring), inherent bottlenecks will remain. The 'no matter' clause emphasizes an unavoidable limitation, highlighting a crucial point about architectural choices or technical constraints rather than the developer's skill. Option A is irrelevant to the core meaning of the statement.
21 / 24
Team Lead (Sarah): 'No matter how much we optimize this API endpoint for speed, it's still going to be slow during peak hours. We need to manage expectations.' What is Sarah primarily communicating to the team regarding the API's performance?
Sarah uses 'no matter how much' to acknowledge that optimization efforts won't overcome a fundamental constraint – peak load. The phrase highlights an unavoidable trade-off between speed and scalability. Option A is too extreme; Sarah isn't advocating for a complete redesign. Option D is incorrect as she is not dismissing performance concerns.
22 / 24
Pull Request Description: 'The system will automatically revert the changes no matter how many users simultaneously attempt to deploy.' What does this statement indicate about the deployment strategy and potential conflict resolution?
The 'no matter' clause indicates that the system is designed to handle concurrent operations. It doesn't imply prioritization or a complex queuing process; it simply states that any deployment attempt will trigger a rollback regardless of the number of users involved. Option A and C are incorrect as they misinterpret the intended behaviour. The core point is automated conflict resolution.
23 / 24
Developer (David): 'I'm working on implementing this new feature no matter how much legacy code I have to refactor.' What is David communicating about his current task and its potential impact?
David's use of 'no matter how much' signifies that he's accepting a trade-off: implementing the new feature will inevitably require refactoring existing code. This acknowledges that technical debt might increase but highlights the prioritization of delivering the new functionality. Option B is too negative; David isn't explicitly requesting resources or delaying the feature.
24 / 24
Senior Dev (Emily): 'No matter how much we improve the error handling for this service, some unexpected failures are inevitable.' What is Emily's statement primarily suggesting about the system's design and operational characteristics?
Emily's use of 'no matter how much' indicates an unavoidable limitation due to the system's environment or architecture. It suggests that despite best efforts at improving error handling, certain failures are inherent and cannot be entirely prevented. Option A is overly ambitious; Emily isn't advocating for a complete overhaul. Option D is incorrect – she's not criticizing the current implementation.
What will I practise in ""No Matter How/What/Who" Concessive Clauses — IT English"?
Practice using "no matter how/what/who/which" to build concessive free-relative clauses in postmortems, runbooks, and trade-off discussions, and how they
How many exercises are in this module?
This module has 24 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.