Intermediate
Grammar
#concession
#cohesion
"Even So" / "Even Then" for Concessive Result
5 exercises — practise introducing a persistent result with "even so" and "even then".
0 / 24 completed
1 / 24
Which sentence correctly uses "even so" to introduce a result that persists despite a stated fact?
"Even so, the p95 latency barely improved" correctly places "even so" as a two-word fixed phrase. Options B, C, and D all reorder or pad the fixed phrase, making it ungrammatical.
2 / 24
Which sentence correctly uses "even then" to show that a result would still fall short even under a stated future condition?
"...might handle Black Friday traffic; even then, a queue could still form..." correctly uses "even then" after the conditional clause to show the limitation persists. Options B, C, and D reorder or pad the fixed phrase incorrectly.
3 / 24
Which sentence correctly distinguishes "even so" (referring back to a fact already true) from "even then" (referring back to a future or hypothetical condition)?
"We already increased the timeout once; even so, requests still fail... even then, a handful of clients..." correctly matches "even so" to the already-true fact and "even then" to the hypothetical future increase. Options B, C, and D swap or merge the two phrases incorrectly.
4 / 24
Which sentence correctly uses "even so" mid-paragraph to concede a persistent problem despite a completed mitigation?
"...the leak was discovered; even so, we are treating every system..." correctly keeps "even so" as a fixed two-word unit with one comma after it. Option B reverses the word order. Option C adds an extraneous "much". Option D wrongly splits the phrase with an internal comma.
5 / 24
Which sentence correctly uses "even then" to show a limitation that would remain true even after a planned future fix?
"...migrate to the new database engine next quarter; even then, the legacy reporting queries will still need..." correctly uses "even then" because the preceding clause describes a future condition, not an already-completed fact. Option B wrongly substitutes "even so", which would require the preceding clause to already be true. Options C and D reorder or pad the phrase.
6 / 24
Reviewer: 'The authentication service is returning 500 errors. We've rolled out the new rate limiting policy.'
Developer (responding in a code review comment): 'Even so,' the errors persist. What's the best way to phrase this response?The phrase 'even so' indicates that despite the implemented rate limiting policy, the problem continues. This is crucial in code reviews – it acknowledges a previously addressed issue hasn't been fully resolved. Option A is too forceful; options C and D propose solutions instead of continuing to highlight the ongoing problem. Option B correctly shows an acknowledgement.
7 / 24
Slack Message from Sarah (Lead Developer): 'Okay team, we've deployed the microservice update to staging. We expect this to significantly improve response times.'
Response from Mark (Junior Dev): 'Even then,' the API is still experiencing latency spikes during peak hours. Which of these options best reflects his concern?'Even then,' indicates Mark is pointing out that the anticipated improvement didn't materialize despite the deployment. This highlights a persistent limitation. Option A suggests a rollback (incorrect), option C demands immediate escalation (unnecessary), and option D ignores the core issue. Option B accurately captures his concern about unmet expectations.
8 / 24
Reviewer: 'The authentication service is returning 500 errors. We've rolled out the new rate limiting policy.'
Developer (responding in a code review comment): 'Even so,' the errors persist. What's the best way to phrase this response?The phrase 'even so' indicates that despite the implemented rate limiting policy, the problem continues. This is crucial in code reviews – it acknowledges a previously addressed issue hasn't been fully resolved. Option A is too forceful; options C and D propose solutions instead of continuing to highlight the ongoing problem. Option B correctly shows an acknowledgement.
9 / 24
Slack Message from Sarah (Lead Developer): 'Okay team, we've deployed the microservice update to staging. We expect this to significantly improve response times.'
Response from Mark (Junior Dev): 'Even then,' the API is still experiencing latency spikes during peak hours. Which of these options best reflects his concern?'Even then,' indicates Mark is pointing out that the anticipated improvement didn't materialize despite the deployment. This highlights a persistent limitation. Option A suggests a rollback (incorrect), option C demands immediate escalation (unnecessary), and option D ignores the core issue. Option B accurately captures his concern about unmet expectations.
10 / 24
Reviewer: 'The authentication service is returning 500 errors. We've rolled out the new rate limiting policy.'
Developer (responding in a code review comment): 'Even so,' the errors persist. What's the best way to phrase this response?The phrase 'even so' indicates that despite the implemented rate limiting policy, the problem continues. This is crucial in code reviews – it acknowledges a previously addressed issue hasn't been fully resolved. Option A is too forceful; options C and D propose solutions instead of continuing to highlight the ongoing problem. Option B correctly shows an acknowledgement.
11 / 24
Slack Message from Sarah (Lead Developer): 'Okay team, we've deployed the microservice update to staging. We expect this to significantly improve response times.'
Response from Mark (Junior Dev): 'Even then,' the API is still experiencing latency spikes during peak hours. Which of these options best reflects his concern?'Even then,' indicates Mark is pointing out that the anticipated improvement didn't materialize despite the deployment. This highlights a persistent limitation. Option A suggests a rollback (incorrect), option C demands immediate escalation (unnecessary), and option D ignores the core issue. Option B accurately captures his concern about unmet expectations.
12 / 24
Reviewer: 'The database migration completed successfully. We've optimized the query structure.'
Developer (responding in a code review comment): 'Even so,' queries are still timing out for users on the east coast. What is the most appropriate phrasing to convey this persistent issue despite the successful migration?
'Even so' is used to acknowledge a previously stated fact (successful migration) while introducing a continuing negative result (query timeouts). Option A misinterprets 'even so' as a judgment of the migration itself. Option B correctly identifies that the problem persists despite the change, mirroring the intended use of 'even so'. Options C and D are irrelevant or incorrectly framed.
13 / 24
Slack Message from David (Senior Architect): 'We've implemented caching for frequently accessed API endpoints. This should dramatically reduce load on the backend servers.'
Response from Emily (Junior Developer): 'Even then,' requests are failing intermittently. What does Emily mean?
Response from Emily (Junior Developer): 'Even then,' requests are failing intermittently. What does Emily mean?
'Even then' indicates that the expected improvement (reduced load) *didn't* occur, despite the implemented caching. Emily is highlighting that the problem persists even after the new solution was deployed. This signals a need for further investigation into the root cause of the intermittent failures.
14 / 24
PR Description: 'We've added support for JWT authentication. This will significantly improve security.'
Reviewer Comment: 'Even so,' unauthorized access attempts are still being logged in the audit trail. What is the most accurate interpretation of this comment?
Reviewer Comment: 'Even so,' unauthorized access attempts are still being logged in the audit trail. What is the most accurate interpretation of this comment?
'Even so' highlights that the intended benefit (improved security) hasn't materialized. The fact that unauthorized access attempts *continue* to be logged suggests that the underlying problem isn't a failure of the JWT implementation but rather some other vulnerability or misconfiguration within the system. Option A is an overstatement; option B suggests a simple fix, and option D offers a potential solution without acknowledging the core issue.
15 / 24
Standup Update from Ben (DevOps Engineer): 'We've upgraded the monitoring system to version 3.5. This should provide more granular metrics.'
Response from Chloe (Developer) : 'Even then,' we're still unable to identify the source of the high CPU usage on server X. What does this indicate?
Response from Chloe (Developer) : 'Even then,' we're still unable to identify the source of the high CPU usage on server X. What does this indicate?
'Even then' shows that despite the upgraded monitoring system (providing more granular metrics), the team *still* can't pinpoint the root cause of the CPU usage. This suggests a lack of visibility or a different problem entirely – perhaps the metrics aren't relevant to the issue, or our analysis isn't effective.
16 / 24
PR Description: 'We've refactored the user authentication module. This should improve code maintainability.' Reviewer Comment: 'Even so,' users are still experiencing intermittent login failures. Which of the following best represents the meaning of this comment?
Here, "even so" is used to concede a persistent problem (login failures) even after a change (refactoring). It emphasizes that the refactoring didn't fully solve the issue; it's a continuing limitation. Options A and D are incorrect as they misinterpret the use of 'even so'; option B presents an unrealistic assertion.
17 / 24
Standup Update from Emily (QA Engineer): 'We've completed all regression tests on the new payment processing system. The results indicate a stable and reliable system.' Response from John (Developer): 'Even then,' we're still seeing occasional transaction timeouts. What does this mean?
"Even then" indicates that a previously stated positive outcome (stable and reliable system) is not entirely true in practice. The reported transaction timeouts represent a continuing limitation despite the successful testing. Options A and D are inappropriate given the context; option B is an overstatement.
18 / 24
Slack Message from Alex (Senior Backend): 'We've optimized the database indexing for the reporting service. This should drastically reduce query times.'
Response from Ben (Junior Frontend): 'Even then,' users are still reporting slow load times when generating complex reports. What is the most appropriate response?
This tests using 'even then' to indicate a limitation that persists despite an implemented fix. Option A denies any further action. Option B directly connects the problem to another potential cause (frontend caching), which is a logical next step. Option C suggests investigating query execution, and option D escalates unnecessarily.
19 / 24
Standup Update from Chloe (DevOps): 'We've upgraded the Kubernetes cluster to version 1.28. This should improve resource utilization.'
Response from David (Backend Developer): 'Even then,' we're still experiencing occasional pod scheduling failures. What is the best way to phrase this observation?
This question assesses using 'even then' to acknowledge a persistent issue despite an infrastructure change. Option A dismisses the problem. Option B suggests another potential cause. Option C prompts investigation into resource constraints – a logical response, and option D is an extreme reaction.
20 / 24
Reviewer: 'We've implemented comprehensive logging throughout the application.'
Developer (responding in a code review comment): 'Even so,' debugging complex production issues remains difficult. What is the most appropriate response?
This tests 'even then' indicating a remaining challenge despite increased visibility. Option A blames the developers. Option B suggests a complementary solution (tracing), and option C highlights a potential root cause issue – focusing on design rather than just logging. Removing logging would be counterproductive.
21 / 24
Reviewer: 'The API response times have improved after deploying the new caching layer.'
Developer (responding in a Slack message): 'Even so,' some users are still reporting slow page loads. Which of the following responses best acknowledges this situation and suggests next steps?
A) 'That's great news! The caching is definitely working!'
B) 'Even then,' we should investigate further – perhaps there's a bottleneck elsewhere in the system.
C) 'The caching layer is fully implemented, so slow page loads are likely due to user network issues.'
D) 'Let's revert back to the previous version and see if that resolves the issue.'
A) 'That's great news! The caching is definitely working!'
B) 'Even then,' we should investigate further – perhaps there's a bottleneck elsewhere in the system.
C) 'The caching layer is fully implemented, so slow page loads are likely due to user network issues.'
D) 'Let's revert back to the previous version and see if that resolves the issue.'
This question tests understanding of 'Even so' as acknowledging a positive change but recognizing it doesn't fully solve the problem. Option B correctly identifies the need for further investigation – a key aspect of debugging. Options A and C are overly optimistic or dismissive, while option D is a drastic action that shouldn't be taken immediately.
22 / 24
Sarah (Lead Developer): 'We've implemented a new automated testing framework. This should drastically reduce the time spent on manual testing.'
Mark (Junior Dev): 'Even then,' we're still seeing a high number of bugs reported in production. What's the most appropriate response?
A) 'The automated tests are perfectly reliable; the issues must be caused by user error.'
B) 'Even so,' we need to examine the test coverage and ensure it adequately reflects real-world usage scenarios.
C) 'Let's ignore the production bugs – automated testing is always better than manual testing.'
D) 'The new framework has already solved all problems, so there's nothing more we can do.'
A) 'The automated tests are perfectly reliable; the issues must be caused by user error.'
B) 'Even so,' we need to examine the test coverage and ensure it adequately reflects real-world usage scenarios.
C) 'Let's ignore the production bugs – automated testing is always better than manual testing.'
D) 'The new framework has already solved all problems, so there's nothing more we can do.'
'Even so' highlights that a new tool isn't automatically a solution. Option B correctly emphasizes the importance of thorough test coverage. Options A and C are flawed assumptions, while option D is dismissive of critical feedback.
23 / 24
PR Description: 'We've updated the authentication service to use OAuth 2.0 for improved security.'
Reviewer Comment: 'Even so,' we're still receiving reports of unauthorized access attempts. What is the best approach to address this?
A) Ignore the reports – OAuth 2.0 is inherently secure.
B) Even then, we should investigate potential misconfigurations or vulnerabilities in the implementation.
C) Immediately disable all user accounts to prevent further unauthorized access.
D) Assume the users are intentionally trying to break the system.
A) Ignore the reports – OAuth 2.0 is inherently secure.
B) Even then, we should investigate potential misconfigurations or vulnerabilities in the implementation.
C) Immediately disable all user accounts to prevent further unauthorized access.
D) Assume the users are intentionally trying to break the system.
This question focuses on the nuance of 'Even so,' which means a new feature hasn't eliminated all risks. Option B correctly directs attention to potential implementation issues—a common reason for security vulnerabilities. The other options are incorrect and potentially damaging.
24 / 24
Standup Update from Ben (DevOps Engineer): 'We've migrated the database to a cloud-based solution. This should significantly improve scalability.'
Response from Chloe (Developer) : 'Even then,' we're still experiencing occasional performance degradation during peak hours. What is the most constructive action to take?
A) Accept the performance degradation as an unavoidable consequence of cloud migration.
B) Even so, we should investigate potential resource constraints or query optimization opportunities.
C) Immediately revert back to the old database system.
D) Blame the previous development team for poor initial design.
A) Accept the performance degradation as an unavoidable consequence of cloud migration.
B) Even so, we should investigate potential resource constraints or query optimization opportunities.
C) Immediately revert back to the old database system.
D) Blame the previous development team for poor initial design.
'Even so' indicates that a change hasn't entirely resolved an issue. Option B correctly focuses on investigating potential bottlenecks or inefficiencies—a crucial step in performance tuning. The other options represent unproductive responses.
Next up:
More Grammar Exercises →
Frequently Asked Questions
What will I practise in ""Even So" / "Even Then" for Concessive Result — IT Grammar Exercise"?
Practise choosing between "even so" (a fact already true) and "even then" (a future or hypothetical condition) to introduce a result that persists despite a
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.