ISTQB CT-AI Exam With Confidence Using Practice Dumps

 Challenges for Acquiring Test Data in ML Systems:Compliance needs, the changing nature of data over time, and sourcing data from public sources are significant challenges. Data being generated quickly is generally not a challenge; it can actually be beneficial as it provides more data for training and testing.

 Reference:ISTQB_CT-AI_Syllabus_v1.0, Sections on Data Preparation and Data Quality Issues​​​​.

Setting model and algorithm hyperparameters is an essential step in the machine learning workflow, primarily occurring during the tuning phase.

Evaluating the model (A): This stage involves assessing the model's performance using metrics and does not typically include the setting of hyperparameters.

Deploying the model (B): Deployment is the stage where the model is put into production and used in real-world applications. Hyperparameters should already be set before this stage.

Tuning the model (C): This is the correct stage where hyperparameters are set. Tuning involves adjusting the hyperparameters to optimize the model's performance.

Data testing (D): Data testing involves ensuring the quality and integrity of the data used for training and testing the model. It does not include setting hyperparameters.

Hence, the most appropriate stage of the ML workflow to set model and algorithm hyperparameters isC. Tuning the model.

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.