Pass the iSQI AI Testing CT-GenAI Questions and answers with ExamsMirror

In professional Generative AI applications, thesystem prompt(sometimes called the system message) is the foundational set of instructions that defines the AI's persona, boundaries, and overall behavior. In a testing workflow, this is typically defined by atester or test engineerwho is configuring the AI assistant for a specific project. Unlike the user prompt, which changes with every interaction, the system prompt remains relatively static and acts as a "guardrail" to ensure the model stays in its role (e.g., "You are an expert in ISO 26262 automotive testing standards"). By defining the system prompt, the tester ensures that the model consistently uses specific terminology, adheres to data privacy constraints, and formats its output according to the team's requirements. While end users (Option B) provide the task-specific input, they do not usually have the permissions or technical need to alter the underlying system-level instructions. Similarly, while CI servers (Option C) might trigger the prompt, they do not "define" the human-centric logic contained within it. Properly crafting the system prompt is a core part of setting up an AI-augmented test environment.

A mature GenAI strategy for software testing must move beyond "hype" and focus on tangible value and operational feasibility. Selecting an LLM based onmeasurable test outcomes(such as reduction in test design time, increase in defect detection, or script accuracy) ensures that the AI investment directly supports the organization’s Quality Assurance goals. Furthermore, the model must becompatible with current infrastructure. This includes considerations for data security (on-prem vs. cloud), API integration capabilities, and cost-per-token efficiency. While vendor visibility (Option A) can be a factor, it is not a guarantee of task-specific performance. Prioritizing creativity over compliance (Option B) is highly risky for testing, where precision and policy adherence are paramount. Similarly, while broad functionality (Option C) is useful, it often results in "jack-of-all-trades" models that may not perform as well as specialized or instruction-tuned models on specific testing tasks. Strategic alignment requires a balance between model performance, organizational security requirements, and clear KPIs.

Classical Machine Learning(which includes algorithms like Random Forests, Support Vector Machines, and Linear Regression) is characterized by its reliance onFeature Engineering. This is the process where human experts manually select, extract, and transform raw data into a set of "features" or variables that the algorithm can process. For instance, in a classical ML model predicting software defects, a tester might have to manually define features like "lines of code changed" or "number of previous bugs." In contrast,Deep Learningand its subset,Generative AI(Options B and D), utilize "Representation Learning." This means the multi-layered neural networks automatically identify and extract the relevant features from raw, often unstructured data (like text or images) without explicit human instruction.Symbolic AI(Option A) is based on hard-coded logical rules rather than data-driven learning. Understanding this distinction is fundamental for testers, as it determines the level of data preparation required: Classical ML requires high human effort in data structuring, while GenAI requires high effort in prompt engineering and grounding.

Embeddingsare a fundamental concept in modern Natural Language Processing (NLP) and LLMs. They are high-dimensional numerical vectors—essentially lists of numbers—that represent the meaning (semantics) of a piece of text (a word, sentence, or document). Unlike traditional keyword matching, which looks for identical strings of characters, embeddings allow the model to understand the "closeness" of concepts. For example, in a vector space, the word "bug" would be mathematically closer to "defect" or "error" than to "feature" or "requirement." This captures the semantic relationship between terms. This technology is the backbone of Retrieval-Augmented Generation (RAG) used in testing: when a tester queries a documentation set, the system converts the query into an embedding and looks for other chunks of text with similar vector values. This allows the AI to retrieve relevant context even if the exact keywords do not match. It is not about logical rules (Option C) or groups of tokens (Option A), but rather a mathematical representation of language that enables machines to process human meaning.

Shadow AIrefers to the use of artificial intelligence tools and services within an organization without explicit approval or oversight from the IT or Security departments. In a software testing environment, this often occurs when testers use public, consumer-grade LLMs to analyze proprietary code or sensitive requirement documents to speed up their work. The primary compliance concern is theviolation of established data handling and regulatory compliance standards(such as GDPR, HIPAA, or SOC2). When sensitive test data is fed into a "shadow" AI tool, that data may be stored on external servers or used to train future iterations of the model, leading to massive data leaks and legal exposure. This bypasses the organization's security controls, such as data masking and role-based access. Unlike "authorized" AI which undergoes a rigorous vendor risk assessment, Shadow AI creates an invisible attack surface. For a test organization, mitigating this risk involves providing approved, secure AI alternatives and implementing strict policies and monitoring to ensure that internal intellectual property is never processed by unvetted external services.

