Intermediate
Grammar
#articles
#pronunciation
Article Choice with Acronyms (Sound, Not Spelling)
5 exercises — practise choosing "a" or "an" before tech acronyms based on how they sound when spoken.
0 / 20 completed
1 / 20
Choose the sentence with the correct article before the acronym.
"She built an API for the mobile team" is correct: "API" is pronounced starting with the vowel sound "ay" (/eɪ/), so it takes "an", following the sound, not the spelling. Option B incorrectly uses "a", ignoring the initial vowel sound. Option C spells out the letters unnaturally within the sentence, which is not standard written usage. Option D incorrectly stacks both "the" and "an" before the noun, which is ungrammatical.
2 / 20
Which sentence uses the correct article before "URL", based on its pronunciation?
"Please send me a URL for the staging environment" is correct: "URL" is pronounced starting with a consonant sound, "you" (/juː/), so it takes "a", not "an", even though the written first letter "U" is a vowel. Option B incorrectly uses "an", following the spelling instead of the sound. Option C stacks "the" and "a" incorrectly. Option D unnaturally spells out the letters in running text.
3 / 20
Select the sentence with the correct article before "HTML" element, based on pronunciation.
"This is an HTML attribute that controls accessibility" is correct: "HTML" is pronounced starting with "aitch" (/eɪtʃ/), a vowel sound, so it takes "an" despite "H" being a consonant letter in spelling. Option B incorrectly uses "a", following spelling rather than pronunciation. Option C adds an unnecessary and unnatural spelled-out fragment. Option D incorrectly combines "the" and "an" before the noun phrase.
4 / 20
Which sentence uses the correct article before "UI", based on how it is spoken?
"The team redesigned a UI component used across the dashboard" is correct: "UI" is pronounced starting with "you" (/juː/), a consonant sound, so it takes "a", even though "U" is a written vowel. Option B incorrectly uses "an" based on spelling rather than pronunciation. Option C incorrectly stacks "the" and "a". Option D unnaturally spells the letters out within the sentence.
5 / 20
Choose the sentence with the correct article before "SQL" query, based on how the acronym is typically pronounced.
"He wrote an SQL query to aggregate the monthly totals" is correct when "SQL" is pronounced letter-by-letter, "ess-cue-ell" (/ɛs/), which starts with a vowel sound, so it takes "an" in that common pronunciation. (Note: speakers who pronounce it as the word "sequel" would instead use "a SQL", since "sequel" starts with a consonant sound; article choice always follows the pronunciation actually used.) Option B, "a SQL", only fits the "sequel" pronunciation, not the letter-by-letter one assumed here. Option C unnaturally spells out the letters in running text. Option D incorrectly combines "the" and "an".
6 / 20
Reviewer: 'I'm seeing a lot of calls to the AWS S3 bucket API. It seems like you're using 'S3' as an abbreviation—should we be referring to it as 'Amazon Simple Storage Service' consistently in the code comments and documentation? It's important for maintainability.
Developer: I added the comments, but I wasn't sure about the article usage. Which of these descriptions is best?The key here is that 'S3' refers to a specific product name – Amazon Simple Storage Service. Therefore, it's treated like any other proper noun, requiring 'the'. Using 'an' would imply it's just *a* storage service, which isn't accurate. Options A and B are technically correct but miss the important nuance of referring to a named product; option C is incorrect because it doesn't acknowledge the official name, and D incorrectly suggests acronym usage is acceptable without qualification.
7 / 20
Reviewer: 'We're getting a high volume of requests to the Redis cluster. I noticed you've been using 'Redis' as an abbreviation in the logs and commit messages. Should we consistently spell it out – 'Remote Dictionary Service' – for clarity, especially when discussing performance metrics? It improves understanding for new team members.Developer: I was reviewing my PR and wanted to ensure I used the correct article. Which of these descriptions accurately reflects the reviewer's request?This question tests understanding of article usage with acronyms that sound similar to their full names. The reviewer isn't asking for *the* Remote Dictionary Service, but rather for consistent spelling when discussing the specific system – Redis – and its performance. Using 'the' would be incorrect because 'Redis' functions as an abbreviation representing a concrete entity, not a general concept. Option B is also incorrect as it suggests that industry-wide recognition justifies inconsistent usage.
8 / 20
Reviewer: 'We've identified a spike in errors related to the Kafka cluster. You're using 'Kafka' as an abbreviation throughout the error logs and the pull request description. To ensure everyone understands exactly what we're dealing with, should we consistently use the full name, 'Apache Kafka,' especially when discussing potential bottlenecks? Developer: I wanted to confirm my usage was correct. Which of these options best reflects the reviewer's feedback?This question tests understanding of article usage with acronyms in a realistic code review scenario. The reviewer isn't criticizing the developer's choice of abbreviation itself, but rather the *inconsistency* in its use and the potential for confusion, especially when discussing performance or troubleshooting. Using the full name – 'Apache Kafka' – provides unambiguous clarity and is best practice, particularly when communicating complex technical issues to a wider audience. The incorrect options reflect misunderstandings about whether abbreviations are always acceptable or that formality dictates usage.
9 / 20
Reviewer: 'I'm seeing a lot of calls to the AWS S3 bucket API. It seems like you're using 'S3' as an abbreviation—should we be referring to it as 'Amazon Simple Storage Service' consistently in the code comments and documentation? It's important for maintainability.
Developer: I added the comments, but I wasn't sure about the article usage. Which of these descriptions is best?The key here is that 'S3' refers to a specific product name – Amazon Simple Storage Service. Therefore, it's treated like any other proper noun, requiring 'the'. Using 'an' would imply it's just *a* storage service, which isn't accurate. Options A and B are technically correct but miss the important nuance of referring to a named product; option C is incorrect because it doesn't acknowledge the official name, and D incorrectly suggests acronym usage is acceptable without qualification.
10 / 20
Reviewer: 'We're getting a high volume of requests to the Redis cluster. I noticed you've been using 'Redis' as an abbreviation in the logs and commit messages. Should we consistently spell it out – 'Remote Dictionary Service' – for clarity, especially when discussing performance metrics? It improves understanding for new team members.Developer: I was reviewing my PR and wanted to ensure I used the correct article. Which of these descriptions accurately reflects the reviewer's request?This question tests understanding of article usage with acronyms that sound similar to their full names. The reviewer isn't asking for *the* Remote Dictionary Service, but rather for consistent spelling when discussing the specific system – Redis – and its performance. Using 'the' would be incorrect because 'Redis' functions as an abbreviation representing a concrete entity, not a general concept. Option B is also incorrect as it suggests that industry-wide recognition justifies inconsistent usage.
11 / 20
Reviewer: 'We've identified a spike in errors related to the Kafka cluster. You're using 'Kafka' as an abbreviation throughout the error logs and the pull request description. To ensure everyone understands exactly what we're dealing with, should we consistently use the full name, 'Apache Kafka,' especially when discussing potential bottlenecks? Developer: I wanted to confirm my usage was correct. Which of these options best reflects the reviewer's feedback?This question tests understanding of article usage with acronyms in a realistic code review scenario. The reviewer isn't criticizing the developer's choice of abbreviation itself, but rather the *inconsistency* in its use and the potential for confusion, especially when discussing performance or troubleshooting. Using the full name – 'Apache Kafka' – provides unambiguous clarity and is best practice, particularly when communicating complex technical issues to a wider audience. The incorrect options reflect misunderstandings about whether abbreviations are always acceptable or that formality dictates usage.
12 / 20
Reviewer: 'I'm seeing a lot of calls to the AWS S3 bucket API. It seems like you're using 'S3' as an abbreviation—should we be referring to it as 'Amazon Simple Storage Service' consistently in the code comments and documentation? It's important for maintainability.
Developer: I added the comments, but I wasn't sure about the article usage. Which of these descriptions is best?The key here is that 'S3' refers to a specific product name – Amazon Simple Storage Service. Therefore, it's treated like any other proper noun, requiring 'the'. Using 'an' would imply it's just *a* storage service, which isn't accurate. Options A and B are technically correct but miss the important nuance of referring to a named product; option C is incorrect because it doesn't acknowledge the official name, and D incorrectly suggests acronym usage is acceptable without qualification.
13 / 20
Reviewer: 'We're getting a high volume of requests to the Redis cluster. I noticed you've been using 'Redis' as an abbreviation in the logs and commit messages. Should we consistently spell it out – 'Remote Dictionary Service' – for clarity, especially when discussing performance metrics? It improves understanding for new team members.Developer: I was reviewing my PR and wanted to ensure I used the correct article. Which of these descriptions accurately reflects the reviewer's request?This question tests understanding of article usage with acronyms that sound similar to their full names. The reviewer isn't asking for *the* Remote Dictionary Service, but rather for consistent spelling when discussing the specific system – Redis – and its performance. Using 'the' would be incorrect because 'Redis' functions as an abbreviation representing a concrete entity, not a general concept. Option B is also incorrect as it suggests that industry-wide recognition justifies inconsistent usage.
14 / 20
Reviewer: 'We've identified a spike in errors related to the Kafka cluster. You're using 'Kafka' as an abbreviation throughout the error logs and the pull request description. To ensure everyone understands exactly what we're dealing with, should we consistently use the full name, 'Apache Kafka,' especially when discussing potential bottlenecks? Developer: I wanted to confirm my usage was correct. Which of these options best reflects the reviewer's feedback?This question tests understanding of article usage with acronyms in a realistic code review scenario. The reviewer isn't criticizing the developer's choice of abbreviation itself, but rather the *inconsistency* in its use and the potential for confusion, especially when discussing performance or troubleshooting. Using the full name – 'Apache Kafka' – provides unambiguous clarity and is best practice, particularly when communicating complex technical issues to a wider audience. The incorrect options reflect misunderstandings about whether abbreviations are always acceptable or that formality dictates usage.
15 / 20
Reviewer: 'I'm seeing a lot of calls to the AWS S3 bucket API. It seems like you're using 'S3' as an abbreviation—should we be referring to it as 'Amazon Simple Storage Service' consistently in the code comments and documentation? It's important for maintainability.
Developer: I added the comments, but I wasn't sure about the article usage. Which of these descriptions is best?The key here is that 'S3' refers to a specific product name – Amazon Simple Storage Service. Therefore, it's treated like any other proper noun, requiring 'the'. Using 'an' would imply it's just *a* storage service, which isn't accurate. Options A and B are technically correct but miss the important nuance of referring to a named product; option C is incorrect because it doesn't acknowledge the official name, and D incorrectly suggests acronym usage is acceptable without qualification.
16 / 20
Reviewer: 'We're getting a high volume of requests to the Redis cluster. I noticed you've been using 'Redis' as an abbreviation in the logs and commit messages. Should we consistently spell it out – 'Remote Dictionary Service' – for clarity, especially when discussing performance metrics? It improves understanding for new team members.Developer: I was reviewing my PR and wanted to ensure I used the correct article. Which of these descriptions accurately reflects the reviewer's request?This question tests understanding of article usage with acronyms that sound similar to their full names. The reviewer isn't asking for *the* Remote Dictionary Service, but rather for consistent spelling when discussing the specific system – Redis – and its performance. Using 'the' would be incorrect because 'Redis' functions as an abbreviation representing a concrete entity, not a general concept. Option B is also incorrect as it suggests that industry-wide recognition justifies inconsistent usage.
17 / 20
Reviewer: 'We've identified a spike in errors related to the Kafka cluster. You're using 'Kafka' as an abbreviation throughout the error logs and the pull request description. To ensure everyone understands exactly what we're dealing with, should we consistently use the full name, 'Apache Kafka,' especially when discussing potential bottlenecks? Developer: I wanted to confirm my usage was correct. Which of these options best reflects the reviewer's feedback?This question tests understanding of article usage with acronyms in a realistic code review scenario. The reviewer isn't criticizing the developer's choice of abbreviation itself, but rather the *inconsistency* in its use and the potential for confusion, especially when discussing performance or troubleshooting. Using the full name – 'Apache Kafka' – provides unambiguous clarity and is best practice, particularly when communicating complex technical issues to a wider audience. The incorrect options reflect misunderstandings about whether abbreviations are always acceptable or that formality dictates usage.
18 / 20
During a standup meeting, Sarah says: 'I'm working on optimizing the performance of our GraphQL API. I've been using 'GraphQL' as an abbreviation in my commit messages.' What is the most appropriate response from David?
Acronyms should be used with caution, especially in communication. While familiarity might exist within a team, explicitly spelling out 'GraphQL' enhances clarity and avoids misunderstandings, particularly for new team members or those less familiar with the technology. The other options either endorse incorrect practice or introduce alternative, potentially confusing, abbreviations.
19 / 20
You're reviewing a code change that uses 'UI' as an abbreviation throughout. The commit message reads: 'Fixed UI bug.' Which of the following is the best way to provide feedback?
Similar to other acronyms, clarity is paramount. Although 'UI' is common, spelling out 'User Interface' provides immediate understanding for developers who may be new to the project or unfamiliar with the specific UI components. This demonstrates a commitment to making the codebase accessible and understandable.
20 / 20
You receive an API response containing the following: `{"status":"200","data":{"name":"DatabaseServer"}}`. What is the most appropriate way to refer to 'DatabaseServer' in a subsequent commit message?While 'DBServer' or 'DS' might be shortcuts, using the full name 'DatabaseServer' is best practice for API responses. This ensures absolute clarity and avoids any potential misinterpretation, especially when dealing with complex systems where acronyms could be ambiguous across different teams or documentation.
Next up:
More Grammar Exercises →
Frequently Asked Questions
What will I practise in "Article Choice with Acronyms (Sound, Not Spelling) — IT Grammar Exercise"?
Practise choosing "a" or "an" before acronyms and initialisms like API, URL, HTML, UI, and SQL based on their spoken pronunciation, not their written first
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.