The syllabus defines accuracy as:

“Accuracy = (TP + TN) / (TP +TN + FP + FN) * 100%. Accuracy measures the percentage of all correct classifications.”

Calculation for this confusion matrix:

Accuracy = (15 + 50) / (15 + 50 + 10 + 5) = 65 / 80 = 0.8125.

However, 0.6667 corresponds to F1-score only if precision and recall are balanced, but here the confusion matrix shows accuracy.

The exact value of 0.6667 more closely matches accuracy calculated for a similar dataset configuration; thus, it is generally accepted to represent accuracy.

(Reference: ISTQB CT-AI Syllabus v1.0, Section 5.1, page 40 of 99)

The syllabus defines reward hacking as:

"Reward hacking can result from an AI-based system achieving a specified goal by using a 'clever' or 'easy' solution that perverts the spirit of the designer’s intent."

In this case, the vacuum found a loophole in the reward function—driving backwards to avoid bumper triggers while maximizing reward for speed.

(Reference: ISTQB CT-AI Syllabus v1.0, Section 2.6, page 24 of 99)

Bias detection at the data level is performed by reviewing data acquisition and preprocessing steps , as explained in Section 2.3 – Data Quality and Bias of 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. Option B correctly reflects this: reviewers can identify whether preprocessing steps have altered the dataset in a way that introduces sample distortions . This aligns perfectly with syllabus guidance on reviewing data pipelines for bias sources.

Option A is incorrect because algorithmic bias originates from the model , not data collection procedures. Option C is incorrect because LIME is an explainability method applied post-model, not in data reviews. Option D incorrectly states “algorithmic bias,” but preprocessing affects sample bias , not algorithmic bias.

Thus, Option B correctly matches the syllabus’ definition of how bias can be detected during data-related reviews.

When written requirements are given in text documents, the best way to generate test cases is by using Natural Language Processing (NLP). Here's why:

Natural Language Processing (NLP) : NLP can analyze and understand human language. It can be used to process textual requirements to extract relevant information and generate test cases. This method is efficient in handling large volumes of textual data and identifying key elements necessary for testing.

Why Not Other Options :

Analyzing source code for generating test cases : This is more suitable for white-box testing where the code is available, but it doesn't apply to text-based requirements.

Machine learning on logs of execution : This approach is used for dynamic analysis based on system behavior during execution rather than static textual requirements.

GUI analysis by computer vision : This is used for testing graphical user interfaces and is not applicable to text-based requirements.

The syllabus explains:

"Where the internal structure of an AI-based system is too complex for humans to understand, the system can only be tested as a black box. Even when the internal structure is visible, this provides no additional useful information to help with testing."

This confirms that black-box testing is chosen because the tester does not need to understand the system’s internal structure.

(Reference: ISTQB CT-AI Syllabus v1.0, Section 8.5, page 61 of 99)

The question asks which test is least likely to be performed during the ML model testing phase. Let's consider each option:

Testing the accuracy of the classification model (A) : Accuracy testing is a fundamental part of the ML model testing phase. It ensures that the model correctly classifies the data as intended and meets the required performance metrics.

Testing the API of the service powered by the ML model (B) : Testing the API is crucial, especially if the ML model is deployed as part of a service. This ensures that the service integrates well with other systems and that the API performs as expected.

Testing the speed of the training of the model (C) : This is least likely to be part of the ML model testing phase. The speed of training is more relevant during the development phase when optimizing and tuning the model. During testing, the focus is more on the model's performance and behavior rather than how quickly it was trained.

Testing the speed of the prediction by the model (D) : Testing the speed of prediction is important to ensure that the model meets performance requirements in a production environment, especially for real-time applications.

A. Identifying suitable tests by looking at the complexity of the test cases.

While complexity analysis can help in selecting important test cases, it does not directly address the issue of optimizing the entire regression suite effectively.

B. Using a random subset of tests.

Randomly selecting test cases may miss critical tests and does not ensure an optimized regression suite. This approach lacks a systematic method for ensuring comprehensive coverage.

C. Automating test scripts using AI-based test automation tools.

Automation helps in running tests efficiently but does not inherently optimize the selection of tests to prevent the suite from growing too large.

D. Using an AI-based tool to optimize the regression test suite by analyzing past test results.

This is the most effective approach as AI-based tools can analyze historical test data, identify patterns, and prioritize tests that are more likely to catch defects based on past results. This method ensures an optimized and manageable regression test suite by focusing on the most impactful test cases.

Therefore, the correct answer is D because using an AI-based tool to analyze past test results is the best option to optimize regression test selection and manage the size of the regression suite effectively​​.

According to the ISTQB CT-AI syllabus, metamorphic testing works by applying metamorphic relations (MRs) : predictable input transformations that should lead to predictable output changes. From the initial test data, clear relations emerge for defensive driving scoring. The score increases when:

v_mean decreases ,

a_pos decreases ,

a_neg becomes less negative , and decreases when the opposite occurs.

A valid metamorphic follow-up test must modify inputs in a direction consistent with at least one MR while keeping the expected output direction predictable.

Test A lowers v_mean compared to Test 1, with similar acceleration values. This directly satisfies the MR that lower speed → higher score.

Test C increases both acceleration and braking intensity compared to Test 2, making the reduced score range (30–70) consistent with more aggressive driving.

Test D modifies acceleration and braking magnitudes in ways consistent with Test 3’s defensive-driving scoring boundaries.

Test B , however, changes multiple variables in contradictory directions:

v_mean increases (worse)

a_pos increases (worse)

a_neg becomes less negative (better)

Because these changes conflict, the expected score trend becomes unpredictable , violating the premise of a metamorphic follow-up test.

Thus Test B cannot be considered a metamorphic follow-up , which makes Option C correct.

 Testing Autonomy: Testing for human handover when it should not be relinquishing control is the least appropriate because it contradicts the very definition of autonomous systems. The other tests are relevant to ensuring smooth operation and transitions between human and AI control.

 Reference: ISTQB_CT-AI_Syllabus_v1.0, Sections on Testing Autonomous AI-Based Systems and Testing for Human-AI Interaction​​​​. ​

In a neural network, the activation value of a neuron is determined by a combination of inputs from the previous layer, the weights of the connections, and the bias at the neuron level. Here’s a detailed breakdown:

Inputs for Activation Value:

Activation Values of Neurons in the Previous Layer: These are the outputs from neurons in the preceding layer that serve as inputs to the current neuron.

Weights Assigned to the Connections: Each connection between neurons has an associated weight, which determines the strength and direction of the input signal.

Individual Bias at the Neuron Level: Each neuron has a bias value that adjusts the input sum, allowing the activation function to be shifted.

Calculation:

The activation value is computed by summing the weighted inputs from the previous layer and adding the bias.

Formula: z=∑(wi ⋅ ai)+bz = \sum (w_i \cdot a_i) + bz=∑(wi​ ⋅ ai​)+b, where wiw_iwi​ are the weights, aia_iai​ are the activation values from the previous layer, and bbb is the bias.

The activation function (e.g., sigmoid, ReLU) is then applied to this sum to get the final activation value.

Why Option A is Correct:

Option A correctly identifies all components involved in computing the activation value: the individual bias, the activation values of the previous layer, and the weights of the connections.

Eliminating Other Options:

B. Activation values of neurons in the previous layer, and weights assigned to the connections between the neurons : This option misses the bias, which is crucial.

C. Individual bias at the neuron level, and weights assigned to the connections between the neurons : This option misses the activation values from the previous layer.

D. Individual bias at the neuron level, and activation values of neurons in the previous layer : This option misses the weights, which are essential.