Which THREE types of 'Bias' need to be managed in an AI project?
Measurement bias arises when data collection instruments or sampling methods systematically distort values, so the training set misrepresents the population the model must serve. Recognising it as a distinct bias category satisfies the stem's requirement to identify three manageable bias types, since it can be mitigated through validated collection tools and representative sampling.
Why this answer
Measurement bias (A) must be managed because it arises during data collection when the instruments, sensors, or labeling procedures systematically distort the values recorded, so the training data does not faithfully represent the real-world phenomenon. Sampling bias (D) must be managed because it occurs during data selection when the dataset is drawn from a non-representative subset of the population, causing the model to learn patterns that do not generalize to the intended deployment context. Algorithmic bias (E) must be managed because it emerges from the model's logic, objective function, or optimization process, which can amplify or encode unfair correlations even when the input data is otherwise sound.
The remaining options do not belong: the bias towards free coffee (B) is a humorous personal preference with no bearing on AI data or model behavior, and the bias of the local weather (C) is an environmental condition rather than a systematic distortion in an AI pipeline.
Exam trap
The trap here is that candidates may confuse general 'bias' in everyday language with the specific technical categories of bias tested in AI risk management exams.