5 exercises — practise choosing between as (role/function) and like (resemblance) in technical writing.
0 / 18 completed
1 / 18
Choose the sentence that correctly uses "as" to describe a role or function, not a similarity:
"Acts as a reverse proxy" is correct: "as" is used to describe a role, function, or capacity that something actually has — the container genuinely functions as a reverse proxy, it is not merely similar to one. "Like" (option C) would incorrectly imply the container merely resembles a reverse proxy without actually being one, which changes the meaning and is factually misleading in a technical description. Option A uses a nonstandard preposition combination. Option B ("acts alike") is grammatically incorrect — "alike" is a predicate adjective used differently ("the two systems are alike"), not a preposition that can follow "acts" this way.
2 / 18
Which sentence correctly uses "like" to express similarity/resemblance, followed by a noun phrase?
"Behaves like a timeout" is correct: "like" + noun phrase expresses resemblance or similarity — the error only resembles a timeout in its symptoms, it is not actually one ("though the root cause is different" confirms this is a comparison of appearance, not identity). "As" (option C) would incorrectly claim the error genuinely IS a timeout in function/category, contradicting "the root cause is different". Options A and B use "such" and "so", neither of which functions as a comparison preposition before a bare noun phrase in this way.
3 / 18
Choose the sentence with the correct use of "as" to introduce a full clause (subject + verb) of comparison:
"As the production environment is configured" is correct: "as" (not "like") is the standard, formally correct choice for introducing a full clause with its own subject and verb in a comparison — "as X is/does" is the traditional grammatical rule, though "like" is increasingly common informally in this position too. In formal technical documentation, "as" remains the more precise and widely accepted choice before a clause. Option A uses "like" before a full clause, which many style guides for formal/technical writing still flag as informal or incorrect. Option C additionally drops the article "the" before "production environment". Option D adds the redundant "same" before "as", which is unnecessary and slightly awkward phrasing not matching a clean comparative clause structure.
4 / 18
Which sentence correctly distinguishes "as" (actual identity/role) from "like" (mere resemblance) across two clauses describing a design pattern?
Option C is fully correct: "functions as a translation layer" (genuine role, not mere resemblance), "as the system requires" (introducing a clause, formally "as" rather than "like"), and "serves as this role" (again, genuine role/identity) are all consistent with the actual-identity meaning throughout, which fits the sentence's own claim that the adapter "genuinely serves" this function. Option A incorrectly starts with "like" (implying mere resemblance) but then contradicts itself by saying it "genuinely serves" the role. Option B incorrectly uses "like" before the clause "the system requires", which should be "as" in formal technical writing. Option D mixes both errors — "like" before a clause and "like" describing what should be an actual identity claim about a translation layer, both of which are inconsistent with the sentence's own conclusion.
5 / 18
A code comment says: "This helper works _____ described in the RFC." Choose the correct word to introduce the following clause.
"As described in the RFC" is the correct, standard, and idiomatic choice: "as" is used before a past participle clause like "described" to mean "in the way that/manner that" — this is a very common fixed pattern ("as specified", "as documented", "as configured", "as required") throughout technical writing. "Like" (option A) is not used in this fixed participial pattern; "like described in the RFC" is not standard/idiomatic English. "Alike" (option C) is a predicate adjective and cannot introduce a clause this way. "Same" (option D) would require additional words ("the same as described") to form a grammatical comparison and cannot stand alone before a participle clause like this.
6 / 18
PR Description: "The new feature integrates with the PaymentGatewayas it was outlined in the initial design document. We've addressed the performance concerns raised during testing."
The key here is understanding that "as" in this context introduces a clause of comparison, specifically indicating *how* the new feature aligns with the original design. Using 'like' would imply a superficial resemblance rather than an actual functional correspondence. The description correctly explains that the integration mirrors the document's specifications, justifying the changes made based on performance concerns – demonstrating a clear connection between the code and its intended purpose.
7 / 18
Reviewer: 'The API response is returning data as expected. However, the latency is significantly higher than anticipated.'
Which of the following options best completes this comment, accurately reflecting the reviewer's concern about the response?
The reviewer is pointing out a discrepancy between the *observed* behavior of the API and the *expected* behavior. 'Like' would suggest a superficial resemblance; here, we need to indicate that the data format or content differs from what was anticipated. The correct phrasing highlights this difference in behavior, crucial for identifying potential issues during code review. Using 'like' would imply a simple similarity, which doesn't capture the core of the problem.
8 / 18
PR Description: "The new feature integrates with the PaymentGatewayas it was outlined in the initial design document. We've addressed the performance concerns raised during testing."
The key here is understanding that "as" in this context introduces a clause of comparison, specifically indicating *how* the new feature aligns with the original design. Using 'like' would imply a superficial resemblance rather than an actual functional correspondence. The description correctly explains that the integration mirrors the document's specifications, justifying the changes made based on performance concerns – demonstrating a clear connection between the code and its intended purpose.
9 / 18
Reviewer: 'The API response is returning data as expected. However, the latency is significantly higher than anticipated.'
Which of the following options best completes this comment, accurately reflecting the reviewer's concern about the response?
The reviewer is pointing out a discrepancy between the *observed* behavior of the API and the *expected* behavior. 'Like' would suggest a superficial resemblance; here, we need to indicate that the data format or content differs from what was anticipated. The correct phrasing highlights this difference in behavior, crucial for identifying potential issues during code review. Using 'like' would imply a simple similarity, which doesn't capture the core of the problem.
10 / 18
PR Description: "The new feature integrates with the PaymentGatewayas it was outlined in the initial design document. We've addressed the performance concerns raised during testing."
The key here is understanding that "as" in this context introduces a clause of comparison, specifically indicating *how* the new feature aligns with the original design. Using 'like' would imply a superficial resemblance rather than an actual functional correspondence. The description correctly explains that the integration mirrors the document's specifications, justifying the changes made based on performance concerns – demonstrating a clear connection between the code and its intended purpose.
11 / 18
Reviewer: 'The API response is returning data as expected. However, the latency is significantly higher than anticipated.'
Which of the following options best completes this comment, accurately reflecting the reviewer's concern about the response?
The reviewer is pointing out a discrepancy between the *observed* behavior of the API and the *expected* behavior. 'Like' would suggest a superficial resemblance; here, we need to indicate that the data format or content differs from what was anticipated. The correct phrasing highlights this difference in behavior, crucial for identifying potential issues during code review. Using 'like' would imply a simple similarity, which doesn't capture the core of the problem.
12 / 18
PR Description: "The new feature integrates with the PaymentGatewayas it was outlined in the initial design document. We've addressed the performance concerns raised during testing."
The key here is understanding that "as" in this context introduces a clause of comparison, specifically indicating *how* the new feature aligns with the original design. Using 'like' would imply a superficial resemblance rather than an actual functional correspondence. The description correctly explains that the integration mirrors the document's specifications, justifying the changes made based on performance concerns – demonstrating a clear connection between the code and its intended purpose.
13 / 18
Reviewer: 'The API response is returning data as expected. However, the latency is significantly higher than anticipated.'
Which of the following options best completes this comment, accurately reflecting the reviewer's concern about the response?
The reviewer is pointing out a discrepancy between the *observed* behavior of the API and the *expected* behavior. 'Like' would suggest a superficial resemblance; here, we need to indicate that the data format or content differs from what was anticipated. The correct phrasing highlights this difference in behavior, crucial for identifying potential issues during code review. Using 'like' would imply a simple similarity, which doesn't capture the core of the problem.
14 / 18
John, a senior developer, explained that the new microservice should operate exactly as defined in the service specification. Which sentence best reflects this statement using 'as' correctly?
'As' here indicates an *exact* match or conformity with a defined standard (the service specification). Option 1 uses 'as' incorrectly implying similarity. Options 3 and 4 are less precise; 'like' would be appropriate for describing resemblance, while 'as' denotes identical operation.
15 / 18
During a Slack conversation with the QA team, Sarah reported: 'The API response is returning data like we saw in the mock responses.' What word best completes this sentence to accurately convey Sarah's observation?
'Like' is used here to express *resemblance* or similarity in appearance. The key distinction is that 'as' signifies an exact copy or mirroring of something – Sarah isn't saying the response is identical; she's noting it looks similar to a known example. 'As' would imply an identical replication.
16 / 18
David wrote in his PR description: 'The new authentication flow integrates with the legacy system as it was documented in the system architecture.' Which sentence correctly uses 'as' to introduce a full clause of comparison?
'As' introduces a clause that *compares* the authentication flow to the documentation. Option 0 correctly uses 'as' to introduce the full clause (subject + verb). Options 1 and 2 use 'like' incorrectly; 'as' is required when introducing a comparative statement.
17 / 18
A code review comment reads: 'The database query returns results as the design document outlined.' Which of the following best explains the intended meaning?
'As' emphasizes a strict adherence to the design document – it means the results are *identical* to what was planned. Using 'like' would suggest similarity, but the comment implies precise matching. The other options use less precise language.
18 / 18
Maria states in her standup update: 'The API endpoint is behaving as expected after the recent deployment.' What does she mean by this statement?
'As expected' signifies that the API endpoint is functioning *exactly* as it was designed and documented. It implies full compliance with specifications – any deviation would be considered an issue. 'Like' would suggest a superficial similarity.
What will I practise in "As vs. Like in Comparisons in Technical English — IT Grammar Exercise"?
Practise the distinction between as (role, function, or introducing a clause) and like (similarity, followed by a noun) in technical descriptions, design docs
How many exercises are in this module?
This module has 18 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.