The ISTQB CT-AI syllabus defines these two concepts clearly in Section 2.1 – Flexibility and Adaptability . Flexibility is described as the ability of a system to operate in situations not explicitly covered in its original requirements , while adaptability refers to how easily the system can be modified to handle new environments or conditions. The syllabus stresses that both flexibility and adaptability are crucial, particularly in self-learning AI systems that may need to respond to changes in their environment and adjust their behavior accordingly. It states that systems must be capable of determining when and how to adjust behavior in evolving situations, especially when the operational environment is not fully known at deployment time . This directly aligns with Option A .

Option B reverses definitions—the syllabus states flexibility (not adaptability) relates to unspecified situations. Option C is incorrect: self-learning systems require both flexibility 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 A correctly reflects the syllabus.

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.

The ISTQB CT-AI syllabus introduces AI-specific quality characteristics , including evolution , functional safety , compatibility , and bias-related data quality . Section 5.1 – AI-Specific Test Objectives explains that evolution refers to an AI system’s capability to continue improving or at least maintain performance as it undergoes additional training. GPT_Legal is explicitly described as a self-learning system expected to:

continuously reduce false positives,

achieve weekly accuracy improvements of 10%,

reach and maintain 90% accuracy,

adapt to new environments (patent law firm → corporate legal department).

This aligns perfectly with the syllabus definition of evidence of evolution : ensuring the model does not degrade as additional training data is introduced. Option B therefore directly supports the described acceptance criteria for this evolving, self-learning application.

Option A (functional safety) is irrelevant because patent searching and drafting do not constitute safety-critical domains. Option C (compatibility) is necessary but not the primary AI-specific objective. Option D addresses bias, which is important but not central to the described performance and continuous-learning expectations.

Thus, Option B is the most appropriate AI-specific test objective.

In the syllabus, the evolution characteristic for AI-based systems means the ability of the system to evolve and adapt its behavior in response to changes in the environment or in its own performance:

"Evolution is the system’s ability to change itself to adapt to new situations, different hardware, or a changing operational environment."

(Reference: ISTQB CT-AI Syllabus v1.0, Section 2.3)

The ISTQB CT-AI syllabus lists several characteristics that make it difficult to ensure safety in AI-based systems. Section 2.8 – Safety and AI explicitly names the characteristics that complicate safety assurance: complexity , non-determinism , probabilistic behavior , self-learning , lack of transparency , and lack of robustness . Among these, complexity is a core challenge because modern AI systems—particularly those using deep learning—have highly non-linear behavior, large numbers of parameters, and intricate interactions that are hard to predict.

Option B (Complexity) directly aligns with the syllabus and is therefore correct.

Option A (Determinism) is the opposite of AI behavior; AI is often non-deterministic , and determinism does not make systems unsafe. Option C (Interpretability) does impact trust and explainability, but the syllabus positions it as a transparency challenge, not the primary difficulty in ensuring safety. Option D (Robustness) is a desired quality, not a reason safety is hard; a lack of robustness would be a challenge, not robustness itself.

Thus, complexity best reflects the syllabus’ explicit safety-related difficulty.

The syllabus describes automation bias as:

"A type of bias caused by a person favoring the recommendations of an automated decision-making system over other sources."

This is also known as complacency bias, where testers accept automated system outputs without questioning them.

(Reference: ISTQB CT-AI Syllabus v1.0, Glossary, Page 89 of 99)