AI Coding Tool Limitations — Vocabulary
Practise the language developers use when talking about what AI coding tools get wrong — incorrect suggestions, hallucinated APIs, and the importance of verifying AI output before shipping.
0 / 26 completed
1 / 26
A developer says: 'The Copilot ___ is incorrect — it's calling a method that doesn't exist on this object.'
'The suggestion is incorrect' is the direct way to say the AI's proposed code is wrong. It may look plausible — syntactically valid and logically structured — but produce incorrect results or reference things that don't exist.
2 / 26
The AI generated a call to `stripe.charges.createInstant()`. After checking the Stripe docs, you discover this is a ___ API — it was never real.
A hallucinated API is one the AI fabricated — often it sounds plausible and follows the naming conventions of the real library, making it easy to miss without checking the documentation. Always verify unfamiliar method calls against official sources.
3 / 26
Your tech lead's rule is: 'Always ___ AI output before you push.' What does this mean in practice?
Verifying AI output means actively checking that the code does what it claims — reading it critically, consulting official docs for any unfamiliar methods, running tests, and understanding the logic before shipping it.
4 / 26
Copilot suggests a React hook that was valid in React 16 but is deprecated in React 18. This is an example of ___ ___ ___ causing an incorrect suggestion.
AI models have a training data cutoff — they don't know about library updates, deprecations, or new APIs released after that date. For fast-moving ecosystems like React or cloud SDKs, always cross-check suggestions against the current documentation.
5 / 26
The concept of '___ ___ of AI tools' means a developer must review and own all AI-generated code they commit.
Responsible use of AI tools means understanding that AI-generated code is a starting point, not a finished product. The developer who commits the code owns it — and is accountable for its correctness, security, and maintainability.
6 / 26
git diff
fetchUserAddress and move on.' What is the *underlying issue* David is missing here regarding the AI assistant's suggestion?David's response misses the core problem: 'Hallucination.' While context and bias are relevant considerations, the immediate issue is that the AI is generating code (
get_user_address()) that doesn't actually exist within the project. This indicates a fundamental failure of the AI to accurately represent the system – it's *hallucinating* functionality. Overfitting and bias would be secondary concerns, and insufficient context doesn't fully explain why an entirely fabricated function is being suggested.7 / 26
During a Slack discussion about integrating with a new AI coding tool, Mark says: 'I'm seeing Copilot consistently suggesting boilerplate code for data validation – it's incredibly convenient, but I worry it might be reinforcing bad practices if we don't actively challenge its assumptions.' What is the *primary concern* Mark raises regarding reliance on AI-generated suggestions like this?
Mark's concern highlights the potential for 'algorithmic bias,' where AI models learn from flawed or incomplete datasets. Blindly accepting suggestions without critical evaluation can perpetuate these biases and lead to suboptimal code practices. While convenience is a benefit of these tools, developers must remain vigilant about validating any AI-generated output to ensure it aligns with best practices and doesn't introduce unintended consequences. The correct answer focuses on the importance of active challenge, not simply accepting efficiency.
8 / 26
During a standup update, Alex reports: 'The AI assistant suggested using `async/await` everywhere in my new service. While it's technically correct, I'm concerned about potential performance overhead and increased complexity – it feels like overkill for some of these simple operations.' What is the *key distinction* Alex is highlighting regarding the AI assistant's suggestion?
Alex's concern centers on the AI's lack of contextual awareness. While
async/await is a valid JavaScript feature, it isn't always the optimal solution—introducing overhead and complexity that aren't necessarily justified by the task at hand. The AI tool often prioritizes generating code based on popular patterns without fully assessing their suitability for the specific situation, demonstrating a critical limitation in its reasoning.9 / 26
# PR Description: Refactor User Profile Service - AI Assisted
This question tests understanding of AI limitations regarding security. The incorrect options focus on accepting the AI's output blindly or misinterpreting its intention. The correct answer emphasizes that AI lacks inherent awareness of security best practices and can generate insecure code if not carefully scrutinized. It's crucial to remember that AI tools lack contextual understanding, so simply 'getting it right' doesn't guarantee a secure solution.
10 / 26
git diff
fetchUserAddress and move on.' What is the *underlying issue* David is missing here regarding the AI assistant's suggestion?David's response misses the core problem: 'Hallucination.' While context and bias are relevant considerations, the immediate issue is that the AI is generating code (
get_user_address()) that doesn't actually exist within the project. This indicates a fundamental failure of the AI to accurately represent the system – it's *hallucinating* functionality. Overfitting and bias would be secondary concerns, and insufficient context doesn't fully explain why an entirely fabricated function is being suggested.11 / 26
During a Slack discussion about integrating with a new AI coding tool, Mark says: 'I'm seeing Copilot consistently suggesting boilerplate code for data validation – it's incredibly convenient, but I worry it might be reinforcing bad practices if we don't actively challenge its assumptions.' What is the *primary concern* Mark raises regarding reliance on AI-generated suggestions like this?
Mark's concern highlights the potential for 'algorithmic bias,' where AI models learn from flawed or incomplete datasets. Blindly accepting suggestions without critical evaluation can perpetuate these biases and lead to suboptimal code practices. While convenience is a benefit of these tools, developers must remain vigilant about validating any AI-generated output to ensure it aligns with best practices and doesn't introduce unintended consequences. The correct answer focuses on the importance of active challenge, not simply accepting efficiency.
12 / 26
During a standup update, Alex reports: 'The AI assistant suggested using `async/await` everywhere in my new service. While it's technically correct, I'm concerned about potential performance overhead and increased complexity – it feels like overkill for some of these simple operations.' What is the *key distinction* Alex is highlighting regarding the AI assistant's suggestion?
Alex's concern centers on the AI's lack of contextual awareness. While
async/await is a valid JavaScript feature, it isn't always the optimal solution—introducing overhead and complexity that aren't necessarily justified by the task at hand. The AI tool often prioritizes generating code based on popular patterns without fully assessing their suitability for the specific situation, demonstrating a critical limitation in its reasoning.13 / 26
# PR Description: Refactor User Profile Service - AI Assisted
This question tests understanding of AI limitations regarding security. The incorrect options focus on accepting the AI's output blindly or misinterpreting its intention. The correct answer emphasizes that AI lacks inherent awareness of security best practices and can generate insecure code if not carefully scrutinized. It's crucial to remember that AI tools lack contextual understanding, so simply 'getting it right' doesn't guarantee a secure solution.
14 / 26
git diff
fetchUserAddress and move on.' What is the *underlying issue* David is missing here regarding the AI assistant's suggestion?David's response misses the core problem: 'Hallucination.' While context and bias are relevant considerations, the immediate issue is that the AI is generating code (
get_user_address()) that doesn't actually exist within the project. This indicates a fundamental failure of the AI to accurately represent the system – it's *hallucinating* functionality. Overfitting and bias would be secondary concerns, and insufficient context doesn't fully explain why an entirely fabricated function is being suggested.15 / 26
During a Slack discussion about integrating with a new AI coding tool, Mark says: 'I'm seeing Copilot consistently suggesting boilerplate code for data validation – it's incredibly convenient, but I worry it might be reinforcing bad practices if we don't actively challenge its assumptions.' What is the *primary concern* Mark raises regarding reliance on AI-generated suggestions like this?
Mark's concern highlights the potential for 'algorithmic bias,' where AI models learn from flawed or incomplete datasets. Blindly accepting suggestions without critical evaluation can perpetuate these biases and lead to suboptimal code practices. While convenience is a benefit of these tools, developers must remain vigilant about validating any AI-generated output to ensure it aligns with best practices and doesn't introduce unintended consequences. The correct answer focuses on the importance of active challenge, not simply accepting efficiency.
16 / 26
During a standup update, Alex reports: 'The AI assistant suggested using `async/await` everywhere in my new service. While it's technically correct, I'm concerned about potential performance overhead and increased complexity – it feels like overkill for some of these simple operations.' What is the *key distinction* Alex is highlighting regarding the AI assistant's suggestion?
Alex's concern centers on the AI's lack of contextual awareness. While
async/await is a valid JavaScript feature, it isn't always the optimal solution—introducing overhead and complexity that aren't necessarily justified by the task at hand. The AI tool often prioritizes generating code based on popular patterns without fully assessing their suitability for the specific situation, demonstrating a critical limitation in its reasoning.17 / 26
# PR Description: Refactor User Profile Service - AI Assisted
This question tests understanding of AI limitations regarding security. The incorrect options focus on accepting the AI's output blindly or misinterpreting its intention. The correct answer emphasizes that AI lacks inherent awareness of security best practices and can generate insecure code if not carefully scrutinized. It's crucial to remember that AI tools lack contextual understanding, so simply 'getting it right' doesn't guarantee a secure solution.
18 / 26
git diff
fetchUserAddress and move on.' What is the *underlying issue* David is missing here regarding the AI assistant's suggestion?David's response misses the core problem: 'Hallucination.' While context and bias are relevant considerations, the immediate issue is that the AI is generating code (
get_user_address()) that doesn't actually exist within the project. This indicates a fundamental failure of the AI to accurately represent the system – it's *hallucinating* functionality. Overfitting and bias would be secondary concerns, and insufficient context doesn't fully explain why an entirely fabricated function is being suggested.19 / 26
During a Slack discussion about integrating with a new AI coding tool, Mark says: 'I'm seeing Copilot consistently suggesting boilerplate code for data validation – it's incredibly convenient, but I worry it might be reinforcing bad practices if we don't actively challenge its assumptions.' What is the *primary concern* Mark raises regarding reliance on AI-generated suggestions like this?
Mark's concern highlights the potential for 'algorithmic bias,' where AI models learn from flawed or incomplete datasets. Blindly accepting suggestions without critical evaluation can perpetuate these biases and lead to suboptimal code practices. While convenience is a benefit of these tools, developers must remain vigilant about validating any AI-generated output to ensure it aligns with best practices and doesn't introduce unintended consequences. The correct answer focuses on the importance of active challenge, not simply accepting efficiency.
20 / 26
During a standup update, Alex reports: 'The AI assistant suggested using `async/await` everywhere in my new service. While it's technically correct, I'm concerned about potential performance overhead and increased complexity – it feels like overkill for some of these simple operations.' What is the *key distinction* Alex is highlighting regarding the AI assistant's suggestion?
Alex's concern centers on the AI's lack of contextual awareness. While
async/await is a valid JavaScript feature, it isn't always the optimal solution—introducing overhead and complexity that aren't necessarily justified by the task at hand. The AI tool often prioritizes generating code based on popular patterns without fully assessing their suitability for the specific situation, demonstrating a critical limitation in its reasoning.21 / 26
# PR Description: Refactor User Profile Service - AI Assisted
This question tests understanding of AI limitations regarding security. The incorrect options focus on accepting the AI's output blindly or misinterpreting its intention. The correct answer emphasizes that AI lacks inherent awareness of security best practices and can generate insecure code if not carefully scrutinized. It's crucial to remember that AI tools lack contextual understanding, so simply 'getting it right' doesn't guarantee a secure solution.
22 / 26
During a code review, Emily writes in the comments: 'The AI tool's suggestion to use `try...except` blocks for *every* potential error condition seems overly cautious. While robust, it might introduce unnecessary complexity and impact performance. Do you think this is a valid concern?'
This question tests understanding of 'overly cautious' in the context of AI-generated code. The correct answer acknowledges that while robust error handling is generally good practice, *excessive* use can negatively impact performance and potentially obscure design flaws. The other options misinterpret the core concern about complexity and potential performance bottlenecks.
23 / 26
In a Slack channel discussing the output of an AI coding assistant, David says: 'I'm finding that the tool consistently generates code snippets with verbose logging statements. While helpful for debugging during development, it might not be ideal for production environments where log volume needs to be carefully managed.' What does David primarily mean?
David is raising a concern about operational efficiency. The AI may prioritize developer convenience (easy debugging) over best practices like managing log volume in production. The other options misrepresent the situation – logging isn't inherently a vulnerability and doesn't always require immediate attention from the assistant.
24 / 26
During a PR review, a developer notes: 'The AI suggested using a complex regular expression to validate user input. While functional, it's difficult to maintain and understand, potentially leading to future bugs. I'm concerned about the long-term maintainability.' What is the *primary* issue highlighted here?
The question focuses on 'technical debt.' Complex regular expressions are notoriously difficult to maintain and debug over time. While performance and security could be secondary concerns, the core issue is the increased risk of future bugs and maintenance problems – this is what David was referring to.
25 / 26
A developer writes in a standup update: 'The AI assistant generated code that uses a global variable extensively. I'm worried this could lead to unpredictable behavior and make debugging harder.' What is the main concern expressed here?
This question tests understanding of common anti-patterns. Excessive use of global variables introduces significant risks – namely, making debugging more difficult due to the potential for unpredictable behavior and unintended side effects. The other options represent specific concurrency issues or coding standard violations which are not the primary concern.
26 / 26
In a code review comment, you see: 'The AI provided this API call without specifying any error handling. It's a potential risk; we need to add `try...except` blocks.' What is the most important reason for adding error handling in this case?
The core reason for adding error handling is to handle 'unexpected responses.' APIs can fail – network issues, server errors, invalid data. Without error handling, the application would crash or behave unpredictably when these situations occur. The other options represent secondary considerations regarding readability, coding standards, or security.
Frequently Asked Questions
What will I practice in "AI Coding Tool Limitations — Vocabulary"?
This is an AI Code Generation Tools exercise set. It walks through 26 scenario-based multiple-choice questions built around real usage of AI Code Generation Tools terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 26 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the AI Code Generation Tools vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more AI Code Generation Tools exercises?
See the AI Code Generation Tools exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — AI Code Generation Tools vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.