Intermediate
Grammar
#compound-nouns
#abbreviations
#technical-vocabulary
IT Compound Nouns & Abbreviations
5 exercises — forming technical compound nouns correctly, understanding modifier order, and expanding common IT abbreviations into full noun phrases.
Quick reference
- Modifier first: code review · load balancer · pull request · bug report
- Stress on first word: CODE review · LOAD balancer (stress distinguishes compound nouns from noun phrases)
- Hyphen as modifier: a load-balanced cluster · a well-tested module
- Know your expansions: CI/CD · API · ORM · TDD · SLA · SLO · IaC · SDK
0 / 25 completed
1 / 25
Which is the correct compound noun for a server that balances load across multiple instances?
"Load balancer" — two words, no hyphen — is the standard industry term. Compound noun stress rules: in a compound noun, the first word is stressed (LOAD balancer, not load BALancer). This stress pattern distinguishes compound nouns from noun phrases: a "LOAD balancer" (one thing) vs. "a heavy MACHINE" (adjective + noun). Most IT compound nouns are written as two words: version control, code review, test runner, error message. Some are hyphenated when used as modifiers: "a load-balanced cluster".
2 / 25
Identify the correct IT compound noun in this sentence:
"Please check the _____ before deploying to avoid merge conflicts."
"Please check the _____ before deploying to avoid merge conflicts."
"Pull request" — the standard term for a request to merge code changes into a branch. The word order in compound nouns is: modifier first, head noun last (pull modifies request — "a request to pull/merge code"). Common IT compound nouns with this structure: push notification, merge conflict, code review, bug report, test suite, stack trace, rollback plan. Reversed order ("request pull") is never correct in English compound nouns.
3 / 25
Build the correct compound noun for a document that describes how a system behaves. Choose the right combination.
"Technical specification" (or tech spec) — adjective + noun. Notice the difference between: a technical specification (tech spec), a functional specification (func spec), a design specification. Two-word compound nouns can be: noun+noun (code review), adjective+noun (technical specification), or verb+noun (pull request). In everyday IT usage, many compound terms are shortened: tech spec, dev ops, prod env. Knowing when to abbreviate shows fluency.
4 / 25
Expand the abbreviation into its full noun phrase:
"The team uses a CI/CD pipeline to automate releases."
"The team uses a CI/CD pipeline to automate releases."
"Continuous Integration and Continuous Deployment (or Continuous Delivery) pipeline." — CI/CD is one of the most common IT abbreviations. The distinction: CI = automatically testing and integrating code changes; CD = either automatically delivering to a staging environment (Continuous Delivery) or automatically deploying to production (Continuous Deployment). In interviews and documentation, knowing the full expansion — and the difference between Delivery and Deployment — signals a deeper understanding than just knowing the acronym.
5 / 25
Which compound noun correctly describes a server that stores files and serves them to clients on request?
"File server" — simple two-word compound: modifier (file) + head noun (server). This is the standard pattern for naming IT components by their function: web server, mail server, proxy server, DNS server, database server, game server. The modifier tells you what the server handles. "Server of files" is grammatically possible but not used in IT. "File serving server" is redundant — the word "server" already implies serving. Learning the standard form of IT compound nouns is part of professional fluency.
6 / 25
Reviewer: 'I'm seeing a lot of `IOError` exceptions in the logs during peak times. Can you investigate if the connection pool is being exhausted? It might be worth checking the `ConnectionPoolTimeout` setting.
Developer: I've increased the timeout, but it's still happening. The error seems to be related to slow database queries.
Which of the following best describes the developer's issue?The developer is experiencing a problem related to the number of concurrent connections being made to the database. The `ConnectionPoolTimeout` setting doesn't directly address this; it controls how long a connection attempt waits before timing out. The core issue is that too many requests are competing for limited database resources, leading to errors. Choosing option 3 accurately reflects this technical problem and uses the correct compound noun.
7 / 25
Reviewer: 'We're experiencing high latency with the new API endpoint. The response times are consistently exceeding 500ms. Can you investigate if there's an issue with the RateLimiter implementation or potential bottlenecks in the data processing pipeline?', This question tests understanding of a common performance issue in APIs. The reviewer's comment strongly suggests latency problems with the endpoint, specifically mentioning 'RateLimiter,' which indicates a potential problem with requests being throttled – this is a key aspect of API design and optimization. Choosing this option demonstrates an ability to connect technical terms like
RateLimiter with their practical implications in performance monitoring.8 / 25
Reviewer: 'Our application is experiencing intermittent performance degradation during peak usage. We've identified a spike in requests hitting the Authentication Service and are seeing increased latency. Can you investigate if there's an issue with the AuthenticationServiceTimeout or potential bottlenecks within the service itself?', The reviewer is specifically referencing a time limit configured for the Authentication Service. While all options could potentially contribute to performance issues, 'Authentication Service Timeout' directly addresses the identified problem – requests hitting this service are experiencing increased latency. The other options (Request Volume Monitor, Database Connection Pool Exhaustion, and Network Bandwidth Saturation) represent broader monitoring categories that might *indicate* a problem but don't pinpoint the root cause in this scenario.
9 / 25
Reviewer: 'The application is throwing a NullPointerException when attempting to access the user profile data. We've recently deployed version 2.3 of the User Service. Can you investigate if there's an issue with the service itself, or perhaps a regression in the recent deployment?', Developer: 'I've rolled back to version 2.2 and the error is gone. I'm going to file a bug report.'This scenario highlights the importance of accurately describing errors in technical contexts. The developer correctly identified a problem related to a code change (version 2.3), which aligns with reporting a regression. Options A and B are irrelevant; A focuses on connectivity, while B is asking for documentation – neither addresses the core issue. Option D is an inappropriate troubleshooting step.
10 / 25
Reviewer: 'The service is returning 500 Internal Server Errors intermittently. We've been monitoring the Kubernetes cluster and see a high CPU usage on one of the pods running the Order Processing Service. Can you investigate if there's an issue with resource allocation or potential bottlenecks within the service itself?'
Developer: 'I've scaled up the pod to 4 cores, but the errors are still occurring. I suspect it might be related to excessive logging.'This question tests understanding of common troubleshooting steps in a development environment. The correct answer focuses on logging – excessive logging can significantly impact performance and often contributes to errors like 500 Internal Server Errors. Options A and D are irrelevant; redesigns and new deployments don't directly address high CPU usage or log volume. Option B is incorrect because simply increasing memory doesn't solve a problem caused by inefficient code or resource-intensive operations.
11 / 25
Reviewer: 'I'm seeing a lot of `IOError` exceptions in the logs during peak times. Can you investigate if the connection pool is being exhausted? It might be worth checking the `ConnectionPoolTimeout` setting.
Developer: I've increased the timeout, but it's still happening. The error seems to be related to slow database queries.
Which of the following best describes the developer's issue?The developer is experiencing a problem related to the number of concurrent connections being made to the database. The `ConnectionPoolTimeout` setting doesn't directly address this; it controls how long a connection attempt waits before timing out. The core issue is that too many requests are competing for limited database resources, leading to errors. Choosing option 3 accurately reflects this technical problem and uses the correct compound noun.
12 / 25
Reviewer: 'We're experiencing high latency with the new API endpoint. The response times are consistently exceeding 500ms. Can you investigate if there's an issue with the RateLimiter implementation or potential bottlenecks in the data processing pipeline?', This question tests understanding of a common performance issue in APIs. The reviewer's comment strongly suggests latency problems with the endpoint, specifically mentioning 'RateLimiter,' which indicates a potential problem with requests being throttled – this is a key aspect of API design and optimization. Choosing this option demonstrates an ability to connect technical terms like
RateLimiter with their practical implications in performance monitoring.13 / 25
Reviewer: 'Our application is experiencing intermittent performance degradation during peak usage. We've identified a spike in requests hitting the Authentication Service and are seeing increased latency. Can you investigate if there's an issue with the AuthenticationServiceTimeout or potential bottlenecks within the service itself?', The reviewer is specifically referencing a time limit configured for the Authentication Service. While all options could potentially contribute to performance issues, 'Authentication Service Timeout' directly addresses the identified problem – requests hitting this service are experiencing increased latency. The other options (Request Volume Monitor, Database Connection Pool Exhaustion, and Network Bandwidth Saturation) represent broader monitoring categories that might *indicate* a problem but don't pinpoint the root cause in this scenario.
14 / 25
Reviewer: 'The application is throwing a NullPointerException when attempting to access the user profile data. We've recently deployed version 2.3 of the User Service. Can you investigate if there's an issue with the service itself, or perhaps a regression in the recent deployment?', Developer: 'I've rolled back to version 2.2 and the error is gone. I'm going to file a bug report.'This scenario highlights the importance of accurately describing errors in technical contexts. The developer correctly identified a problem related to a code change (version 2.3), which aligns with reporting a regression. Options A and B are irrelevant; A focuses on connectivity, while B is asking for documentation – neither addresses the core issue. Option D is an inappropriate troubleshooting step.
15 / 25
Reviewer: 'The service is returning 500 Internal Server Errors intermittently. We've been monitoring the Kubernetes cluster and see a high CPU usage on one of the pods running the Order Processing Service. Can you investigate if there's an issue with resource allocation or potential bottlenecks within the service itself?'
Developer: 'I've scaled up the pod to 4 cores, but the errors are still occurring. I suspect it might be related to excessive logging.'This question tests understanding of common troubleshooting steps in a development environment. The correct answer focuses on logging – excessive logging can significantly impact performance and often contributes to errors like 500 Internal Server Errors. Options A and D are irrelevant; redesigns and new deployments don't directly address high CPU usage or log volume. Option B is incorrect because simply increasing memory doesn't solve a problem caused by inefficient code or resource-intensive operations.
16 / 25
Reviewer: 'I'm seeing a lot of `IOError` exceptions in the logs during peak times. Can you investigate if the connection pool is being exhausted? It might be worth checking the `ConnectionPoolTimeout` setting.
Developer: I've increased the timeout, but it's still happening. The error seems to be related to slow database queries.
Which of the following best describes the developer's issue?The developer is experiencing a problem related to the number of concurrent connections being made to the database. The `ConnectionPoolTimeout` setting doesn't directly address this; it controls how long a connection attempt waits before timing out. The core issue is that too many requests are competing for limited database resources, leading to errors. Choosing option 3 accurately reflects this technical problem and uses the correct compound noun.
17 / 25
Reviewer: 'We're experiencing high latency with the new API endpoint. The response times are consistently exceeding 500ms. Can you investigate if there's an issue with the RateLimiter implementation or potential bottlenecks in the data processing pipeline?', This question tests understanding of a common performance issue in APIs. The reviewer's comment strongly suggests latency problems with the endpoint, specifically mentioning 'RateLimiter,' which indicates a potential problem with requests being throttled – this is a key aspect of API design and optimization. Choosing this option demonstrates an ability to connect technical terms like
RateLimiter with their practical implications in performance monitoring.18 / 25
Reviewer: 'Our application is experiencing intermittent performance degradation during peak usage. We've identified a spike in requests hitting the Authentication Service and are seeing increased latency. Can you investigate if there's an issue with the AuthenticationServiceTimeout or potential bottlenecks within the service itself?', The reviewer is specifically referencing a time limit configured for the Authentication Service. While all options could potentially contribute to performance issues, 'Authentication Service Timeout' directly addresses the identified problem – requests hitting this service are experiencing increased latency. The other options (Request Volume Monitor, Database Connection Pool Exhaustion, and Network Bandwidth Saturation) represent broader monitoring categories that might *indicate* a problem but don't pinpoint the root cause in this scenario.
19 / 25
Reviewer: 'The application is throwing a NullPointerException when attempting to access the user profile data. We've recently deployed version 2.3 of the User Service. Can you investigate if there's an issue with the service itself, or perhaps a regression in the recent deployment?', Developer: 'I've rolled back to version 2.2 and the error is gone. I'm going to file a bug report.'This scenario highlights the importance of accurately describing errors in technical contexts. The developer correctly identified a problem related to a code change (version 2.3), which aligns with reporting a regression. Options A and B are irrelevant; A focuses on connectivity, while B is asking for documentation – neither addresses the core issue. Option D is an inappropriate troubleshooting step.
20 / 25
Reviewer: 'The service is returning 500 Internal Server Errors intermittently. We've been monitoring the Kubernetes cluster and see a high CPU usage on one of the pods running the Order Processing Service. Can you investigate if there's an issue with resource allocation or potential bottlenecks within the service itself?'
Developer: 'I've scaled up the pod to 4 cores, but the errors are still occurring. I suspect it might be related to excessive logging.'This question tests understanding of common troubleshooting steps in a development environment. The correct answer focuses on logging – excessive logging can significantly impact performance and often contributes to errors like 500 Internal Server Errors. Options A and D are irrelevant; redesigns and new deployments don't directly address high CPU usage or log volume. Option B is incorrect because simply increasing memory doesn't solve a problem caused by inefficient code or resource-intensive operations.
21 / 25
Reviewer: 'I'm seeing a lot of `IOError` exceptions in the logs during peak times. Can you investigate if the connection pool is being exhausted? It might be worth checking the `ConnectionPoolTimeout` setting.
Developer: I've increased the timeout, but it's still happening. The error seems to be related to slow database queries.
Which of the following best describes the developer's issue?The developer is experiencing a problem related to the number of concurrent connections being made to the database. The `ConnectionPoolTimeout` setting doesn't directly address this; it controls how long a connection attempt waits before timing out. The core issue is that too many requests are competing for limited database resources, leading to errors. Choosing option 3 accurately reflects this technical problem and uses the correct compound noun.
22 / 25
Reviewer: 'We're experiencing high latency with the new API endpoint. The response times are consistently exceeding 500ms. Can you investigate if there's an issue with the RateLimiter implementation or potential bottlenecks in the data processing pipeline?', This question tests understanding of a common performance issue in APIs. The reviewer's comment strongly suggests latency problems with the endpoint, specifically mentioning 'RateLimiter,' which indicates a potential problem with requests being throttled – this is a key aspect of API design and optimization. Choosing this option demonstrates an ability to connect technical terms like
RateLimiter with their practical implications in performance monitoring.23 / 25
Reviewer: 'Our application is experiencing intermittent performance degradation during peak usage. We've identified a spike in requests hitting the Authentication Service and are seeing increased latency. Can you investigate if there's an issue with the AuthenticationServiceTimeout or potential bottlenecks within the service itself?', The reviewer is specifically referencing a time limit configured for the Authentication Service. While all options could potentially contribute to performance issues, 'Authentication Service Timeout' directly addresses the identified problem – requests hitting this service are experiencing increased latency. The other options (Request Volume Monitor, Database Connection Pool Exhaustion, and Network Bandwidth Saturation) represent broader monitoring categories that might *indicate* a problem but don't pinpoint the root cause in this scenario.
24 / 25
Reviewer: 'The application is throwing a NullPointerException when attempting to access the user profile data. We've recently deployed version 2.3 of the User Service. Can you investigate if there's an issue with the service itself, or perhaps a regression in the recent deployment?', Developer: 'I've rolled back to version 2.2 and the error is gone. I'm going to file a bug report.'This scenario highlights the importance of accurately describing errors in technical contexts. The developer correctly identified a problem related to a code change (version 2.3), which aligns with reporting a regression. Options A and B are irrelevant; A focuses on connectivity, while B is asking for documentation – neither addresses the core issue. Option D is an inappropriate troubleshooting step.
25 / 25
Reviewer: 'The service is returning 500 Internal Server Errors intermittently. We've been monitoring the Kubernetes cluster and see a high CPU usage on one of the pods running the Order Processing Service. Can you investigate if there's an issue with resource allocation or potential bottlenecks within the service itself?'
Developer: 'I've scaled up the pod to 4 cores, but the errors are still occurring. I suspect it might be related to excessive logging.'This question tests understanding of common troubleshooting steps in a development environment. The correct answer focuses on logging – excessive logging can significantly impact performance and often contributes to errors like 500 Internal Server Errors. Options A and D are irrelevant; redesigns and new deployments don't directly address high CPU usage or log volume. Option B is incorrect because simply increasing memory doesn't solve a problem caused by inefficient code or resource-intensive operations.
Next up:
Articles & Prepositions →
Frequently Asked Questions
What will I practise in "IT Compound Nouns & Abbreviations — Grammar Exercise"?
Practice forming and expanding IT compound nouns and abbreviations. 5 exercises on technical terms like CI/CD, load balancer, pull request, and file server.
How many exercises are in this module?
This module has 25 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.