CT-AI Exam Dumps : ISTQB Certified Tester AI Testing Exam

 AI-Based Autonomous Functions:An AI-based autonomous system is one that can respond to its environment without human intervention. The other options either involve human decisions or do not use AI at all.

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

The ISTQB CT-AI syllabus explains inSection 4.5 – Testing AI-Specific Risksthat adversarial testing is a structured test activity in which testers applyadversarial attacks—crafted or perturbed inputs—to intentionally expose weaknesses in the ML model. The purpose is to identify vulnerabilities that could be exploited throughdata poisoning,evasion attacks, orinput manipulation. OptionCcorrectly reflects this syllabus definition: adversarial testing is aboutusing attacks to locate weaknesses so they can be removed or mitigated.

Option A is incorrect because regression testing does not verify data sourcing policies; it verifies unchanged functionality after modifications. Option B is incorrect because adversarial examples are oftenaddedto training datasets to improverobustness(a practice called adversarial training), not excluded. Option D is incorrect because AIB testing is not described as superior to exploratory data analysis in outlier detection; both have different purposes, and EDA remains essential for data quality assessment.

Thus,Option Cis consistent with syllabus-defined adversarial testing.

Section5.3 – AI Support for Defect Predictionof the ISTQB CT-AI syllabus explains that AI-based defect prediction models rely onhistorical patterns, including past defects, code behavior, and similar system configurations. ML models trained on prior defect data can identifycomponents likely to contain defectswhen new changes resemble previous defect-inducing patterns. This directly supports OptionA, which states that defect prediction is most effective when based on previous similar constellations.

Option B is incorrect: ML can predictwhich componentsare likely to fail, not only whether defects exist. Option C is incomplete; code metrics help, but defect prediction relies onmanycontextual features (historical defects, code churn, commit frequency, etc.). Option D is wrong because defect prediction isnotbased on formal principles and typically requiresmany features, not just a few.

Thus,Option Ais the correct and syllabus-consistent answer.