TheAI Effectis clearly defined in theISTQB Certified Tester AI Testing Syllabus v1.0under Section1.1 - Definition of AI and AI Effect. The document explains that society's understanding of what qualifies as
"AI" changes over time. Technologies once considered AI-such as expert systems from the 1970s and 1980s or early chess-playing systems-are no longer viewed as AI today. This phenomenon is explicitly labeled the
"AI Effect,"described as"the changing perception of what constitutes AI."The syllabus states that as AI capabilities become routine or widely implemented, they often stop being perceived as true artificial intelligence .
Options B, C, and D do not capture this definition. While AI learning from data (B) is a property of ML, it does not describe the shifting perception of AI. Option C describes a technological achievement, not a perceptual shift. Option D references a historical AI milestone (Deep Blue defeating Kasparov) that the syllabus specifically uses as an example of technology that is no longer considered AI due to the AI Effect.
Therefore, onlyOption Aaccurately reflects the AI Effect as defined by the ISTQB 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.

The ISTQB CT-AI syllabus defines these two concepts clearly inSection 2.1 - Flexibility and Adaptability.
Flexibility is described as the ability of a system to operate in situationsnot explicitly covered in its original requirements, while adaptability refers to how easily the system can bemodifiedto handle new environments or conditions. The syllabus stresses that both flexibility and adaptability are crucial, particularly inself- learning AI systemsthat may need to respond to changes in their environment and adjust their behavior accordingly. It states that systems must be capable of determiningwhenandhowto adjust behavior in evolving situations, especially when the operational environment is not fully known at deployment time . This directly aligns with OptionA.
Option B reverses definitions-the syllabus states flexibility (not adaptability) relates to unspecified situations. Option C is incorrect: self-learning systems requirebothflexibility and adaptability; they are not categorized as one or the other. Option D incorrectly defines flexibility; the syllabus defines adaptability-not flexibility-as ease of modification.
Thus,Option Acorrectly reflects the syllabus.

The syllabus explains that EDA can be used to analyze data to identify outliers and unusual patterns, which can indicate adversarial attacks like data poisoning:
"Testing to detect data poisoning is possible using EDA, as poisoned data may show up as outliers." (Reference: ISTQB CT-AI Syllabus v1.0, Section 9.1.2, page 67 of 99)

The syllabus discusses using AI-based tools to reduce GUI test brittleness:
"AI can be used to reduce the brittleness of this approach, by employing AI-based tools to identify the correct objects using various criteria (e.g., XPath, label, id, class, X/Y coordinates), and to choose the historically most stable identification criteria." (Reference: ISTQB CT-AI Syllabus v1.0, Section 11.6.1)