5 exercises — using must, can't, must have, should have, and can for epistemic deduction in debugging sessions, code reviews, and incident post-mortems.
0 / 20 completed
1 / 20
During a debugging session, a developer says: "The memory usage spiked at exactly 3 AM every night — it _____ be the scheduled batch job." Which modal expresses a confident logical deduction?
Must expresses near-certain logical deduction based on evidence. When you say "It must be the batch job," you are reasoning from strong evidence (the timing pattern) to a conclusion. This is epistemic modality — using modal verbs to express degrees of certainty rather than permission or obligation. Might and could express weak possibility — appropriate when the evidence is thin. Should expresses expectation or prediction ("It should work"), not deduction from evidence. In debugging and incident analysis, choosing the right modal signals exactly how confident you are in your conclusion.
2 / 20
A code reviewer comments: "The test suite passed, but the production error persists — the bug _____ be in the test environment configuration, not the application code." Which modal is correct?
Cannot (or can't) is used for negative logical deduction — concluding that something is impossible based on evidence. The reasoning: if the test suite passed but production still fails, the bug logically cannot be in the application code alone. Must not is used for prohibition or strong advice: "You must not commit secrets." It is NOT used for negative deduction. Should not expresses expectation: "This should not happen."May not expresses weak possibility: "It may not be the cause" — this is a possibility, not a deduction. The deduction pair is: positive = must, negative = cannot / can't.
3 / 20
An incident report reads: "The database was unresponsive for 45 minutes. The on-call engineer _____ missed the PagerDuty alert." Which modal best expresses a past deduction?
Must have + past participle is the structure for deduction about a past event. "The engineer must have missed the alert" means: based on the evidence (45-minute outage with no response), I conclude this almost certainly happened. Should have expresses past obligation or criticism: "The engineer should have responded faster" (they had a duty to, but did not). Would have expresses a hypothetical result in a conditional: "If they had seen the alert, they would have responded."Could have expresses past ability or possibility: "The engineer could have missed it" (it is a possibility, less certain than "must have"). In post-mortems, modal perfect forms are essential.
4 / 20
A DevOps engineer writes in an SRE postmortem: "The deployment pipeline _____ been configured incorrectly — three separate services failed in the same sequence." Which form is correct?
Must have been configured is the correct past deduction form. The pattern is: modal + have + past participle. The evidence (three services failing in the same sequence) strongly supports a single root cause — a misconfiguration. This high-confidence deduction requires "must have." Might is a present-tense possibility modal and cannot directly express past deduction in this context without "have" ("might have been" would be possible but weaker). Should have implies the configuration ought to have been done correctly — a criticism, not a deduction. Could alone is present tense ability, not a past deduction.
5 / 20
A developer is uncertain about a race condition: "Two threads accessing the same variable simultaneously _____ cause unpredictable behaviour, depending on the scheduler." Which modal is most appropriate?
Can is the correct modal for expressing theoretical possibility or capability — something that has the potential to happen under certain conditions. "Two threads can cause unpredictable behaviour" means: this is a known possible outcome, not a guaranteed one. The phrase "depending on the scheduler" confirms it is conditional. Must would imply it always happens with certainty. Will would state it as a definite outcome every time. Shall is archaic in technical English except in formal contracts and is inappropriate here. In technical documentation about race conditions, concurrency bugs, and edge cases, can is the go-to modal for expressing potential without overstating certainty.
6 / 20
During a performance investigation, a developer noticed intermittent latency spikes. They hypothesized: 'The database connection pool _____ be the bottleneck.' Which modal best expresses this confident deduction?
'Must be' indicates a strong belief based on evidence. The developer is confidently concluding that the connection pool is causing the problem. 'Should have been' suggests a recommendation rather than deduction, and 'could be' or 'might be' express uncertainty.
7 / 20
A code reviewer found an unexpected null pointer exception. They commented: 'The service isn't handling the case where the input data is missing — it _____ be a missing validation check.' Which modal correctly expresses this deduction?
'Must have been' indicates the reviewer believes it is definitively true. The scenario points to a logical conclusion given the observed error. 'Should have been' suggests a recommendation and 'can be' or 'might have been' express uncertainty.
8 / 20
A Slack message from a senior engineer reads: 'The API endpoint returned a 503 error during peak hours — the load balancer _____ be experiencing throttling.' Which modal best conveys this deduction based on observed symptoms?
'Must have been' indicates a strong belief given the evidence (503 error during peak hours). The load balancer is the most likely culprit based on this information. 'Could be' or 'might be' express possibility without certainty.
9 / 20
A developer writing a PR description states: 'The error occurred only when the user uploads a file larger than 10MB — the code _____ be failing to handle large files correctly.' Which modal is appropriate for this deduction?
'Must have been' suggests a strong belief based on the specific condition under which the error occurs. This implies that the code's handling of large files is indeed flawed. 'Should be' would suggest a recommended change.
10 / 20
A standup update from a developer says: 'I noticed the build times were significantly longer after the recent dependency upgrade — the caching mechanism _____ be broken.' Which modal best expresses this deduction about the system's behaviour?
'Has to be' is a strong statement of belief based on observed changes in build times. The broken caching mechanism is the most logical explanation for the increased duration. 'Could be' or 'might be' express possibility without certainty.
11 / 20
During a performance investigation, a developer noticed intermittent latency spikes. They hypothesized: 'The database connection pool _____ be the bottleneck.' Which modal best expresses this confident deduction?
'Must be' indicates a strong belief based on evidence. The developer is confidently concluding that the connection pool is causing the problem. 'Should have been' suggests a recommendation rather than deduction, and 'could be' or 'might be' express uncertainty.
12 / 20
A code reviewer found an unexpected null pointer exception. They commented: 'The service isn't handling the case where the input data is missing — it _____ be a missing validation check.' Which modal correctly expresses this deduction?
'Must have been' indicates the reviewer believes it is definitively true. The scenario points to a logical conclusion given the observed error. 'Should have been' suggests a recommendation and 'can be' or 'might have been' express uncertainty.
13 / 20
A Slack message from a senior engineer reads: 'The API endpoint returned a 503 error during peak hours — the load balancer _____ be experiencing throttling.' Which modal best conveys this deduction based on observed symptoms?
'Must have been' indicates a strong belief given the evidence (503 error during peak hours). The load balancer is the most likely culprit based on this information. 'Could be' or 'might be' express possibility without certainty.
14 / 20
A developer writing a PR description states: 'The error occurred only when the user uploads a file larger than 10MB — the code _____ be failing to handle large files correctly.' Which modal is appropriate for this deduction?
'Must have been' suggests a strong belief based on the specific condition under which the error occurs. This implies that the code's handling of large files is indeed flawed. 'Should be' would suggest a recommended change.
15 / 20
A standup update from a developer says: 'I noticed the build times were significantly longer after the recent dependency upgrade — the caching mechanism _____ be broken.' Which modal best expresses this deduction about the system's behaviour?
'Has to be' is a strong statement of belief based on observed changes in build times. The broken caching mechanism is the most logical explanation for the increased duration. 'Could be' or 'might be' express possibility without certainty.
16 / 20
During a performance investigation, a developer noticed intermittent latency spikes. They hypothesized: 'The database connection pool _____ be the bottleneck.' Which modal best expresses this confident deduction?
'Must be' indicates a strong belief based on evidence. The developer is confidently concluding that the connection pool is causing the problem. 'Should have been' suggests a recommendation rather than deduction, and 'could be' or 'might be' express uncertainty.
17 / 20
A code reviewer found an unexpected null pointer exception. They commented: 'The service isn't handling the case where the input data is missing — it _____ be a missing validation check.' Which modal correctly expresses this deduction?
'Must have been' indicates the reviewer believes it is definitively true. The scenario points to a logical conclusion given the observed error. 'Should have been' suggests a recommendation and 'can be' or 'might have been' express uncertainty.
18 / 20
A Slack message from a senior engineer reads: 'The API endpoint returned a 503 error during peak hours — the load balancer _____ be experiencing throttling.' Which modal best conveys this deduction based on observed symptoms?
'Must have been' indicates a strong belief given the evidence (503 error during peak hours). The load balancer is the most likely culprit based on this information. 'Could be' or 'might be' express possibility without certainty.
19 / 20
A developer writing a PR description states: 'The error occurred only when the user uploads a file larger than 10MB — the code _____ be failing to handle large files correctly.' Which modal is appropriate for this deduction?
'Must have been' suggests a strong belief based on the specific condition under which the error occurs. This implies that the code's handling of large files is indeed flawed. 'Should be' would suggest a recommended change.
20 / 20
A standup update from a developer says: 'I noticed the build times were significantly longer after the recent dependency upgrade — the caching mechanism _____ be broken.' Which modal best expresses this deduction about the system's behaviour?
'Has to be' is a strong statement of belief based on observed changes in build times. The broken caching mechanism is the most logical explanation for the increased duration. 'Could be' or 'might be' express possibility without certainty.
What will I practise in "Modal Verbs for Deduction in Technical Contexts — Grammar Exercise"?
Practise epistemic modal verbs — must, can't, should have, might have — for deduction and inference in debugging and incident analysis. 5 exercises.
How many exercises are in this module?
This module has 20 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.