5 exercises — practise hyphenating "as-is" as a premodifier versus "as is" predicatively.
0 / 26 completed
1 / 26
Which sentence correctly hyphenates "as-is" when it directly modifies a following noun?
"We shipped an as-is copy of the legacy config to unblock the migration" is correct: as a compound adjective directly before the noun "copy", "as-is" is hyphenated. Option B omits the hyphen in the premodifying position, which is inconsistent with standard compound-adjective hyphenation. Option C incorrectly hyphenates the noun into the compound as well. Option D places "as-is" after the noun it's meant to modify, breaking the premodifier pattern.
2 / 26
Choose the sentence that correctly uses the unhyphenated predicative phrase "as is" after a noun, meaning "in its current, unmodified state".
"The ticket says to ship the current build as is, without further cleanup" is correct: in the predicative (post-noun, non-modifying) position, "as is" is conventionally written without a hyphen. Option B applies the premodifier's hyphen here too, which most style guides reserve for the compound-adjective position instead. Option C redundantly appends "is" after an already complete idiom. Option D substitutes the ungrammatical "like is".
3 / 26
Select the sentence that correctly uses "as-is" to describe accepting a system's current, unpatched state without changes.
"...an as-is acceptance of the current API version, with no further changes planned" is correct: "as-is" premodifies "acceptance" as a hyphenated compound adjective, and "an" is used because "as-is" starts with a vowel sound. Option B substitutes the full clause "as it is", which isn't the fixed idiom form. Option C incorrectly uses "a" instead of "an" before the vowel sound. Option D over-hyphenates by joining the noun into the compound.
4 / 26
Which sentence correctly uses "as is" (predicative, no hyphen) at the end of a clause in a release note disclaimer?
"This beta feature is provided as is, with no guarantee of stability" is correct: in this common legal/disclaimer pattern, "as is" follows the verb without a hyphen, since it's not directly premodifying a noun. Option B applies the premodifier hyphenation in a predicative slot. Option C incorrectly reorders the phrase before "provided". Option D confuses the idiom with the unrelated hypothetical phrase "as it were".
5 / 26
Choose the sentence that correctly contrasts hyphenated premodifying "as-is" and unhyphenated predicative "as is" within the same sentence.
"The as-is workaround stays in place until the real fix ships; until then, the service runs as is" is correct: the first instance premodifies "workaround" (hyphenated), and the second is predicative after "runs" (unhyphenated) — both following the conventional pattern. Option B reverses the hyphenation in both positions. Option C uses the hyphen in the predicative position too. Option D drops the hyphen from the premodifying position.
6 / 26
During a code review of the new payment API, Sarah flagged a potential issue. Here's her comment:
`"The API returns the transaction status as 'as is', which doesn't provide enough detail for our reporting needs."`
Which phrasing would be most appropriate to suggest to Sarah?
Sarah's comment highlights a potential issue because 'as is' often implies returning data in its original format without transformation or enrichment. This can be insufficient for detailed reporting and analysis. Option 1 accurately reflects this concern – that the response lacks critical details. Options B and C are misinterpretations of what 'as is' means, while option D suggests an acceptable practice that isn't always appropriate.
7 / 26
Mark just submitted a PR updating the user profile API. During review, you notice this comment from Liam:
`"The response from the get_user endpoint is returned as 'as is', which doesn't include any error codes. This makes it difficult to diagnose issues."`
Which of the following suggestions would be most constructive for Liam to offer?
This question focuses on providing constructive feedback in a code review context. Liam's comment highlights a potential issue – the lack of error codes – which is a common concern in API design. Option A directly addresses this by suggesting a solution (adding an error code field), making it the most helpful suggestion. Options B and C simply dismiss the problem or advocate for overly strict requirements, while option D is unnecessarily aggressive.
8 / 26
During a code review of the new user authentication API, David pointed out a potential security vulnerability. Here's his comment:
`"The server returns the user's password as 'as is', which violates our security policy and exposes sensitive data."`
Which of the following responses would be most helpful for David?
David correctly identified a serious problem: returning passwords in plain text. Option A dismisses the issue without proper action. Option B suggests an impractical immediate solution. Option C attempts to rationalize a bad practice and misrepresents the policy's intent. Option D, however, accurately reflects the severity of the situation and proposes a necessary course of action – prioritizing hashing for security.
9 / 26
Liam is reviewing the implementation of a new microservice responsible for processing user orders. He notices that the service consistently returns order details as a JSON string: `{"orderId": "12345", "userId": "67890", "status": "as is"}`. During Slack discussion, Sarah suggests he investigate this choice. Which of the following responses would be most helpful for Liam to offer? Consider that 'as is' in this context might not be immediately clear to other developers.
The correct answer highlights the potential issue with using 'as is' in this context. While a literal interpretation might seem acceptable, it implies that no validation or processing is occurring on the returned data. This could lead to inconsistencies and difficulties in debugging because the status isn't explicitly defined. Options A and B incorrectly focus solely on lack of detail or adherence to database format; option C correctly identifies the ambiguity of 'as is' and the need for clarification, while option D misunderstands the intended meaning.
10 / 26
During a code review of the new payment API, Sarah flagged a potential issue. Here's her comment:
`"The API returns the transaction status as 'as is', which doesn't provide enough detail for our reporting needs."`
Which phrasing would be most appropriate to suggest to Sarah?
Sarah's comment highlights a potential issue because 'as is' often implies returning data in its original format without transformation or enrichment. This can be insufficient for detailed reporting and analysis. Option 1 accurately reflects this concern – that the response lacks critical details. Options B and C are misinterpretations of what 'as is' means, while option D suggests an acceptable practice that isn't always appropriate.
11 / 26
Mark just submitted a PR updating the user profile API. During review, you notice this comment from Liam:
`"The response from the get_user endpoint is returned as 'as is', which doesn't include any error codes. This makes it difficult to diagnose issues."`
Which of the following suggestions would be most constructive for Liam to offer?
This question focuses on providing constructive feedback in a code review context. Liam's comment highlights a potential issue – the lack of error codes – which is a common concern in API design. Option A directly addresses this by suggesting a solution (adding an error code field), making it the most helpful suggestion. Options B and C simply dismiss the problem or advocate for overly strict requirements, while option D is unnecessarily aggressive.
12 / 26
During a code review of the new user authentication API, David pointed out a potential security vulnerability. Here's his comment:
`"The server returns the user's password as 'as is', which violates our security policy and exposes sensitive data."`
Which of the following responses would be most helpful for David?
David correctly identified a serious problem: returning passwords in plain text. Option A dismisses the issue without proper action. Option B suggests an impractical immediate solution. Option C attempts to rationalize a bad practice and misrepresents the policy's intent. Option D, however, accurately reflects the severity of the situation and proposes a necessary course of action – prioritizing hashing for security.
13 / 26
Liam is reviewing the implementation of a new microservice responsible for processing user orders. He notices that the service consistently returns order details as a JSON string: `{"orderId": "12345", "userId": "67890", "status": "as is"}`. During Slack discussion, Sarah suggests he investigate this choice. Which of the following responses would be most helpful for Liam to offer? Consider that 'as is' in this context might not be immediately clear to other developers.
The correct answer highlights the potential issue with using 'as is' in this context. While a literal interpretation might seem acceptable, it implies that no validation or processing is occurring on the returned data. This could lead to inconsistencies and difficulties in debugging because the status isn't explicitly defined. Options A and B incorrectly focus solely on lack of detail or adherence to database format; option C correctly identifies the ambiguity of 'as is' and the need for clarification, while option D misunderstands the intended meaning.
14 / 26
During a code review of the new payment API, Sarah flagged a potential issue. Here's her comment:
`"The API returns the transaction status as 'as is', which doesn't provide enough detail for our reporting needs."`
Which phrasing would be most appropriate to suggest to Sarah?
Sarah's comment highlights a potential issue because 'as is' often implies returning data in its original format without transformation or enrichment. This can be insufficient for detailed reporting and analysis. Option 1 accurately reflects this concern – that the response lacks critical details. Options B and C are misinterpretations of what 'as is' means, while option D suggests an acceptable practice that isn't always appropriate.
15 / 26
Mark just submitted a PR updating the user profile API. During review, you notice this comment from Liam:
`"The response from the get_user endpoint is returned as 'as is', which doesn't include any error codes. This makes it difficult to diagnose issues."`
Which of the following suggestions would be most constructive for Liam to offer?
This question focuses on providing constructive feedback in a code review context. Liam's comment highlights a potential issue – the lack of error codes – which is a common concern in API design. Option A directly addresses this by suggesting a solution (adding an error code field), making it the most helpful suggestion. Options B and C simply dismiss the problem or advocate for overly strict requirements, while option D is unnecessarily aggressive.
16 / 26
During a code review of the new user authentication API, David pointed out a potential security vulnerability. Here's his comment:
`"The server returns the user's password as 'as is', which violates our security policy and exposes sensitive data."`
Which of the following responses would be most helpful for David?
David correctly identified a serious problem: returning passwords in plain text. Option A dismisses the issue without proper action. Option B suggests an impractical immediate solution. Option C attempts to rationalize a bad practice and misrepresents the policy's intent. Option D, however, accurately reflects the severity of the situation and proposes a necessary course of action – prioritizing hashing for security.
17 / 26
Liam is reviewing the implementation of a new microservice responsible for processing user orders. He notices that the service consistently returns order details as a JSON string: `{"orderId": "12345", "userId": "67890", "status": "as is"}`. During Slack discussion, Sarah suggests he investigate this choice. Which of the following responses would be most helpful for Liam to offer? Consider that 'as is' in this context might not be immediately clear to other developers.
The correct answer highlights the potential issue with using 'as is' in this context. While a literal interpretation might seem acceptable, it implies that no validation or processing is occurring on the returned data. This could lead to inconsistencies and difficulties in debugging because the status isn't explicitly defined. Options A and B incorrectly focus solely on lack of detail or adherence to database format; option C correctly identifies the ambiguity of 'as is' and the need for clarification, while option D misunderstands the intended meaning.
18 / 26
During a code review of the new payment API, Sarah flagged a potential issue. Here's her comment:
`"The API returns the transaction status as 'as is', which doesn't provide enough detail for our reporting needs."`
Which phrasing would be most appropriate to suggest to Sarah?
Sarah's comment highlights a potential issue because 'as is' often implies returning data in its original format without transformation or enrichment. This can be insufficient for detailed reporting and analysis. Option 1 accurately reflects this concern – that the response lacks critical details. Options B and C are misinterpretations of what 'as is' means, while option D suggests an acceptable practice that isn't always appropriate.
19 / 26
Mark just submitted a PR updating the user profile API. During review, you notice this comment from Liam:
`"The response from the get_user endpoint is returned as 'as is', which doesn't include any error codes. This makes it difficult to diagnose issues."`
Which of the following suggestions would be most constructive for Liam to offer?
This question focuses on providing constructive feedback in a code review context. Liam's comment highlights a potential issue – the lack of error codes – which is a common concern in API design. Option A directly addresses this by suggesting a solution (adding an error code field), making it the most helpful suggestion. Options B and C simply dismiss the problem or advocate for overly strict requirements, while option D is unnecessarily aggressive.
20 / 26
During a code review of the new user authentication API, David pointed out a potential security vulnerability. Here's his comment:
`"The server returns the user's password as 'as is', which violates our security policy and exposes sensitive data."`
Which of the following responses would be most helpful for David?
David correctly identified a serious problem: returning passwords in plain text. Option A dismisses the issue without proper action. Option B suggests an impractical immediate solution. Option C attempts to rationalize a bad practice and misrepresents the policy's intent. Option D, however, accurately reflects the severity of the situation and proposes a necessary course of action – prioritizing hashing for security.
21 / 26
Liam is reviewing the implementation of a new microservice responsible for processing user orders. He notices that the service consistently returns order details as a JSON string: `{"orderId": "12345", "userId": "67890", "status": "as is"}`. During Slack discussion, Sarah suggests he investigate this choice. Which of the following responses would be most helpful for Liam to offer? Consider that 'as is' in this context might not be immediately clear to other developers.
The correct answer highlights the potential issue with using 'as is' in this context. While a literal interpretation might seem acceptable, it implies that no validation or processing is occurring on the returned data. This could lead to inconsistencies and difficulties in debugging because the status isn't explicitly defined. Options A and B incorrectly focus solely on lack of detail or adherence to database format; option C correctly identifies the ambiguity of 'as is' and the need for clarification, while option D misunderstands the intended meaning.
22 / 26
During a Slack discussion about the new billing microservice, Anya writes: 'The service is returning the payment amount as 'as is', without any currency formatting. This makes it difficult to display correctly in our customer dashboard.' Which of the following best describes why Anya's comment highlights a potential issue?
Anya's comment focuses on the lack of currency formatting within the 'as is' return. This directly impacts user experience and potential localization issues – failing to account for different currencies would be a significant problem. The other options represent broader coding concerns that aren't the core issue highlighted by Anya's statement.
23 / 26
You're reviewing a PR for a new API endpoint designed to retrieve customer support tickets. The developer has included this line of code: `return ticket_data as is;`. What does 'as is' typically imply in this context, and what potential problem might it represent?
'As is' in this scenario means returning the data exactly as it exists within the system—without any transformation or filtering. This can be problematic if the returned data contains sensitive information that should not be exposed directly to the client-side application, potentially violating security policies.
24 / 26
In a pull request for a new feature flag API, Ben comments: 'The server returns the feature flag status as 'as is', which doesn't include any human-readable descriptions. This makes it difficult to understand what each flag actually does.' What's the primary reason Ben raises concern about this approach?
Ben's concern stems from the absence of descriptive information alongside the 'as is' status. Feature flag names alone are often ambiguous; without accompanying descriptions, developers can't effectively understand their purpose and manage them correctly – exposing internal configurations is a secondary risk but not the core issue.
25 / 26
During a standup update, Sarah reports: 'The order processing service consistently returns order details as 'as is', including internal IDs. This makes it difficult for our reporting team to track orders accurately.' What's the most significant problem highlighted by Sarah's statement?
Sarah's comment focuses on the return of 'as is' data including internal IDs. This isn't suitable for reporting because the internal IDs are not mapped to human-readable identifiers or a standard tracking system – this directly impacts the accuracy and usability of reports.
26 / 26
You're reviewing code for a new API that retrieves user profile data. The developer has implemented: `return profile_data as is;`. Which statement best explains why this approach might be problematic from a security perspective?
Returning raw, unformatted data (as is) makes it easier for an attacker to identify and potentially exploit sensitive information contained within the profile data—even if no specific sanitization occurs. The lack of formatting itself is the vulnerability, not a direct injection attack.
What will I practise in ""As-Is" vs "As Is" (Hyphenation) — IT Grammar Exercise"?
Practise the hyphenated compound adjective "as-is" before a noun versus the unhyphenated predicative "as is" after a noun, in tickets, specifications
How many exercises are in this module?
This module has 26 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.