5 exercises — a/an/the with technical nouns: "an API", "the database", "a singleton", zero article for product names and uncountable nouns.
0 / 17 completed
1 / 17
A developer writes in a ticket: "We need to add _____ API endpoint that accepts _____ JSON payload and returns _____ HTTP 200 response."
Option B is correct. Two important rules:
a vs an with abbreviations: the choice depends on the pronunciation of the first letter, not its spelling. "API" is pronounced "ay-pee-eye" — it starts with the vowel sound /eɪ/, so it takes an. "HTTP" starts with "aitch" /eɪtʃ/, a vowel sound — so an HTTP. "A JSON payload" — "JSON" starts with /dʒ/ (consonant sound) — so a. Acronym article rule: an API, an IDE, an MVP, an SLA, an ORM; but a URL (/jʊ/), a UI (/juː/), a SQL query (if pronounced "sequel").
a/an vs the: the first three nouns are being introduced generically — no specific endpoint is implied — so use the indefinite article.
2 / 17
An architecture document states: "_____ load balancer distributes requests across _____ three backend servers. _____ server that fails is automatically removed from _____ pool."
Option C is the most natural. Article rules at work:
"A load balancer" — the document is describing the system generically, as a type of component, not referring to one specific, previously mentioned load balancer. Use indefinite article.
"three backend servers" — no article needed before a cardinal number in this context ("distributes across three servers").
"A server that fails" — a generic/hypothetical server, not a specific identified one. Use indefinite.
"the pool" — "pool" has already been conceptually introduced (the pool is part of the system being described), so the definite article is appropriate — it refers to the pool that belongs to the load balancer described above.
3 / 17
A README introduction reads: "This library provides _____ caching layer built on _____ Redis. _____ caching layer supports _____ LRU eviction and _____ TTL configuration."
Option B is correct. Key rules demonstrated:
"a caching layer" — first mention, introduced as a feature of the library. Indefinite article.
"Redis" (no article) — proper nouns and product/brand names (Redis, PostgreSQL, Kubernetes, Docker, GitHub) take no article. Never "a Redis" or "the Redis" unless you mean a specific installation: "the Redis instance in staging".
"The caching layer" — second mention, now identified and specific. Switch to definite article.
"LRU eviction and TTL configuration" (no article) — technical features listed as uncountable/abstract concepts take zero article. Compare: "supports LRU eviction" vs "has a good LRU eviction policy".
4 / 17
A code review comment says: "_____ performance of this query is acceptable, but using _____ singleton pattern here would be _____ mistake."
Option C is correct.
"The performance" — performance here is specified ("of this query") — we know exactly which performance we mean. Use "the" with nouns that are uniquely identified by a following prepositional phrase. "The performance of this query", "the complexity of the algorithm", "the latency of the endpoint".
"a singleton pattern" — the singleton pattern is being named as a type/category ("using a singleton pattern" = using this kind of pattern). Indefinite article for a category reference.
"a mistake" — one of many possible mistakes, introduced for the first time. Indefinite article.
Note: Option D is wrong because abstract nouns like "performance" and "pattern" in specific contexts do need articles.
5 / 17
An incident report summary states: "_____ outage began at 14:23 UTC. _____ root cause was _____ memory leak in _____ authentication service. _____ engineering team resolved _____ issue within 47 minutes."
Option C is correct, and this exercise illustrates how articles shift from indefinite to definite within a single paragraph:
"An outage" — first mention, introduced into the discourse. Indefinite. (Starts with vowel sound /aʊ/, so "an").
"The root cause" — every outage has exactly one root cause in an incident report; the concept of "root cause" is treated as unique and already implied by the context. Use "the". In postmortem writing, "the root cause" is a near-fixed phrase.
"a memory leak" — one of many possible causes; introduced for the first time.
"the authentication service" — a specific, named service known to the reader (it's "our" auth service).
"The engineering team" and "the issue" — both are uniquely identified entities already known in context.
6 / 17
Sarah, a junior developer, posted this message in the team Slack channel after receiving an API response:
'The response code is 403. It says 'Forbidden'. I'm not sure why—the request was authenticated and seemed legitimate.'
Which of the following best describes the correct way to respond, considering technical writing conventions?
Option A: 'That's a standard response for unauthorized access attempts. Just double-check the user's permissions in the database.'
Option B: 'It's likely a bug! The API should always return 200 if authentication is correct. Report this immediately!'
Option C: 'A 403 response indicates the server denied access, usually due to insufficient permissions or resource limitations. Let's investigate the request details – user ID, IP address, and any associated roles.'
Option D: 'Don't worry about it; sometimes APIs return unexpected codes. Just log the error and move on.'
This question assesses understanding of API response codes beyond simply knowing their values. A key aspect of technical writing is providing context and actionable information. Option C correctly identifies that a 403 signifies access denial due to permissions or resource limits, prompting further investigation – the crucial step in effective debugging. Options A and D are too simplistic and don't offer guidance on how to proceed, while option B incorrectly assumes all 200 responses are always valid.
7 / 17
Sarah is troubleshooting a 403 error returned by an API. She's understandably confused because the request *appeared* to be authenticated. Which response best aligns with clear and helpful technical documentation, particularly within a code review context or Slack discussion?
Consider how a developer needs actionable information to diagnose the problem.
Option C is the most appropriate response because it provides a clear explanation of what a 403 error signifies – specifically insufficient permissions or resource limitations. It moves beyond simply stating the problem (as in Option A) and suggests a focused investigation based on relevant request details. Options B and D are overly alarmist; while reporting an issue is important, immediately declaring it 'likely a bug' without investigation isn't helpful. Option D dismisses the error without offering any guidance.
8 / 17
Sarah, a junior developer, posted this message in the team Slack channel after receiving an API response:
'The response code is 403. It says 'Forbidden'. I'm not sure why—the request was authenticated and seemed legitimate.'
Which of the following best describes the correct way to respond, considering technical writing conventions?
Option A: 'That's a standard response for unauthorized access attempts. Just double-check the user's permissions in the database.'
Option B: 'It's likely a bug! The API should always return 200 if authentication is correct. Report this immediately!'
Option C: 'A 403 response indicates the server denied access, usually due to insufficient permissions or resource limitations. Let's investigate the request details – user ID, IP address, and any associated roles.'
Option D: 'Don't worry about it; sometimes APIs return unexpected codes. Just log the error and move on.'
This question assesses understanding of API response codes beyond simply knowing their values. A key aspect of technical writing is providing context and actionable information. Option C correctly identifies that a 403 signifies access denial due to permissions or resource limits, prompting further investigation – the crucial step in effective debugging. Options A and D are too simplistic and don't offer guidance on how to proceed, while option B incorrectly assumes all 200 responses are always valid.
9 / 17
Sarah is troubleshooting a 403 error returned by an API. She's understandably confused because the request *appeared* to be authenticated. Which response best aligns with clear and helpful technical documentation, particularly within a code review context or Slack discussion?
Consider how a developer needs actionable information to diagnose the problem.
Option C is the most appropriate response because it provides a clear explanation of what a 403 error signifies – specifically insufficient permissions or resource limitations. It moves beyond simply stating the problem (as in Option A) and suggests a focused investigation based on relevant request details. Options B and D are overly alarmist; while reporting an issue is important, immediately declaring it 'likely a bug' without investigation isn't helpful. Option D dismisses the error without offering any guidance.
10 / 17
Sarah, a junior developer, posted this message in the team Slack channel after receiving an API response:
'The response code is 403. It says 'Forbidden'. I'm not sure why—the request was authenticated and seemed legitimate.'
Which of the following best describes the correct way to respond, considering technical writing conventions?
Option A: 'That's a standard response for unauthorized access attempts. Just double-check the user's permissions in the database.'
Option B: 'It's likely a bug! The API should always return 200 if authentication is correct. Report this immediately!'
Option C: 'A 403 response indicates the server denied access, usually due to insufficient permissions or resource limitations. Let's investigate the request details – user ID, IP address, and any associated roles.'
Option D: 'Don't worry about it; sometimes APIs return unexpected codes. Just log the error and move on.'
This question assesses understanding of API response codes beyond simply knowing their values. A key aspect of technical writing is providing context and actionable information. Option C correctly identifies that a 403 signifies access denial due to permissions or resource limits, prompting further investigation – the crucial step in effective debugging. Options A and D are too simplistic and don't offer guidance on how to proceed, while option B incorrectly assumes all 200 responses are always valid.
11 / 17
Sarah is troubleshooting a 403 error returned by an API. She's understandably confused because the request *appeared* to be authenticated. Which response best aligns with clear and helpful technical documentation, particularly within a code review context or Slack discussion?
Consider how a developer needs actionable information to diagnose the problem.
Option C is the most appropriate response because it provides a clear explanation of what a 403 error signifies – specifically insufficient permissions or resource limitations. It moves beyond simply stating the problem (as in Option A) and suggests a focused investigation based on relevant request details. Options B and D are overly alarmist; while reporting an issue is important, immediately declaring it 'likely a bug' without investigation isn't helpful. Option D dismisses the error without offering any guidance.
12 / 17
David, a senior engineer, comments on a PR:
'This function uses the get_user method. It's good practice to use a consistent naming convention for all database queries - consider using db.query instead of sql.execute here.'
The question tests understanding of when to apply articles in a code review context. David isn't criticizing the *function* itself, but rather its naming convention – a common concern during code reviews. Choosing 'incorrect' highlights the core issue: David's comment is about style and consistency, not functionality. Option 'correct' demonstrates an understanding of best practices for maintainability.
13 / 17
David, a senior engineer, comments on a PR:
'This function uses the get_user method. It's good practice to use a consistent naming convention for all database queries - consider using db.query instead of sql.execute here.'
The question tests understanding of when to apply articles in a code review context. David isn't criticizing the *function* itself, but rather its naming convention – a common concern during code reviews. Choosing 'incorrect' highlights the core issue: David's comment is about style and consistency, not functionality. Option 'correct' demonstrates an understanding of best practices for maintainability.
14 / 17
David, a senior engineer, comments on a PR:
'This function uses the get_user method. It's good practice to use a consistent naming convention for all database queries - consider using db.query instead of sql.execute here.'
The question tests understanding of when to apply articles in a code review context. David isn't criticizing the *function* itself, but rather its naming convention – a common concern during code reviews. Choosing 'incorrect' highlights the core issue: David's comment is about style and consistency, not functionality. Option 'correct' demonstrates an understanding of best practices for maintainability.
15 / 17
Mark is writing a Slack message to his team about a recent API outage. He says: 'The service was down for about an hour. The root cause was a database connection timeout.' Which sentence best demonstrates the correct use of articles in this technical context?
'The' service was down…
Here, 'a' and 'the' are used to indicate general instances of services and causes. Using 'the' implies a specific, defined service or root cause which isn't necessarily the case here. Incorrect options overuse 'the' when referring to unspecified items; it's generally better to use 'a' or 'an' unless you can clearly define what is being referred to.
16 / 17
You're writing a PR description for a new feature that uses a caching layer. Which sentence best illustrates the appropriate use of articles in this scenario?
'We implemented _____ Redis instance to improve performance.'
When referring to a specific instance of something (like a Redis server), 'a' is typically used. Using 'the' would imply it's a uniquely defined instance, which isn't generally the case in technical contexts. It's also more natural and common to say 'Redis instance' rather than 'an Redis instance'.
17 / 17
A code review comment reads: 'The authentication service is experiencing high CPU utilization. Consider optimizing _____ database queries to reduce the load.' Which option best utilizes articles appropriately in this scenario?
'The authentication service…',
'The' is used here because 'authentication service' refers to a specific entity – the named service. Using 'a' would imply a general instance of an authentication service which isn't appropriate in this context. Similarly, 'the database queries' refers to a specific set of queries.
What will I practise in "Articles in Technical Writing — Grammar Exercise"?
Practise a, an, and the with technical nouns: an API, the database, a singleton, Redis with no article. 5 interactive exercises for IT professionals.
How many exercises are in this module?
This module has 17 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.