5 exercises — practise choosing between declarative, imperative, interrogative, and exclamative sentences for different IT communication contexts.
0 / 12 completed
1 / 12
A technical writer is documenting a setup procedure. Which sentence type is most appropriate for each step in the instructions?
Imperative sentences ("Install Node.js version 20 or higher") are the standard for step-by-step technical instructions. They are direct, concise, and action-oriented — the verb leads, which mirrors the action the user must perform. This is the convention across all major style guides (Google, Microsoft, Apple, Mozilla). Declarative alternatives ("The user should install...") are longer and slightly softer — acceptable in narrative documentation but unnecessarily wordy for numbered steps. Interrogative steps ("Have you installed...?") read like a checklist, not an instruction. The imperative is the global technical writing standard for procedures.
2 / 12
Which use of interrogative form is appropriate in technical documentation?
Option A — using an interrogative as a section heading in a troubleshooting guide ("Why does this error occur?", "How do I reset my password?", "What is the difference between X and Y?") — is a well-established convention. It mirrors how users think and search ("why does this happen?") and is used by AWS, Google Cloud, Stripe, and others in their FAQ and troubleshooting sections. Option B ("Is the server running?") as a deployment step is interrogative used as a checklist item — acceptable but non-standard for a guide. Option C as a test file title is unusual — test files typically use descriptive noun phrases or imperative function names. Option A is the clearest, most conventionally appropriate use.
3 / 12
Which sentence is more appropriate for an API reference entry describing what a function does?
Both the imperative ("Call getUser() to retrieve...") and the declarative ("getUser() retrieves...") are standard in API documentation and represent two different but equally accepted conventions. The imperative (Option A) is action-focused and common in tutorial-style or task-oriented docs: it tells the developer what to do. The declarative (Option B) is reference-focused — it describes what the function does, which is the convention in many formal API references (MDN, Javadoc, Python standard library). Option C is weaker: "if you want to" is unnecessarily hedged and conversational for a reference. Choose one style per document and apply it consistently.
4 / 12
A developer is leaving a code review comment. Which formulation most effectively uses interrogative structure?
"Does this handle empty input? I don't see a null check." (Option B) is the most effective code review comment. The interrogative frame ("Does this handle...?") softens the feedback — it invites the author to respond or clarify, acknowledges that the reviewer may have missed something, and reduces the confrontational tone. This is the recommended approach in many engineering culture guides (e.g., Google's code review guide). Option A (declarative) is direct but could come across as blunt. Option C ("You forgot") is accusatory — making the comment personal rather than about the code. Option D uses exclamation marks — inappropriate and aggressive. Code review convention: frame concerns as questions or observations, not accusations.
5 / 12
Which statement about exclamative sentences in technical communication is most accurate?
Option B correctly identifies the register boundary for exclamative sentences. In informal IT communication — Slack celebrations ("The deploy went through!"), team announcements ("We hit 1M users!"), internal social posts — exclamatives are natural and positive. They reinforce team morale. However, in technical documentation, API references, error messages, code reviews, and formal reports, exclamative sentences are unprofessional. They undermine credibility ("What an elegant algorithm!" in a spec reads as subjective and fluffy). Error messages should be calm and actionable — not exclamative ("Critical error!" is common but borderline; "Error: Connection refused. Check your network." is better). The rule: exclamatives belong in human, social communication — not in technical reference material.
6 / 12
Mark, during a daily standup, reports: 'The database connection timeout is consistently at 30 seconds!'. Which sentence type best reflects the urgency and problem-focused nature of this communication?
This question assesses the use of exclamatory sentences for conveying urgency. Option 2 directly states the issue and its impact – a key element of standup updates. The other options are too vague or lack the immediate concern suggested by Mark's statement. Exclamative sentences often signal a need for immediate attention.
7 / 12
Mark, during a daily standup, reports: 'The database connection timeout is consistently at 30 seconds!'. Which sentence type best reflects the urgency and problem-focused nature of this communication?
This question assesses the use of exclamatory sentences for conveying urgency. Option 2 directly states the issue and its impact – a key element of standup updates. The other options are too vague or lack the immediate concern suggested by Mark's statement. Exclamative sentences often signal a need for immediate attention.
8 / 12
David left the following comment on a code review: 'Why did you use this specific algorithm? Can you explain your reasoning?' Which sentence type is predominantly used in this comment?
// Sort users by last name
The code sorts user names alphabetically.
This comment utilizes an interrogative structure – it's a direct question. The purpose of code reviews is often to understand the rationale behind decisions, and asking 'why' is a natural part of that process. The other options represent different sentence types that aren't appropriate for this scenario.
9 / 12
John is drafting a Slack message to his team about a critical bug he's found in the authentication service. He needs to quickly alert them and request immediate assistance. Which sentence type would be MOST appropriate for this urgent communication?
Option A: 'We are currently investigating potential issues.'
Option B: 'The authentication service is experiencing intermittent failures, please investigate immediately!'
Option C: 'This update includes some minor bug fixes.'
Option D: 'Let's discuss the latest features.'
This question assesses exclamatory sentences – used to express strong emotions or urgency. Option B directly commands action and highlights the severity of the problem, fitting the scenario perfectly. Options A and C are passive or trivial, while D is entirely inappropriate for urgent notifications.
10 / 12
Sarah is writing a PR description for a new feature: 'We've implemented rate limiting to prevent abuse. This limits requests to 100 per minute.' Which sentence type best conveys this information in a clear and concise manner?
This is an example of a declarative sentence, presenting a factual statement. Declarative sentences are most appropriate for PR descriptions because they clearly state what has been done without needing to prompt a response or convey emotion. The other options represent different sentence types that aren't suitable for this concise update.
11 / 12
Liam is responding to a code review comment: 'Is there a specific reason you chose to use the synchronous API call here?' Which sentence type is predominantly used in this response?
This is a classic example of an interrogative sentence used for clarification. Liam is *asking* a question to understand the reviewer's reasoning. The key here is that it's not a statement; it's a request for information. The other options represent different sentence types with distinct purposes.
12 / 12
Ben is drafting a Slack message to inform his team about an unexpected error during deployment. He writes: 'Something went wrong! We're investigating.' Which sentence type best suits Ben's immediate communication needs?
This message utilizes an exclamatory sentence type to convey the urgency and seriousness of the situation. The exclamation point emphasizes the unexpected nature of the error, prompting immediate attention. Declarative or interrogative sentences would be inappropriate for this critical alert. It's crucial to use appropriate tone in technical communications based on the context.
What will I practise in "Sentence Types in IT Communication — Grammar Exercise"?
Practise using declarative, imperative, interrogative, and exclamative sentences strategically in technical documentation, API docs, code reviews, and team
How many exercises are in this module?
This module has 12 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.