Restrictive vs Non-Restrictive Appositives in Technical English
5 exercises — practise comma rules for essential vs extra appositive information.
0 / 20 completed
1 / 20
The company uses several databases. Which sentence correctly punctuates a RESTRICTIVE appositive that identifies which specific database is meant?
"The database Postgres handles all transactional workloads" is correct: since the company uses several databases, the name "Postgres" is essential to identify which one is meant, making this a restrictive appositive that takes no commas. Option B incorrectly sets "Postgres" off with commas, which would only be appropriate if there were just one database and the name were extra, non-essential information. Option C and D use inconsistent, partial comma placement (only before or only after the appositive), which is grammatically invalid — restrictive appositives take no commas at all, and non-restrictive ones need commas on both sides.
2 / 20
The company has exactly one CTO. Which sentence correctly punctuates a NON-RESTRICTIVE appositive that adds extra, non-essential information about her?
"Our CTO, Elena Petrova, announced the new architecture roadmap" is correct: since there is only one CTO, her name is additional, non-essential information rather than identifying information, so it must be set off with a comma both before and after the appositive. Option A omits the necessary commas, which incorrectly presents "Elena Petrova" as if it were essential to identify which CTO is meant, treating it as restrictive. Option C includes only the closing comma, an inconsistent and invalid partial punctuation pattern. Option D wrongly inserts a comma between "Our" and "CTO", splitting the noun phrase itself rather than setting off the appositive correctly.
3 / 20
Which sentence correctly punctuates a non-restrictive appositive describing a well-known, uniquely identified tool?
"The build tool, Webpack, bundles all our frontend assets" is correct here because the context implies there is one specific, already-understood build tool, and "Webpack" is supplementary naming information, so it is properly set off with commas on both sides as a non-restrictive appositive. Option B omits both commas, which would only be correct if multiple build tools existed and "Webpack" were needed to specify which one, making it restrictive instead. Option C uses only a trailing comma, an inconsistent punctuation pattern that isn't valid for either restrictive or non-restrictive appositives. Option D incorrectly inserts a comma right after "The", breaking up the noun phrase "the build tool" itself.
4 / 20
The team maintains multiple microservices. Which sentence correctly punctuates a restrictive appositive that specifies which microservice caused the outage?
"The microservice payment-gateway caused last night's outage" is correct: because multiple microservices exist, naming "payment-gateway" is essential to identify which one is being discussed, so no commas should separate it from "the microservice" — this is a restrictive appositive. Option A incorrectly adds commas around "payment-gateway", which would wrongly suggest the name is extra, non-identifying information even though it's actually necessary here. Option C adds only a trailing comma, an invalid mixed punctuation pattern. Option D inserts an erroneous comma directly after "The", incorrectly breaking the noun phrase.
5 / 20
Which sentence correctly distinguishes a restrictive appositive from a non-restrictive one across two clauses in the same sentence?
"The framework React was chosen over the framework Vue for this project" is correct: since the sentence explicitly compares two named frameworks, each name is essential to distinguish one framework from the other, making both appositives restrictive and requiring no commas. Option A inconsistently punctuates the first appositive as if restrictive-with-a-stray-comma and the second as fully non-restrictive, which contradicts the parallel, identifying role both names play. Option C similarly mixes comma treatment across the two parallel appositives and adds an unnecessary comma before "for this project". Option D inserts random, ungrammatical commas around "was chosen" that don't correspond to any valid appositive or clause boundary.
6 / 20
John, our lead backend engineer, just submitted a pull request to integrate with the new Kafka cluster. In your code review comment, how should you best describe Kafka to another reviewer?
This is an example of a non-restrictive appositive. It provides extra information about Kafka – specifically its longevity and established use within the team. The commas indicate that the addition isn't essential to identifying 'John'; we already know *which* engineer submitted the PR. Option A is too vague, option C implies it's new, and option D doesn't include this crucial detail.
7 / 20
During a Slack discussion about debugging performance issues in the PaymentService, Sarah mentions: 'The transactionId was unusually long – it was 64 characters long.' Which of the following sentences correctly punctuates this phrase?
Here, 'transactionId' is the subject. The phrase 'it was 64 characters long' provides extra detail about the length of the ID, which isn't crucial to identifying *which* transaction we're talking about. Using commas here would incorrectly create a restrictive clause, implying that only this specific transaction has a 64-character ID. Option A incorrectly uses a semicolon; option C uses a hyphen unnecessarily; and option D is overly verbose.
8 / 20
In a PR description for a new feature that utilizes the GraphQL API, you want to briefly explain what GraphQL is. Which sentence best demonstrates correct punctuation?
This uses a non-restrictive appositive to define GraphQL. The commas signal that the definition is supplemental information – we already know we're talking about an API. Options B, C, and D either add unnecessary clauses or use incorrect punctuation (hyphens and 'and' respectively) that would create restrictive phrasing.
9 / 20
During a standup update, Mark says: 'The ErrorCode 404 is frequently reported in the UserAuthentication module.' How should this be presented to ensure clarity for your team?
This correctly uses a non-restrictive appositive to identify the specific error code. The commas indicate this information is additional and doesn't limit our understanding of 'ErrorCode 404'. Options B, C, and D add clauses that are unnecessary and would create restrictive phrasing if not properly punctuated.
10 / 20
You're writing a comment on a code review for a function called DatabaseConnection. You want to add detail about the specific database it connects to. Which sentence is correctly punctuated?
This demonstrates a non-restrictive appositive – it provides extra information about *which* database. The commas show that knowing it's connected to PostgreSQL doesn't limit our understanding of the function itself. Options B, C, and D introduce unnecessary clauses or use incorrect punctuation resulting in restrictive phrasing.
11 / 20
John, our lead backend engineer, just submitted a pull request to integrate with the new Kafka cluster. In your code review comment, how should you best describe Kafka to another reviewer?
This is an example of a non-restrictive appositive. It provides extra information about Kafka – specifically its longevity and established use within the team. The commas indicate that the addition isn't essential to identifying 'John'; we already know *which* engineer submitted the PR. Option A is too vague, option C implies it's new, and option D doesn't include this crucial detail.
12 / 20
During a Slack discussion about debugging performance issues in the PaymentService, Sarah mentions: 'The transactionId was unusually long – it was 64 characters long.' Which of the following sentences correctly punctuates this phrase?
Here, 'transactionId' is the subject. The phrase 'it was 64 characters long' provides extra detail about the length of the ID, which isn't crucial to identifying *which* transaction we're talking about. Using commas here would incorrectly create a restrictive clause, implying that only this specific transaction has a 64-character ID. Option A incorrectly uses a semicolon; option C uses a hyphen unnecessarily; and option D is overly verbose.
13 / 20
In a PR description for a new feature that utilizes the GraphQL API, you want to briefly explain what GraphQL is. Which sentence best demonstrates correct punctuation?
This uses a non-restrictive appositive to define GraphQL. The commas signal that the definition is supplemental information – we already know we're talking about an API. Options B, C, and D either add unnecessary clauses or use incorrect punctuation (hyphens and 'and' respectively) that would create restrictive phrasing.
14 / 20
During a standup update, Mark says: 'The ErrorCode 404 is frequently reported in the UserAuthentication module.' How should this be presented to ensure clarity for your team?
This correctly uses a non-restrictive appositive to identify the specific error code. The commas indicate this information is additional and doesn't limit our understanding of 'ErrorCode 404'. Options B, C, and D add clauses that are unnecessary and would create restrictive phrasing if not properly punctuated.
15 / 20
You're writing a comment on a code review for a function called DatabaseConnection. You want to add detail about the specific database it connects to. Which sentence is correctly punctuated?
This demonstrates a non-restrictive appositive – it provides extra information about *which* database. The commas show that knowing it's connected to PostgreSQL doesn't limit our understanding of the function itself. Options B, C, and D introduce unnecessary clauses or use incorrect punctuation resulting in restrictive phrasing.
16 / 20
John, our lead backend engineer, just submitted a pull request to integrate with the new Kafka cluster. In your code review comment, how should you best describe Kafka to another reviewer?
This is an example of a non-restrictive appositive. It provides extra information about Kafka – specifically its longevity and established use within the team. The commas indicate that the addition isn't essential to identifying 'John'; we already know *which* engineer submitted the PR. Option A is too vague, option C implies it's new, and option D doesn't include this crucial detail.
17 / 20
During a Slack discussion about debugging performance issues in the PaymentService, Sarah mentions: 'The transactionId was unusually long – it was 64 characters long.' Which of the following sentences correctly punctuates this phrase?
Here, 'transactionId' is the subject. The phrase 'it was 64 characters long' provides extra detail about the length of the ID, which isn't crucial to identifying *which* transaction we're talking about. Using commas here would incorrectly create a restrictive clause, implying that only this specific transaction has a 64-character ID. Option A incorrectly uses a semicolon; option C uses a hyphen unnecessarily; and option D is overly verbose.
18 / 20
In a PR description for a new feature that utilizes the GraphQL API, you want to briefly explain what GraphQL is. Which sentence best demonstrates correct punctuation?
This uses a non-restrictive appositive to define GraphQL. The commas signal that the definition is supplemental information – we already know we're talking about an API. Options B, C, and D either add unnecessary clauses or use incorrect punctuation (hyphens and 'and' respectively) that would create restrictive phrasing.
19 / 20
During a standup update, Mark says: 'The ErrorCode 404 is frequently reported in the UserAuthentication module.' How should this be presented to ensure clarity for your team?
This correctly uses a non-restrictive appositive to identify the specific error code. The commas indicate this information is additional and doesn't limit our understanding of 'ErrorCode 404'. Options B, C, and D add clauses that are unnecessary and would create restrictive phrasing if not properly punctuated.
20 / 20
You're writing a comment on a code review for a function called DatabaseConnection. You want to add detail about the specific database it connects to. Which sentence is correctly punctuated?
This demonstrates a non-restrictive appositive – it provides extra information about *which* database. The commas show that knowing it's connected to PostgreSQL doesn't limit our understanding of the function itself. Options B, C, and D introduce unnecessary clauses or use incorrect punctuation resulting in restrictive phrasing.
What will I practise in "Restrictive vs Non-Restrictive Appositives — IT Grammar Exercise"?
Practise punctuating restrictive (essential, no commas) and non-restrictive (extra, comma-set-off) appositives when naming tools, systems, and people in
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.