Bias in AI models often originates fromincomplete or non-representative training data. In this case, if the training datasetpurposely excludes specific faulty conditions, the machine learning model willfail to learn and detectthese conditions in real-world scenarios.
This results in:
* Sample bias, where the training data is not fully representative of all possible faulty conditions.
* Algorithmic bias, where the model prioritizes certain defect types while ignoring others.
* B. Selecting training data by purposely including all known faulty conditions# This would help reduce bias by improving model generalization.
* C. Selecting testing data from a different dataset than the training dataset# This is a good practice to evaluate model generalization but does not inherently introduce bias.
* D. Selecting testing data from a boat manufacturer's bolt longevity data# While using unrelated data can createpoor model accuracy, it does not directly introduce bias unless systematic patterns in the incorrect dataset lead to unfair decision-making.
* Section 8.3 - Testing for Algorithmic, Sample, and Inappropriate Biasstates thatsample bias can occur if the training dataset is not fully representative of the expected data space, leading to biased predictions.
Why are the other options incorrect?Reference from ISTQB Certified Tester AI Testing Study Guide:

Defect prediction models aim to identify parts of the software that are likely to contain defects by analyzing historical data and code quality metrics. The primary goal is to use this predictive information to allocate testing and maintenance resources effectively. Let's break down why option D is the correct choice:
Understanding Classification Models:
Classification models are a type of supervised learning algorithm used to categorize or classify data into predefined classes or labels. In the context of defect prediction, the classification model would classify parts of the code as either "defective" or "non-defective" based on the input features.
Input Data - Code Quality Metrics:
The input data for these classification models typically includes various code quality metrics such as cyclomatic complexity, lines of code, number of methods, depth of inheritance, coupling between objects, etc. These metrics help the model learn patterns associated with defects.
Historical Data:
Historical versions of the code along with their defect records provide the labeled data needed for training the classification model. By analyzing this historical data, the model can learn which metrics are indicative of defects.
Why Option D is Correct:
Option D specifies using a classification model to predict the presence of defects by using code quality metrics as input data. This accurately describes the process of defect prediction using historical bug data and quality metrics.
Eliminating Other Options:
A . Identifying the relationship between developers and the modules developed by them: This does not directly involve predicting defects based on code quality metrics and historical data.
B . Search of similar code based on natural language processing: While useful for other purposes, this method does not describe defect prediction using classification models and code metrics.
C . Clustering of similar code modules to predict based on similarity: Clustering is an unsupervised learning technique and does not directly align with the supervised learning approach typically used in defect prediction models.
Reference:
ISTQB CT-AI Syllabus, Section 9.5, Metamorphic Testing (MT), describes various testing techniques including classification models for defect prediction.
"Using AI for Defect Prediction" (ISTQB CT-AI Syllabus, Section 11.5.1).

Sample bias occurs when the training data is not representative of the overall population that the model will encounter in practice.
In this case, the over-representation of ethnicity A (70%) compared to B, C, and D (30%) creates a sample bias, as the model may become biased towards better performance on ethnicity A.

The ISTQB CT-AI syllabus explains in Section1.6 - Machine Learning Approachesthatsupervised learning is appropriate when labeled data exists and the goal is to predict an output based on known historical examples. Predicting a customer'spurchase probabilityis aclassificationtask when the output corresponds to discrete categories such as"likely to purchase"vs."not likely to purchase."The syllabus gives similar examples in describing classification as the process of assigning instances to predefined classes based on learned patterns in labeled data. Because the retail company wants to determine whether a customer will make a purchase based on marketing actions, classification is the most appropriate choice .
Option A (regression) predicts continuous numeric values and is less suitable because the task centers on categorical likelihood, not estimating exact monetary values. Option C (unsupervised learning) is used when labels are not available-here, the company has labeled purchase histories. Option D (reinforcement learning) requires an interactive environment with reward-driven behavior, which is not applicable to this scenario.
Thus,supervised learning (classification)is the most suitable approach according to the syllabus.

Bias detection at thedata levelis performed by reviewingdata acquisition and preprocessing steps, as explained in Section2.3 - Data Quality and Biasof the ISTQB CT-AI syllabus. Sample bias arises when data is distorted or when preprocessing introduces unintended shifts-for example, by filtering, normalization, or labeling steps that disproportionately affect subsets of the data. OptionBcorrectly reflects this: reviewers can identify whether preprocessing steps have altered the dataset in a way that introducessample distortions. This aligns perfectly with syllabus guidance on reviewing data pipelines for bias sources.
Option A is incorrect because algorithmic bias originates from themodel, not data collection procedures.
Option C is incorrect because LIME is anexplainabilitymethod applied post-model, not in data reviews.
Option D incorrectly states "algorithmic bias," but preprocessing affectssample bias, not algorithmic bias.
Thus, OptionBcorrectly matches the syllabus' definition of how bias can be detected during data-related reviews.