5 exercises — practise negative question forms for gentle suggestions and confirmation in standups and code reviews.
0 / 40 completed
1 / 40
A reviewer wants to gently suggest an alternative approach. Which negative question is grammatically correct?
"Shouldn't we cache..." is the correct negative question form: contracted negative auxiliary ("shouldn't") + subject + base verb. This is a common, softened way to suggest an alternative in code review, implying "I think we should" while inviting disagreement. Option A spells out "should not" before "we", which is grammatically unusual word order for a negative question (native speakers say "Shouldn't we", not "Should not we" — the uncontracted negative question requires "Should we not", not this order). Option C incorrectly adds "to" before the base verb "cache", which is never used after a bare modal. Option D stacks two negatives incorrectly ("Don't shouldn't"), which is doubly ungrammatical.
2 / 40
Which is the correct fully uncontracted (formal) form of "Doesn't this endpoint need authentication?"
"Does this endpoint not need authentication?" is the correct uncontracted negative question: auxiliary ("does") + subject ("this endpoint") + "not" + base verb. In formal/uncontracted negative questions, "not" moves after the subject rather than staying attached to the auxiliary. Option A ("Does not this endpoint...") keeps "not" attached to "does" before the subject, which sounds archaic and is not standard modern English (it was common in older formal English but reads oddly today). Option B scrambles the word order entirely. Option D is not a question at all — it lacks subject-auxiliary inversion and would only work as a question with rising intonation in speech, not in written technical English.
3 / 40
An engineer expresses surprise in a standup: "_____ the migration already finished? I thought it would take all week." Choose the correct negative question opener.
"Hasn't the migration already finished?" is correct because "the migration" is a third-person singular subject, requiring "has" (and its negative contraction "hasn't"), not "have"/"haven't", which is used for plural or first/second-person subjects. Option A ("Haven't") would require a plural or you/I/we subject, which does not match "the migration". Option B ("Has not've") is not a valid contraction in English — you cannot stack "not" and "'ve" this way. Option C ("Doesn't have") incorrectly mixes the present perfect meaning (has it finished) with a "does" auxiliary construction, which does not combine with "finished" correctly here.
4 / 40
Which negative question is the natural way to seek confirmation that a teammate has already reviewed a PR?
"Didn't you already review this PR yesterday?" is correct: past-tense negative auxiliary ("didn't") + subject + base verb ("review"), used to seek confirmation of something the speaker believes to be true. Option A incorrectly pairs the present-tense auxiliary "don't" with the past-tense verb "reviewed" — auxiliaries and main verbs must agree in form (with "did", the main verb reverts to its base form, not the past tense, since "did" itself already carries the past tense). Option C has scrambled word order. Option D incorrectly uses the "-ing" form "reviewing" after "didn't", when the base form "review" is required.
5 / 40
Which negative question best signals mild criticism about a missing test, appropriate for a professional code review comment?
"Shouldn't there be a test covering this edge case?" correctly applies negative-question inversion to the existential "there" construction: negative auxiliary ("shouldn't") + "there" + base verb ("be"). This softly implies "I think there should be a test" while phrasing it as an open question — a common, polite way to flag a gap in a code review. Option A mixes "isn't" (present tense, present state) with "be" (base form), which is grammatically inconsistent — "isn't there a test" would be correct on its own, but not combined with "be". Option B reverses the required order of "there" and "be". Option C breaks the existential "there" pattern entirely and produces an ungrammatical sentence.
6 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
7 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
8 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
9 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
10 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
11 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
12 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
13 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
14 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
15 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
16 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
17 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
18 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
19 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
20 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
21 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
22 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
23 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
24 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
25 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
26 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
27 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
28 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
29 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
30 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
31 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
32 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
33 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
34 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
35 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
36 / 40
Lead Developer: "The new API is returning a 403 error for users with limited accounts. Is this intentional?" Junior Dev: _____ ?
This scenario tests understanding of negative questions related to authorization. Option 1 correctly focuses on whether restrictions are documented, which is a common area of ambiguity. Options 2 and 3 introduce other potential issues (misconfiguration) but don't directly address the core question of authorization requirements.
37 / 40
Backend Engineer (Slack message): "I've deployed the new feature. Can you confirm that the database connection is still active?" Which negative question would be most appropriate to respond with?
This question focuses on verifying deployment success. Option 1 highlights an area where things can go wrong and is relevant to the context of a Slack message. Options 2 and 3 shift the focus to less directly related issues (latency/infrastructure compatibility) while option 1 is the most pertinent.
38 / 40
Tech Lead (Standup Update): "I've been troubleshooting this performance issue. I'm not seeing any obvious bottlenecks in the code. _____ ?"
This scenario tests using negative questions to seek further investigation. Option 1 suggests a common troubleshooting path, while options 2 and 3 address alternative causes of performance problems. The question is framed as seeking confirmation that a basic check has been performed.
39 / 40
Code Reviewer (PR Comment): "The unit tests for this function are missing. _____ ?"
This question assesses negative phrasing used for constructive criticism. Option 1 is a common response when someone defends their code's correctness. The correct answer seeks clarification about the *reason* for the missing tests, not just demanding they be added – key to professional feedback.
40 / 40
Senior Engineer (Slack Message): "I've reviewed the changes. I'm still a little unsure about the handling of error codes in this module. _____ ?"
This question tests using negative questions to express mild concern. Option 1 is appropriate when expressing doubt about adherence to best practices. The correct answer seeks reassurance and a deeper dive into the implementation details, rather than simply demanding more documentation.
What will I practise in "Negative Questions in Technical English — IT Grammar Exercise"?
Practise forming negative questions correctly to suggest alternatives, express surprise, or seek confirmation in standups and code reviews.
How many exercises are in this module?
This module has 40 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.