Practise the language developers use when discussing AI-assisted code review: flagging issues, surfacing optimizations, and writing clear PR comments that reference AI tool output.
0 / 17 completed
1 / 17
A PR comment reads: 'The ___ a potential bug on line 42 — worth checking the null path.' What did the AI tool do?
'AI flagged a potential bug' means the AI review tool marked a line or block as suspicious. It does not mean the bug is confirmed — the developer must investigate and decide whether it is a real issue or a false positive.
2 / 17
In a PR comment you write: 'Copilot ___ an optimization here — caching the result would save a DB call per request.'
'Copilot suggested an optimization' is standard PR language for sharing an AI-proposed improvement. Including the source (Copilot) keeps the review transparent — reviewers know the idea came from AI, not the author.
3 / 17
The AI review tool raised ten warnings, but after investigation you mark eight as ___. What does this term mean?
False positives are AI warnings that turn out to be incorrect. A high false-positive rate reduces trust in the tool and causes alert fatigue — developers start ignoring warnings, including real ones.
4 / 17
A team member asks: 'Should we ___ the AI suggestion or follow it?' They want to know whether to disregard the tool's advice.
A human override means a developer explicitly decides the AI suggestion is wrong or not applicable in this context. Overrides should be documented (e.g., in a PR comment) so future reviewers understand why the AI advice was not followed.
5 / 17
Your PR comment states: 'Leaving this note for transparency — ___ this pattern as a potential race condition, but I've reviewed the execution model and it cannot occur here.'
Attributing a flag to the AI tool in a PR comment is good practice — it explains the origin of the concern and shows that the developer reviewed it rather than dismissing it without thought.
6 / 17
Sarah: 'The AI flagged this as a 'high severity' issue. It suggested adding a mutex lock around the data access. I'm not sure we should be introducing locking primitives into this microservice – it feels like overkill. What does 'mutex lock' actually *do* in this context, and why is the AI flagging it so seriously?',
Considering Sarah's question and the AI's recommendation, which of the following best describes the purpose of a mutex lock?
A mutex lock is a fundamental concurrency control mechanism. It prevents multiple threads from simultaneously accessing shared resources, which can lead to data corruption or unpredictable behavior when different parts of the application try to modify the same data concurrently. The AI flagged it 'high severity' because the absence of this protection could have serious consequences – Sarah's skepticism is warranted; introducing a mutex lock might be an overreaction without fully understanding the potential race conditions.
7 / 17
PR Description: 'AI Review suggests adding a try-catch block around the database query. This addresses potential SQL injection vulnerabilities. Please review and approve.'
During a code review meeting, you're discussing this PR with your team lead, Mark. He asks, 'Why did the AI specifically recommend a try-catch block here? It seems like a bit of an overreach.'
This question tests understanding of common defensive programming practices in the context of AI-assisted code review. While SQL injection *is* a serious concern, recommending a `try-catch` block isn't solely about preventing it; it's a broader technique for robust error handling. A `try-catch` block handles exceptions that might occur during database operations (e.g., connection errors, invalid query syntax) and prevents the application from crashing or displaying incorrect data. The AI is flagging a potential risk and proposing a general solution to manage those risks.
8 / 17
Sarah: 'The AI flagged this as a 'high severity' issue. It suggested adding a mutex lock around the data access. I'm not sure we should be introducing locking primitives into this microservice – it feels like overkill. What does 'mutex lock' actually *do* in this context, and why is the AI flagging it so seriously?',
Considering Sarah's question and the AI's recommendation, which of the following best describes the purpose of a mutex lock?
A mutex lock is a fundamental concurrency control mechanism. It prevents multiple threads from simultaneously accessing shared resources, which can lead to data corruption or unpredictable behavior when different parts of the application try to modify the same data concurrently. The AI flagged it 'high severity' because the absence of this protection could have serious consequences – Sarah's skepticism is warranted; introducing a mutex lock might be an overreaction without fully understanding the potential race conditions.
9 / 17
PR Description: 'AI Review suggests adding a try-catch block around the database query. This addresses potential SQL injection vulnerabilities. Please review and approve.'
During a code review meeting, you're discussing this PR with your team lead, Mark. He asks, 'Why did the AI specifically recommend a try-catch block here? It seems like a bit of an overreach.'
This question tests understanding of common defensive programming practices in the context of AI-assisted code review. While SQL injection *is* a serious concern, recommending a `try-catch` block isn't solely about preventing it; it's a broader technique for robust error handling. A `try-catch` block handles exceptions that might occur during database operations (e.g., connection errors, invalid query syntax) and prevents the application from crashing or displaying incorrect data. The AI is flagging a potential risk and proposing a general solution to manage those risks.
10 / 17
Sarah: 'The AI flagged this as a 'high severity' issue. It suggested adding a mutex lock around the data access. I'm not sure we should be introducing locking primitives into this microservice – it feels like overkill. What does 'mutex lock' actually *do* in this context, and why is the AI flagging it so seriously?',
Considering Sarah's question and the AI's recommendation, which of the following best describes the purpose of a mutex lock?
A mutex lock is a fundamental concurrency control mechanism. It prevents multiple threads from simultaneously accessing shared resources, which can lead to data corruption or unpredictable behavior when different parts of the application try to modify the same data concurrently. The AI flagged it 'high severity' because the absence of this protection could have serious consequences – Sarah's skepticism is warranted; introducing a mutex lock might be an overreaction without fully understanding the potential race conditions.
11 / 17
PR Description: 'AI Review suggests adding a try-catch block around the database query. This addresses potential SQL injection vulnerabilities. Please review and approve.'
During a code review meeting, you're discussing this PR with your team lead, Mark. He asks, 'Why did the AI specifically recommend a try-catch block here? It seems like a bit of an overreach.'
This question tests understanding of common defensive programming practices in the context of AI-assisted code review. While SQL injection *is* a serious concern, recommending a `try-catch` block isn't solely about preventing it; it's a broader technique for robust error handling. A `try-catch` block handles exceptions that might occur during database operations (e.g., connection errors, invalid query syntax) and prevents the application from crashing or displaying incorrect data. The AI is flagging a potential risk and proposing a general solution to manage those risks.
12 / 17
Sarah: 'The AI flagged this as a 'high severity' issue. It suggested adding a mutex lock around the data access. I'm not sure we should be introducing locking primitives into this microservice – it feels like overkill. What does 'mutex lock' actually *do* in this context, and why is the AI flagging it so seriously?',
Considering Sarah's question and the AI's recommendation, which of the following best describes the purpose of a mutex lock?
A mutex lock is a fundamental concurrency control mechanism. It prevents multiple threads from simultaneously accessing shared resources, which can lead to data corruption or unpredictable behavior when different parts of the application try to modify the same data concurrently. The AI flagged it 'high severity' because the absence of this protection could have serious consequences – Sarah's skepticism is warranted; introducing a mutex lock might be an overreaction without fully understanding the potential race conditions.
13 / 17
PR Description: 'AI Review suggests adding a try-catch block around the database query. This addresses potential SQL injection vulnerabilities. Please review and approve.'
During a code review meeting, you're discussing this PR with your team lead, Mark. He asks, 'Why did the AI specifically recommend a try-catch block here? It seems like a bit of an overreach.'
This question tests understanding of common defensive programming practices in the context of AI-assisted code review. While SQL injection *is* a serious concern, recommending a `try-catch` block isn't solely about preventing it; it's a broader technique for robust error handling. A `try-catch` block handles exceptions that might occur during database operations (e.g., connection errors, invalid query syntax) and prevents the application from crashing or displaying incorrect data. The AI is flagging a potential risk and proposing a general solution to manage those risks.
14 / 17
Mark asks in a Slack channel: 'The AI flagged this as a potential security vulnerability – it suggested implementing input validation. It's returning a 'high confidence' score. What does 'high confidence' typically indicate in the context of an AI code review tool?', Hint: Consider how these tools are trained
'High confidence' in an AI code review tool reflects the level of certainty the model has based on its training. It doesn't guarantee absolute correctness; instead, it suggests the tool strongly believes a potential issue exists and warrants closer scrutiny. Importantly, human judgment remains crucial – even high-confidence flags require validation.
15 / 17
During a standup meeting, David says: 'Copilot suggested refactoring this function to use a more efficient data structure. I'm not sure if it's actually faster – could we get an estimated performance improvement?', What does David want to know specifically about the AI suggestion?
David is asking for a quantifiable metric – an estimated performance improvement. While helpful, 'functional changes' represent the actual impact on what the code *does*. The other options are irrelevant to understanding the value (or lack thereof) of Copilot's suggestion regarding efficiency.
16 / 17
During a code review session, Emily states: 'The AI identified this as a 'potential deadlock'. It recommended adding synchronization primitives. I'm concerned about the added complexity – is this really necessary?', What does 'potential deadlock' refer to in this context?
'Potential deadlock' is a specific concurrency issue. It describes a scenario where multiple threads are blocked indefinitely, waiting for each other to release resources. This results in a standstill – the AI is highlighting this complex interaction that requires careful handling.
17 / 17
During a code review, Liam says: 'The AI flagged this as a 'critical' vulnerability – it suggested using parameterized queries. I'm not sure we should be doing that; it seems overly cautious for simple reads.' What does 'overly cautious' mean in this context?
'Overly cautious' here refers to taking more precautions than necessary. The AI is flagging a potential vulnerability (SQL injection), and the suggestion of parameterized queries represents a best practice for mitigating that risk – it's not simply about being cautious; it's about actively addressing a known threat.
What will I practice in "AI-Assisted Code Review — Vocabulary"?
This is an AI Code Generation Tools exercise set. It walks through 17 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 17 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.