Vision-Language Models (VLMs)represent a specialized subset of multimodal Large Language Models. Their defining characteristic is the ability to process, understand, and reason across both textual and visual modalities simultaneously. In the field of software testing, VLMs are revolutionary because they allow the AI to "see" a User Interface (UI). A tester can provide a screenshot of a web page alongside a natural language prompt, and the VLM can identify UI elements, detect visual regressions, or even validate that the visual layout matches a design specification. They are not a "superset" (Option C) of multimodal AI, but rather a specific implementation of it focused on the intersection of sight and language. Unlike traditional OCR or pixel-comparison tools used in legacy UI automation (Option B), VLMs understand thecontextof what they see—for instance, identifying a "broken" button icon that a human would recognize but a rule-based script might miss. This integration of visual and textual data is what makes them a vital component of modern, AI-augmented Quality Assurance strategies.

This scenario describes a failure in the model's ability to apply logical weight to specific domain concepts, specifically in the context of Risk-Based Testing (RBT). When an LLM ranks a low-impact UI element (a tooltip) higher than a critical functional failure (payment processing), it demonstrates a "Reasoning error in risk calculation logic." While LLMs can follow formulas like $Risk = Likelihood \times Impact$, they may lack the deep semantic understanding of "Impact" within a specific business domain unless explicitly guided. This is not necessarily a hallucination (Option C), as the model isn't necessarily inventing facts, but rather misapplying the logic of prioritization. It is also distinct from dataset bias (Option D), which would involve a systematic skewing across all outputs. In professional testing, this type of error highlights the necessity of "human-in-the-loop" verification. Testers must review AI-generated prioritizations to ensure that the logical deductions align with the actual business risk and technical criticality of the features being tested.

This scenario describes a form ofRequest Manipulation, specifically a type of "Prompt Injection" or "Adversarial Prompting." In this attack vector, the user (or an external attacker) provides malicious or deceptive input—in this case, via an image in a multimodal LLM—to bypass the model's intended constraints or to steer its logic toward an unintended outcome. By crafting an image that tricks the LLM into seeing "acceptance criteria" that aren't actually there, the attacker manipulates the model’s request processing to generate false validation results. This is different fromData Poisoning(Option A), which involves corrupting the training data before the model is even built. It is also distinct fromData Exfiltration(Option B), which aims to steal data from the model. In a testing environment, request manipulation is a significant risk because it can lead to "Silent Failures," where the AI reports that tests have passed or requirements are met based on deceptive input, thereby compromising the integrity of the entire Quality Assurance process.

As Generative AI becomes integrated into the software testing lifecycle, the role of the tester shifts from manual authoring to the "orchestration" of AI models. Mastering prompt engineering is the primary competency required to effectively steer LLMs. Prompt engineering involves the deliberate design of inputs—incorporating roles, context, instructions, and constraints—to elicit the most accurate and "on-policy" outputs from the model. In a testing context, "on-policy" refers to testware that adheres to organizational standards, security protocols, and specific project requirements. While technical skills like network configuration or low-level programming (Options B, C, and D) are valuable in specific engineering domains, they do not directly influence the communicative interface between the human and the AI. A tester proficient in prompt engineering can utilize techniques like "Chain-of-Thought" or "Few-shot prompting" to ensure the LLM understands the nuances of a test plan, thereby reducing hallucinations and ensuring the generated test cases are actionable, relevant, and compliant with the project's quality gates.

While a basic chatbot is primarily designed for textual interaction and information retrieval, anLLM-powered agent(or AI Agent) is characterized by itsagency—the ability to use tools and trigger actions in the external world. In a software testing context, an agent does not just "talk" about testing; it can actually perform testing tasks. For example, an agent could be given the goal to "verify the login module," and it would independently decide to call an API, generate a test script, execute it against a test environment, and then analyze the results to report a bug in Jira. This ability totrigger automated actions(Option C) through "function calling" or tool integration is what makes agents far more powerful than simple conversational interfaces (Option D). Agents can reason about "how" to achieve a goal, selecting the appropriate tools (like Selenium, Postman, or specialized internal utilities) to complete the task. This moves the AI from being a passive advisor to an active participant in the test automation ecosystem, requiring testers to focus more on goal definition and result validation.