5 exercises — practise forming echo questions and wh-echo questions to confirm surprising statements.
0 / 22 completed
1 / 22
A teammate says: "We're rolling back the entire release." Which echo question correctly asks for confirmation of the surprising part?
An echo question repeats the original statement (with the subject pronoun adjusted) using rising intonation instead of subject-auxiliary inversion, to express surprise or request confirmation. Option B is correct: "You're rolling back the entire release?" — it echoes the statement almost verbatim, only changing "we're" to "you're", and relies on question intonation (shown by the question mark) rather than inversion. Option A uses a wh-echo question ("rolling back what?"), which is a different, valid echo-question type used when only part of the information is in doubt — but it does not confirm the specific fact stated ("the entire release"); it asks the speaker to repeat that part. Option C is a tag question, a different structure entirely. Option D incorrectly inserts "did" while keeping the -ing form, producing an ungrammatical hybrid.
2 / 22
A colleague says: "The vulnerability has been in production for eight months." Which wh-echo question correctly asks the speaker to repeat the surprising detail (the duration)?
A wh-echo question keeps the statement's original word order (no inversion) and simply replaces the surprising element with a wh-word, placed where that element occurred — here, at the end, since "for eight months" was at the end of the original statement. Option A is correct: "It has been in production for how long?" mirrors the statement structure, with "how long" replacing "eight months" in its original position, signaled as a question by intonation/context. Option B is a standard, fully-inverted wh-question ("How long has it been...") — grammatical, but not an echo question; it does not preserve the statement's original word order. Option C incorrectly fronts "for how long" while keeping statement word order, which is not how English forms this echo structure. Option D uses "what" instead of "how long", which does not match the type of information (a duration) being questioned.
3 / 22
In a stand-up, a developer says: "I pushed straight to main without a review." A surprised teammate wants to echo just the surprising action. Which is most natural?
Option A is the most natural full echo question in this context — it repeats the entire statement with rising intonation, expressing genuine surprise while still confirming exactly what was said. Option B is a standard yes/no question with subject-auxiliary inversion — grammatical and usable, but it is not an echo question; it does not have the same rhetorical effect of directly mirroring the surprising statement back. Option C ("You did what?") is a valid, very informal echo question but it questions the entire action generically rather than confirming the specific detail already given — appropriate for extreme disbelief, but less precise/professional than option A for a stand-up. Option D scrambles normal word order and is ungrammatical.
4 / 22
Which sentence correctly identifies the register difference between an echo question and a full inverted question when responding to "The API key was committed to the public repo"?
Option A correctly describes the register distinction: echo questions (statement word order + question intonation) are typically used in spontaneous spoken reactions — expressing surprise, alarm, or seeking immediate confirmation — and feel more informal and emotionally charged. Fully inverted questions ("Was the API key committed...?") are more neutral and are the default choice for formal spoken or written questions, such as in an incident report follow-up. Option B is incorrect because register does differ, even though both are grammatical. Option C is incorrect — the echo question is a complete, grammatically valid sentence in spoken English, not a fragment. Option D is incorrect — echo questions are a spoken/conversational phenomenon primarily, essentially never used in formal written documentation, the opposite of what the option claims.
5 / 22
A PM says: "The client wants the feature by Friday." An engineer wants to echo the statement to express disbelief about the specific deadline. Which is the best wh-echo question?
Option A correctly forms a wh-echo question by keeping the statement's word order intact ("The client wants the feature by...") and substituting the surprising element ("Friday") with the appropriate wh-word ("when") in its original position at the end. This directly signals which piece of information the speaker finds hard to believe. Option B breaks statement word order without applying the subject-auxiliary inversion required for a standard question, making it ungrammatical. Option C is a grammatically correct standard inverted wh-question, but — like earlier examples — it is not an echo question, since it does not mirror the original statement's structure. Option D substitutes "what" for "the feature" instead of "Friday" — the wrong element for expressing disbelief specifically about the deadline.
6 / 22
During a code review, another developer says: 'This function is throwing a NullPointerException.' You want to echo the *specific* error to ensure you understand it correctly. Which of the following questions best achieves this? Focus on repeating the precise technical detail.
This question tests the ability to accurately repeat technical jargon. The incorrect options are too broad or focus on a solution rather than repeating the core problem – the specific error message. Repeating 'What is causing the NullPointerException?' ensures you've understood and can discuss it further.
7 / 22
In a Slack channel discussing a deployment failure, a DevOps engineer writes: 'The servers are down.' You want to echo the severity of the situation. Which question best reflects this? Consider the impact of the statement.
This question assesses understanding of echo questions for conveying urgency. Simply asking 'What's happening with the servers?' directly repeats the key information – the *state* of the servers. The other options are more exploratory or directive, failing to accurately reflect the initial statement's impact.
8 / 22
A senior developer says in a PR review: 'The database connection pool is set to 10.' You notice this might be too low for peak load. Which echo question best expresses your concern? Focus on highlighting a potential issue.
This question tests your ability to frame a concern using an echo question. Repeating 'I'm concerned about the connection pool size' directly addresses your observation and prompts further discussion. The other options are requests for explanation or solutions, not accurate repetitions of the initial statement.
9 / 22
A team lead announces: 'We're deprecating Feature X.' You want to echo just the action being taken. Which question best accomplishes this? Focus on repeating the core action.
This question tests understanding of concise echo questions. Repeating 'We're deprecating Feature X' provides a precise and direct repetition of the announced action. The other options introduce extraneous information or ask for reasons/timing, deviating from the core echo requirement.
10 / 22
During a code review, another developer says: 'This function is throwing a NullPointerException.' You want to echo the *specific* error to ensure you understand it correctly. Which of the following questions best achieves this? Focus on repeating the precise technical detail.
This question tests the ability to accurately repeat technical jargon. The incorrect options are too broad or focus on a solution rather than repeating the core problem – the specific error message. Repeating 'What is causing the NullPointerException?' ensures you've understood and can discuss it further.
11 / 22
In a Slack channel discussing a deployment failure, a DevOps engineer writes: 'The servers are down.' You want to echo the severity of the situation. Which question best reflects this? Consider the impact of the statement.
This question assesses understanding of echo questions for conveying urgency. Simply asking 'What's happening with the servers?' directly repeats the key information – the *state* of the servers. The other options are more exploratory or directive, failing to accurately reflect the initial statement's impact.
12 / 22
A senior developer says in a PR review: 'The database connection pool is set to 10.' You notice this might be too low for peak load. Which echo question best expresses your concern? Focus on highlighting a potential issue.
This question tests your ability to frame a concern using an echo question. Repeating 'I'm concerned about the connection pool size' directly addresses your observation and prompts further discussion. The other options are requests for explanation or solutions, not accurate repetitions of the initial statement.
13 / 22
A team lead announces: 'We're deprecating Feature X.' You want to echo just the action being taken. Which question best accomplishes this? Focus on repeating the core action.
This question tests understanding of concise echo questions. Repeating 'We're deprecating Feature X' provides a precise and direct repetition of the announced action. The other options introduce extraneous information or ask for reasons/timing, deviating from the core echo requirement.
14 / 22
During a code review, another developer says: 'This function is throwing a NullPointerException.' You want to echo the *specific* error to ensure you understand it correctly. Which of the following questions best achieves this? Focus on repeating the precise technical detail.
This question tests the ability to accurately repeat technical jargon. The incorrect options are too broad or focus on a solution rather than repeating the core problem – the specific error message. Repeating 'What is causing the NullPointerException?' ensures you've understood and can discuss it further.
15 / 22
In a Slack channel discussing a deployment failure, a DevOps engineer writes: 'The servers are down.' You want to echo the severity of the situation. Which question best reflects this? Consider the impact of the statement.
This question assesses understanding of echo questions for conveying urgency. Simply asking 'What's happening with the servers?' directly repeats the key information – the *state* of the servers. The other options are more exploratory or directive, failing to accurately reflect the initial statement's impact.
16 / 22
A senior developer says in a PR review: 'The database connection pool is set to 10.' You notice this might be too low for peak load. Which echo question best expresses your concern? Focus on highlighting a potential issue.
This question tests your ability to frame a concern using an echo question. Repeating 'I'm concerned about the connection pool size' directly addresses your observation and prompts further discussion. The other options are requests for explanation or solutions, not accurate repetitions of the initial statement.
17 / 22
A team lead announces: 'We're deprecating Feature X.' You want to echo just the action being taken. Which question best accomplishes this? Focus on repeating the core action.
This question tests understanding of concise echo questions. Repeating 'We're deprecating Feature X' provides a precise and direct repetition of the announced action. The other options introduce extraneous information or ask for reasons/timing, deviating from the core echo requirement.
18 / 22
During a Slack discussion about a recent database migration, Sarah (a junior engineer) writes: 'The migration script failed with a 'connection refused' error.' Mark (a senior engineer) wants to echo the *specific* error to confirm his understanding and suggest a potential cause. Which of the following questions best achieves this?
This question tests echoing a technical detail within a Slack conversation. Option 1 is an overly general suggestion. Option 2 directly echoes the specific error reported by Sarah, which is what Mark needs to confirm his understanding. Options 3 and 4 are too broad and don't focus on repeating the key information. The goal of echoing in this situation is precision.
19 / 22
A PR reviewer comments: 'This code doesn't handle edge cases.' Alex (a developer) wants to echo the feedback to clarify its implications. Which of the following questions best demonstrates this?
Echoing in this scenario focuses on repeating the core concern – the lack of edge case handling. Option 1 prompts further clarification, moving away from a simple echo. Option 2 is the correct direct echo. Options 3 and 4 shift the focus to solutions rather than confirming understanding of the original feedback.
20 / 22
During a standup update, David says: 'I'm working on optimizing the API response time.' Lisa (a team lead) wants to echo just the action being taken. Which of the following questions best accomplishes this?
This question tests echoing a simple action. The correct answer directly repeats David's statement – 'I'm working on optimizing the API response time.' Options 3 and 4 delve into unnecessary detail or potential consequences, which is not what Lisa is seeking in an echo. Option 2 asks for more information, defeating the purpose of a brief, focused echo.
21 / 22
A DevOps engineer posts on Slack: 'The application server is experiencing high CPU utilization.' Ben (a backend developer) wants to echo the severity of the issue. Which question best reflects this?
Echoing a statement about severity requires repeating the core message. Option 1 directly repeats 'The application server is experiencing high CPU utilization.' This emphasizes the impact – high CPU. Options 3 and 4 shift the focus away from the initial statement of concern and towards potential solutions or further investigation, which isn't what 'echoing' should do.
22 / 22
A code reviewer writes: 'The new feature introduces a potential race condition.' Emily (a developer) wants to echo the warning. Which of the following questions best fulfills this purpose?
Echoing a warning about a race condition necessitates repeating the core issue. Option 1 directly echoes 'The new feature introduces a potential race condition.' Options 3 and 4 move beyond simply acknowledging the problem and start suggesting solutions – this is not what an echo question achieves; it's a request for further detail to understand the problem.
What will I practise in "Echo Questions in Technical English — IT Grammar Exercise"?
Practise echo questions like 'You're rolling back the entire release?' and wh-echo questions like 'By when?
How many exercises are in this module?
This module has 22 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.