Practice vocabulary for responsible AI development: responsible AI principles, fairness-aware ML, demographic parity, model performance on minority classes, and testing for bias.
0 / 18 completed
1 / 18
Your organization publishes a set of ___ AI principles covering fairness, transparency, and accountability.
Responsible AI principles are an organization's stated commitments to building and deploying AI ethically — typically covering fairness, reliability, safety, privacy, inclusivity, transparency, and accountability.
2 / 18
The ML team adopts ___-aware ML to ensure the model does not disadvantage any group.
Fairness-aware ML integrates fairness constraints and metrics into the model development process — choosing algorithms, loss functions, and evaluation criteria that reduce discriminatory outcomes.
3 / 18
An audit reveals the model violates ___ parity: approval rates differ significantly by protected group.
Demographic parity (also called statistical parity) requires that the proportion of positive predictions is equal across demographic groups. Violating it means the model favours or disadvantages certain groups.
4 / 18
The evaluation report notes: 'The model performs worse on ___ classes.' What does this mean?
When a model performs worse on minority classes, it means that underrepresented groups in the training data receive less accurate predictions — a common fairness problem caused by imbalanced datasets.
5 / 18
Before launch the team runs a suite of tests ___ for bias to verify fairness across subgroups.
Testing for bias involves running targeted evaluations that compare model performance across protected attributes (gender, ethnicity, age, etc.) to identify and quantify unfair outcomes before deployment.
6 / 18
PR Description
Subject: Refactor User Profile API - Added Deprecation Warnings
Body:
Hi team,
This PR introduces deprecation warnings for the legacy user profile endpoint (/v1/users/{user_id}). We're transitioning to a new, more efficient API and want to give users time to migrate. I've included logging around these warnings to help us monitor usage.
Please review and let me know if you have any concerns about the impact on existing integrations.
Thanks,
John
This question assesses understanding of communicating responsible AI changes within a development workflow. The correct answer emphasizes documentation and acknowledging potential disruption – a crucial aspect of mitigating risks associated with transitioning APIs. Options A and B focus on technical aspects that are important but miss the core concern about user impact and dependency management. Option D is overly aggressive and ignores best practices for phased rollouts.
7 / 18
During a code review discussion about the user profile API changes, Sarah asks: 'John, are we considering potential downstream effects of these deprecation warnings? Specifically, what measures have we taken to ensure that older integrations relying on this endpoint don't experience unexpected errors or data inconsistencies when they eventually receive the warning messages?'
This question assesses understanding of responsible AI beyond just adding logging. While logging is a step, it doesn't address the potential for integration failures or data inconsistencies when older systems receive deprecation warnings. Option 2 correctly highlights proactive testing and comprehensive error handling – crucial components of mitigating risk in a phased API transition. Options A, C, and D all represent insufficient consideration of downstream impacts and user experience during a change like this; they demonstrate a lack of awareness regarding integration dependencies and potential disruption.
8 / 18
PR Description
Subject: Refactor User Profile API - Added Deprecation Warnings
Body:
Hi team,
This PR introduces deprecation warnings for the legacy user profile endpoint (/v1/users/{user_id}). We're transitioning to a new, more efficient API and want to give users time to migrate. I've included logging around these warnings to help us monitor usage.
Please review and let me know if you have any concerns about the impact on existing integrations.
Thanks,
John
This question assesses understanding of communicating responsible AI changes within a development workflow. The correct answer emphasizes documentation and acknowledging potential disruption – a crucial aspect of mitigating risks associated with transitioning APIs. Options A and B focus on technical aspects that are important but miss the core concern about user impact and dependency management. Option D is overly aggressive and ignores best practices for phased rollouts.
9 / 18
During a code review discussion about the user profile API changes, Sarah asks: 'John, are we considering potential downstream effects of these deprecation warnings? Specifically, what measures have we taken to ensure that older integrations relying on this endpoint don't experience unexpected errors or data inconsistencies when they eventually receive the warning messages?'
This question assesses understanding of responsible AI beyond just adding logging. While logging is a step, it doesn't address the potential for integration failures or data inconsistencies when older systems receive deprecation warnings. Option 2 correctly highlights proactive testing and comprehensive error handling – crucial components of mitigating risk in a phased API transition. Options A, C, and D all represent insufficient consideration of downstream impacts and user experience during a change like this; they demonstrate a lack of awareness regarding integration dependencies and potential disruption.
10 / 18
PR Description
Subject: Refactor User Profile API - Added Deprecation Warnings
Body:
Hi team,
This PR introduces deprecation warnings for the legacy user profile endpoint (/v1/users/{user_id}). We're transitioning to a new, more efficient API and want to give users time to migrate. I've included logging around these warnings to help us monitor usage.
Please review and let me know if you have any concerns about the impact on existing integrations.
Thanks,
John
This question assesses understanding of communicating responsible AI changes within a development workflow. The correct answer emphasizes documentation and acknowledging potential disruption – a crucial aspect of mitigating risks associated with transitioning APIs. Options A and B focus on technical aspects that are important but miss the core concern about user impact and dependency management. Option D is overly aggressive and ignores best practices for phased rollouts.
11 / 18
During a code review discussion about the user profile API changes, Sarah asks: 'John, are we considering potential downstream effects of these deprecation warnings? Specifically, what measures have we taken to ensure that older integrations relying on this endpoint don't experience unexpected errors or data inconsistencies when they eventually receive the warning messages?'
This question assesses understanding of responsible AI beyond just adding logging. While logging is a step, it doesn't address the potential for integration failures or data inconsistencies when older systems receive deprecation warnings. Option 2 correctly highlights proactive testing and comprehensive error handling – crucial components of mitigating risk in a phased API transition. Options A, C, and D all represent insufficient consideration of downstream impacts and user experience during a change like this; they demonstrate a lack of awareness regarding integration dependencies and potential disruption.
12 / 18
PR Description
Subject: Refactor User Profile API - Added Deprecation Warnings
Body:
Hi team,
This PR introduces deprecation warnings for the legacy user profile endpoint (/v1/users/{user_id}). We're transitioning to a new, more efficient API and want to give users time to migrate. I've included logging around these warnings to help us monitor usage.
Please review and let me know if you have any concerns about the impact on existing integrations.
Thanks,
John
This question assesses understanding of communicating responsible AI changes within a development workflow. The correct answer emphasizes documentation and acknowledging potential disruption – a crucial aspect of mitigating risks associated with transitioning APIs. Options A and B focus on technical aspects that are important but miss the core concern about user impact and dependency management. Option D is overly aggressive and ignores best practices for phased rollouts.
13 / 18
During a code review discussion about the user profile API changes, Sarah asks: 'John, are we considering potential downstream effects of these deprecation warnings? Specifically, what measures have we taken to ensure that older integrations relying on this endpoint don't experience unexpected errors or data inconsistencies when they eventually receive the warning messages?'
This question assesses understanding of responsible AI beyond just adding logging. While logging is a step, it doesn't address the potential for integration failures or data inconsistencies when older systems receive deprecation warnings. Option 2 correctly highlights proactive testing and comprehensive error handling – crucial components of mitigating risk in a phased API transition. Options A, C, and D all represent insufficient consideration of downstream impacts and user experience during a change like this; they demonstrate a lack of awareness regarding integration dependencies and potential disruption.
14 / 18
Mark from the data science team sends this message: 'Just ran a quick fairness check on the loan application model – saw a significant disparity in approval rates for applicants with addresses in historically redlined neighborhoods. Need to investigate further.' What does Mark likely mean when he mentions 'fairness check'?
Mark uses 'fairness check' to indicate he's examining whether the model produces different outcomes (like approval rates) for groups based on sensitive attributes (in this case, location). This is a core concept in responsible AI – ensuring equitable results regardless of group membership. The other options relate to legal compliance or risk scoring, but don't address the fundamental issue of bias.
15 / 18
During a code review, David comments on this snippet:
```python
def predict_fraud(user_data):
# Uses features like age and income to score risk.
return model.predict(user_data)
```
What is David most likely concerned about regarding the use of 'age' and 'income' as features?
David's concern centers on 'fairness' – age and income are frequently correlated with protected characteristics (like race or gender). If the model relies heavily on these features without addressing potential bias, it could perpetuate discriminatory outcomes. It is a critical consideration when building AI systems.
16 / 18
PR Description
Subject: Implement Differential Privacy for User Activity Data
Body:
This PR introduces a differential privacy mechanism to our user activity tracking system. We're using adding noise to the aggregated data to protect individual users' privacy while still allowing us to generate useful insights. This helps mitigate risks of re-identification and ensures compliance with GDPR.
Which aspect of responsible AI does this PR primarily address?
While data security is a component, the core purpose here is to enhance 'algorithmic transparency'. Differential privacy techniques are specifically designed to make it harder to infer information about individuals from aggregated datasets – directly addressing concerns about how models derive insights and potentially causing harm. GDPR compliance is a consequence of this approach.
17 / 18
During the daily stand-up meeting, Priya says: 'We're working on adding explainability features to our recommendation engine. We're focusing on showing users *why* a particular product was recommended – highlighting key factors like purchase history and similar user behavior.' What is Priya referring to when she mentions 'explainability' in the context of AI?
'Explainability' in responsible AI means making the reasoning of a model understandable to humans. Priya is focusing on providing transparency – showing *why* a recommendation was made, rather than simply presenting the outcome. This builds trust and allows users (and developers) to identify potential biases or errors.
18 / 18
The team is deploying a new fraud detection model. After initial rollout, they observe that the model disproportionately flags transactions from users in a specific geographic region as potentially fraudulent. What term best describes this issue?
'Data drift' refers to changes in the statistical properties of the input data over time – in this case, a shift in transaction patterns within that specific region. This can lead to the model learning spurious correlations and generating biased predictions. 'Algorithmic bias' is the broader concept encompassing this issue.
What will I practice in "Responsible AI Development Vocabulary"?
This is an AI Ethics exercise set. It walks through 18 scenario-based multiple-choice questions built around real usage of AI Ethics 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 18 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 Ethics 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 Ethics exercises?
See the AI Ethics 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 Ethics vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.