AAIR ISACA Advanced in AI Risk Questions and Answers

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. Mapping AI project outcomes to enterprise performance metrics ties investment to measurable organizational value. An inventory improves visibility and workforce metrics measure only one dimension, while a narrow focus on quantifiable benefits can miss strategic value. This makes option C, Mapping AI project outcomes to enterprise performance metrics, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. A conversational system exposed to unrestricted text is vulnerable to prompt injection and unsafe output. Runtime input validation and output filtering directly constrain malicious instructions and help prevent disclosure of secrets or harmful actions. This makes option D, Implement runtime input validation and output filtering, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Free-form data can contain inconsistent formats, scales, terminology, and representations that distort model learning. Scaling and standardizing inputs reduces unwanted variance and helps prevent irrelevant formatting differences from becoming sources of bias. This makes option C, Scaling and standardizing inputs, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Risk transfer is used when a third party assumes defined financial or contractual consequences of residual risk that the organization cannot or chooses not to retain. It can reduce organizational liability, but it does not eliminate the organization ' s governance responsibilities. This makes option A, lower organizational liability when internal mitigations fail, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. Civil aviation is safety-critical, so governance must preserve qualified human oversight, intervention, escalation, and override capability. Technical simplification, privacy, and centralization are relevant but do not replace human accountability for consequential decisions. This makes option A, Provisions for human oversight, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Automated risk scenario generation tools operate based on programmed logic, historical data, and pattern recognition. They may excel at generating scenarios based on known risks and documented processes but struggle to account for complex organizational interdependencies that are not fully captured in their data inputs.

Why D is Correct: The ISACA AAIR risk scenario development guidance identifies the failure to account for process interdependencies as the greatest risk from automated scenario generation. AI systems do not operate in isolation—they are embedded in complex organizational ecosystems where failures cascade through interconnected processes, systems, and stakeholders. Automated tools may miss these interdependencies, producing scenarios that are technically accurate in isolation but miss the most consequential cascade effects.

Why A is Wrong: Complexity in likelihood and impact scoring is a risk quantification challenge that affects scenario prioritization but does not result in missing scenarios entirely. Complex scoring can be managed through additional analytical methods.

Why B is Wrong: Emerging adversarial attack vectors are a potential blind spot for any tool or analyst working from historical data, but this is a known limitation of retrospective approaches that can be supplemented with threat intelligence. It does not represent the distinctive risk of automated scenario generation.

Why C is Wrong: Underestimating model change impacts is a scenario calibration issue that represents a less severe risk than missing entire categories of scenarios arising from unmodeled interdependencies.

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. AI risk should be explicitly included in enterprise risk appetite and tolerance so use cases are judged against approved business boundaries. A risk register and data controls are useful, but appetite and tolerance connect treatment decisions directly to business objectives. This makes option D, Include AI in risk appetite and tolerance, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Explainability and input transparency are foundational requirements for responsible AI governance. When these are absent, organizations lose the ability to identify when AI systems produce harmful, biased, or inaccurate results—leaving those harms undetected and unaddressed.

Why C is Correct: According to ISACA AAIR, the inability to explain AI decisions is most dangerous because it creates an environment where discriminatory or inaccurate outputs can persist undetected. This exposes the organization to regulatory penalties (particularly under anti-discrimination, financial services, and privacy laws), reputational damage, and harm to affected individuals. The detection gap—not knowing what the system is doing wrong—is the core governance failure.

Why A is Wrong: External provider dependence is a third-party risk management concern. While relevant, it is a structural risk that can be addressed through contract management, not an immediate consequence of lacking explainability.

Why B is Wrong: Declining adoption rates represent a change management and trust concern. Business unit reluctance to adopt AI is a cultural and operational issue, not the primary risk from unexplainable AI decisions.

Why D is Wrong: Manual review bottlenecks represent operational inefficiency. They may result from lack of confidence in AI outputs but do not represent the primary organizational harm from unexplainability.

Following a model exfiltration attack, multiple AI systems may require restoration. Prioritization must be based on objective criteria that reflect the potential business impact of continued unavailability. Systems supporting critical business functions must be restored before those supporting non-critical functions.

Why A is Correct: According to ISACA AAIR business continuity guidance for AI, the primary criterion for restoration priority is the AI system ' s criticality to business requirements. Systems that support mission-critical functions—patient care, financial transaction processing, safety operations—represent the highest restoration priority because their unavailability causes the greatest operational harm. This risk-based prioritization framework is consistent with standard business continuity management principles applied to the AI context.

Why B is Wrong: Team member expertise affects restoration capacity and speed but should not drive prioritization decisions. Priority is determined by business impact, not by where the team has the most technical capability. Resource allocation follows priority, not the reverse.

Why C is Wrong: Vulnerability testing and patch costs are operational considerations that may influence restoration timelines but should not override business criticality in determining priority. Cost-based prioritization could lead to restoring cheaper but less critical systems first.

Why D is Wrong: Dataset availability affects the feasibility and timeline of model retraining but is a logistical consideration rather than the primary basis for restoration priority. Critical systems should be prioritized even if their restoration is technically more complex.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Rapidly changing generative-AI risk is best communicated through concrete real-world incidents and business impacts that stakeholders can understand. Technical root causes or exhaustive lists can obscure the practical consequences that decision-makers need to evaluate. This makes option B, Provide real-world examples of risk impacts from generative AI incidents and breaches, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. When ethical and legal exposures exceed tolerance and the AI system is non-critical, avoidance is the most proportionate response. Acceptance is inappropriate above tolerance, transfer cannot remove all accountability, and mitigation is suitable only if effective controls can reduce exposure sufficiently. This makes option D, Avoidance, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. A business impact analysis focuses on how disruption affects critical operations and on recovery requirements such as recovery time objectives. Development records, asset classification, and incident procedures are related controls but are not the primary purpose of a BIA. This makes option A, Effects of AI system outages on core operations and associated recovery time targets, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. Mapping identified AI risks to organizational objectives translates technical exposure into business consequences and ensures risk is considered in strategic decisions. Workshops and vulnerability reports help identify issues but do not create the same direct strategy linkage. This makes option A, Map AI risk to organizational objectives, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Business processes are most suitable for AI integration when objectives, decisions, and rules are sufficiently defined for the AI tool to operate against clear requirements. Industry popularity, immediate scaling, and staffing reductions do not establish suitability. This makes option D, the process includes clearly defined rules for AI tools to follow, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Dependence on a single proprietary AI environment can create vendor lock-in, making migration technically difficult, operationally disruptive, and expensive. Transparency and scalability are relevant concerns, but prohibitive switching costs are the central dependency risk. This makes option B, Prohibitive migration costs, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Multi-jurisdictional AI deployment requires jurisdiction-specific compliance strategies because privacy and data protection laws vary significantly across countries. A one-size-fits-all approach frequently fails to meet local requirements, while post-deployment remediation creates legal exposure during the gap period.

Why B is Correct: According to ISACA AAIR guidance, the best approach to multi-jurisdictional compliance is to tailor controls to each relevant statutory framework before deployment and maintain audit trails that demonstrate adherence. This proactive, documented approach reduces legal exposure, satisfies regulatory examination requirements, and enables the organization to demonstrate accountability—a key requirement of frameworks like GDPR.

Why A is Wrong: Post-deployment remediation means the organization is non-compliant during deployment, which creates immediate regulatory exposure. Iterative fixes after harm has occurred are inadequate for protecting individuals or the organization.

Why C is Wrong: Uniform global policies cannot satisfy jurisdictions with conflicting requirements—some laws mandate data residency within borders, making cross-border transfer impossible regardless of encryption strength.

Why D is Wrong: Restricting disclosure of model operations conflicts with transparency requirements embedded in many privacy laws, including GDPR ' s right to explanation. IP protection cannot override regulatory disclosure obligations.

An enterprise AI governance dashboard must provide decision-makers with a comprehensive, integrated view of AI program health across all dimensions—risk, performance, compliance, ethics, and operations. Fragmenting this view or focusing on narrow metrics produces an incomplete governance picture.

Why B is Correct: The ISACA AAIR governance reporting guidance recommends aggregating diverse metrics from all AI life cycle stages as the best approach for an enterprise governance dashboard. This comprehensive aggregation enables decision-makers to see the full AI risk and performance picture—from data quality in training through deployment performance, bias monitoring, security incidents, and compliance status—in a single, actionable view. This unified perspective supports informed enterprise-level governance decisions.

Why A is Wrong: Uptime and availability metrics are operational infrastructure indicators that represent only one dimension of AI governance. Focusing primarily on availability misses critical governance concerns including model fairness, accuracy, bias, and ethical compliance.

Why C is Wrong: Risk heat maps based solely on training variance are narrow technical performance indicators. A governance dashboard requires breadth across risk types and life cycle stages, not depth on one specific technical metric.

Why D is Wrong: Assigning dashboard responsibility exclusively to IT centralizes governance reporting in one function that may lack visibility into business risk, ethical compliance, and strategic alignment dimensions of AI governance. Enterprise dashboards require cross-functional input and ownership.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Third-party AI requires greater continuous monitoring because models, data, dependencies, and provider behavior can change over time. Traditional onboarding assessments alone may not detect drift, updates, or newly introduced AI-specific risk. This makes option C, Greater emphasis on continuous monitoring due to the dynamically evolving nature of AI models, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Third-party AI integration requires enforceable allocation of responsibility. Contractual accountability for AI controls clarifies which party must implement, maintain, monitor, and remediate controls across the supplier relationship. This makes option A, Assigning contractual accountability for AI controls, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Business continuity planning for customer-facing AI solutions must ensure service availability and resilience under failure conditions. The BCP must specify the technical and operational mechanisms that maintain service continuity when primary systems are disrupted.

Why B is Correct: The ISACA AAIR business continuity guidance identifies secure access to alternate resources, multi-region failover, and load balancing as the most important additions to a BCP for customer-facing AI. These mechanisms ensure that service disruptions—whether from technical failures, cyber incidents, or regional outages—do not result in total unavailability. For customer-facing solutions, maintaining service continuity directly affects customer trust, revenue, and regulatory compliance with service availability obligations.

Why A is Wrong: Post-incident audits of recovery times and accuracy metrics are monitoring activities that occur after incidents. While valuable for improvement planning, they do not define the recovery mechanisms that the BCP must specify to ensure continuity during disruptions.

Why C is Wrong: Centralizing failover under a single cloud provider creates a concentration risk—if that provider experiences an outage, all failover mechanisms fail simultaneously. Good BCP design requires geographic and provider diversification, not concentration.

Why D is Wrong: Breach containment criteria address security incident response, not service continuity. While related to incident management, breach response procedures are typically documented in the incident response plan rather than the BCP, which focuses on maintaining or restoring business operations.

Model poisoning attacks target the training data or model parameters to degrade performance or introduce malicious behavior. Supply chain tampering introduces compromised components at vendor or integration stages. Security by design principles require embedding defenses against these threats from the earliest design stages.

Why C is Correct: According to ISACA AAIR security by design guidance, adversarial resilience and data integrity controls address both model poisoning and supply chain tampering at their root. Adversarial resilience training prepares the model to resist maliciously crafted inputs. Data integrity controls—cryptographic signing, provenance tracking, integrity verification—detect tampering in training data and model artifacts across the supply chain. Together, these form the most comprehensive defense against both attack categories.

Why A is Wrong: Data refreshes with checksums detect post-hoc data corruption but do not build adversarial resilience into the model itself. Checksums verify file integrity but cannot prevent poisoning attacks that maintain file integrity while altering data content.

Why B is Wrong: Frequent retraining and bias monitoring address performance drift and fairness but do not specifically protect against deliberate tampering. A retrained model may still be trained on poisoned data if integrity controls are absent.

Why D is Wrong: Data tokenization protects sensitive field values from unauthorized access (a privacy control) but does not address model poisoning or supply chain tampering, which can occur without accessing or exposing the sensitive field values themselves.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Retrieval-augmented generation improves LLM responses by retrieving relevant external information at inference time and supplying it as context. This can improve grounding and currency without extensive retraining of the underlying model. This makes option B, Retrieval-augmented generation (RAG), the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Adversarial testing deliberately supplies malformed, misleading, or hostile inputs to reveal failure modes that ordinary accuracy or load testing may miss. This is especially important for customer-facing AI where unexpected inputs can manipulate or degrade outputs. This makes option A, Using adversarial inputs to determine failure modes, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. Embedding human-centered values in AI governance is intended to reduce societal, safety, ethical, and environmental harms and protect the rights and interests of affected stakeholders. Transparency and organizational legitimacy are related benefits but are narrower outcomes. This makes option C, Mitigating societal and environmental risk, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. Governance should scale controls to the impact of the customer-service AI system and involve business stakeholders so the control environment reflects risk tolerance and gains operational support. Monitoring alone does not create cultural alignment. This makes option C, Scale controls to AI system impact and involve business stakeholders to obtain buy-in, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Generative AI capabilities and the associated risk landscape evolve rapidly. Governance policies and controls must be refreshed through a structured, regular process rather than reactively or only when compliance requirements change.

Why A is Correct: According to ISACA AAIR, establishing a regular review cadence with codified reassessment procedures is the most robust approach because it creates a systematic, predictable process for keeping governance current. By documenting when and how policies will be reviewed—including triggers for ad hoc review (new deployments, incidents, regulatory changes)—the organization ensures governance never stagnates regardless of external pressures.

Why B is Wrong: Regulatory alignment is an important input to governance refresh but represents a reactive, external-trigger approach. Relying primarily on regulatory signals means governance lags behind organizational AI changes not covered by new regulations.

Why C is Wrong: Centralizing authority in executive and technical leadership creates decision bottlenecks and reduces the operational agility needed to keep pace with rapidly evolving AI deployments. Distributed governance with clear escalation paths is more effective.

Why D is Wrong: Annual reviews are too infrequent for generative AI tools, which may see significant capability changes and risk profile shifts multiple times per year. Annual compliance audits cannot keep governance current in a rapidly evolving AI environment.

Business-critical AI decision systems require comprehensive testing of failure modes and recovery procedures before deployment. For systems making consequential decisions, untested failure scenarios create significant operational, financial, and reputational risks when failures occur in production.

Why C is Correct: The ISACA AAIR testing and validation guidance identifies insufficient scenario-based failure mode testing as the greatest concern for business-critical AI. Without testing how the system behaves when it fails—what recovery procedures activate, how human oversight is engaged, how data integrity is maintained during failures—organizations cannot be confident the system can be safely operated through failures. For critical systems, untested failure scenarios represent unacceptable operational risk.

Why A is Wrong: Conventional security providers may require AI-specific expertise supplements but represent an operational security management concern rather than the greatest risk to system reliability and safety. Security monitoring can be supplemented without fundamentally threatening critical system operations.

Why B is Wrong: Cross-functional incident training gaps are a significant organizational preparedness concern but represent a human capability gap that can be addressed through training programs. The system design risk of untested failure modes is more fundamental.

Why D is Wrong: Not requiring 100% decision accuracy is appropriate risk tolerance calibration—no AI system achieves perfect accuracy, and setting realistic thresholds is a sign of mature risk governance. This reflects sound risk acceptance practice rather than a governance concern.

Different AI model architectures are optimized for different tasks. Content creation requires a model that can generate novel outputs—text, images, audio, or code—rather than classify, cluster, or optimize decisions based on rules or rewards.

Why A is Correct: According to ISACA AAIR AI technology selection guidance, generative models are specifically designed to synthesize new content by learning the underlying probability distributions of training data. They can produce novel, contextually appropriate outputs—exactly what content creation requires. Large language models (LLMs), diffusion models, and GANs are generative architectures designed for this purpose.

Why B is Wrong: Unsupervised clustering groups existing data points by similarity but does not generate new content. It is used for pattern discovery and segmentation, not creative output generation.

Why C is Wrong: Rule-based expert systems execute predefined logic trees and cannot produce novel content beyond the rules explicitly encoded. They are rigid, deterministic systems unsuitable for open-ended content creation.

Why D is Wrong: Reinforcement learning optimizes decision sequences to maximize cumulative rewards. It is suited for sequential decision-making tasks (games, robotics, recommendation systems) but is not the appropriate architecture for direct content generation.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Aircraft-component failure prediction is safety-critical, so robust safety validation must demonstrate acceptable behavior, limitations, and failure modes before reliance. Integration, sensor capacity, and maintenance history support performance but do not replace safety assurance. This makes option C, Robust safety validation mechanisms, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Temperature is a hyperparameter in language model generation that controls output randomness. Lower temperatures make the model more deterministic—concentrating probability mass on the most likely tokens and producing more consistent, predictable outputs. Higher temperatures introduce more randomness and diversity.

Why B is Correct: According to ISACA AAIR model configuration guidance, lowering model temperature is primarily used to enhance consistency and accuracy of outputs. In production applications requiring reliable, reproducible responses—such as customer service, compliance reporting, or technical documentation—lower temperature ensures the model consistently generates the most appropriate response based on its learned knowledge, reducing variability and improving output quality.

Why A is Wrong: Temperature adjustment does not directly mitigate bias. Bias in AI models is a function of training data and model architecture, not output randomness. A biased model at low temperature will consistently generate biased outputs; lowering temperature may actually make bias more persistent by reducing variation.

Why C is Wrong: Diversifying ideas and recommendations is achieved by increasing temperature, not lowering it. Higher temperature is used for creative tasks where variety is valuable; lower temperature is used for tasks requiring precision and consistency.

Why D is Wrong: Model temperature has no direct relationship to computational energy consumption. Energy use is primarily driven by model size, computation requirements, and inference frequency—not the temperature parameter.

Within the ISACA Advanced in AI Risk framework, governance decisions should align AI use with policy, accountability, stakeholder expectations, risk appetite, and applicable legal or ethical obligations. An AI governance framework primarily creates structured enterprise oversight, accountability, policy alignment, monitoring, and compliance. Resource allocation and technical standardization may improve, but they are secondary outcomes rather than the central governance benefit. This makes option A, Structured enterprise AI risk oversight and compliance, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Evasion attacks involve adversaries crafting inputs specifically designed to fool AI models into producing incorrect outputs—for example, manipulating images to evade object detection or modifying text to bypass content classifiers. Detecting these attacks requires identifying inputs that are statistically unusual or inconsistent with legitimate use patterns.

Why B is Correct: The ISACA AAIR adversarial AI security guidance identifies anomaly detection as the most effective mitigation for evasion attacks. Anomaly detection systems monitor input distributions, model query patterns, and output characteristics for statistical deviations that indicate adversarial manipulation. By identifying inputs that fall outside expected distributions or trigger unusual model responses, anomaly detection catches evasion attempts before they produce harmful outputs.

Why A is Wrong: API rate limiting controls query frequency to prevent brute-force model probing but does not detect or prevent crafted adversarial inputs sent at normal rates. An attacker can evade rate limits by spacing requests or distributing queries.

Why C is Wrong: Predictive analytics uses historical patterns to forecast future outcomes. It does not specifically detect real-time adversarial manipulation of model inputs.

Why D is Wrong: Feature importance weighting adjusts how much different input features influence model predictions. While it can improve robustness to irrelevant features, it does not detect adversarial inputs specifically crafted to exploit important features.

Acceptable use policies (AUPs) govern how employees interact with organizational systems and tools. Embedding AI risk considerations into AUPs ensures that AI-related behaviors align with the organization ' s risk appetite and tolerance thresholds.

Why C is Correct: According to ISACA AAIR governance principles, the best justification for embedding AI risk in AUPs is maintaining consistent enterprise risk tolerance across all AI-driven decision-making. When risk tolerances are codified in AUPs, employees understand what AI behaviors are permissible, and deviation from these boundaries triggers escalation. This enterprise-wide alignment prevents individual business units from accepting risks that exceed organizational thresholds.

Why A is Wrong: Shadow AI mitigation through allow lists is a specific technical control mechanism, not the primary governance justification for AUP integration. It addresses unauthorized tool use rather than risk tolerance alignment.

Why B is Wrong: Applying uniform risk controls across diverse business functions is a compliance approach that may not be appropriate—different functions may legitimately have different risk profiles. The goal is tolerance alignment, not control uniformity.

Why D is Wrong: Assigning accountability to business unit leadership is a governance structure decision. AUPs define behavioral expectations, not organizational accountability assignments, which are addressed through RACI frameworks and policy governance.

Enterprise risk framework integration elevates AI risk management from a technical discipline to a strategic organizational function, ensuring AI risks are considered alongside all other enterprise risks in strategic planning and decision-making.

Why D is Correct: The ISACA AAIR curriculum identifies enterprise integration as the mechanism that enables organization-level oversight and ensures AI risk management aligns with strategic objectives, risk appetite, and governance structures. This integration allows the board and senior management to make informed decisions about AI investment, deployment, and risk acceptance with full awareness of AI ' s contribution to the organizational risk profile.

Why A is Wrong: KPI benchmarking is an operational performance management activity. While integration may improve KPI accuracy, this is a secondary operational benefit rather than the primary strategic benefit of ERM integration.

Why B is Wrong: Regulatory compliance is improved by integration but represents a specific compliance benefit rather than the primary organizational value. Compliance is an output of good governance, not the purpose of ERM integration.

Why C is Wrong: Cyber threat identification is a security function that benefits from integration but is not the primary benefit. Many AI risks are non-cyber in nature—fairness, accuracy, transparency—and would not be captured by a cyber-focused framing.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Unsupervised learning operates without predefined labels, making discovered patterns harder to validate and explain against known targets. This creates particular assurance challenges around interpretation, labeling, and explainability compared with supervised classification. This makes option D, Lack of labeling and explainability, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Explainability depends on traceability. Documentation of model logic and data provenance provides evidence of how outputs were produced and which data influenced them, supporting auditability, accountability, and meaningful review of AI decisions. This makes option D, Documentation of model logic and data provenance, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while pre serving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Shared cloud infrastructure creates confidentiality and integrity exposure for model weights and data. Unauthorized access can disclose proprietary models, sensitive training information, or customer data, making this more significant than cost, latency, or scaling concerns. This makes option B, Unauthorized access to model weights and data, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Adversarial training improves model robustness against known attack patterns by incorporating adversarial examples into the training process. However, no single security technique provides comprehensive protection—adversarial training addresses only the attack vectors it was designed for, leaving other vulnerabilities unaddressed.

Why B is Correct: The ISACA AAIR security defense-in-depth guidance identifies residual system vulnerabilities as the greatest risk when adversarial training is the sole security measure. Adversarial training protects against specific attack types (evasion, perturbation) but does not address infrastructure vulnerabilities, API security weaknesses, model inversion attacks, membership inference, or other security risks present in a testing environment. A defense-in-depth approach is required for comprehensive protection.

Why A is Wrong: Adversarial training does increase computational requirements and may extend training cycles, but inefficiency is an operational concern rather than a security risk. The security risk of unprotected vulnerabilities significantly outweighs training cycle efficiency.

Why C is Wrong: Overfitting to adversarial training examples is a model quality concern that can be managed through standard regularization techniques. It represents a model performance trade-off, not the greatest security risk from relying solely on adversarial training.

Why D is Wrong: Exposure of proprietary algorithms is an intellectual property risk that is not specifically increased by relying on adversarial training. Algorithm confidentiality is protected through access controls and encryption, which are separate from the adversarial training approach.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. AI supply-chain assurance depends on verifiable end-to-end provenance of models and data so the organization can trace origin, modification, and integrity. Training and indemnity clauses help governance but do not prove that supplied artifacts are trustworthy. This makes option C, Verifiable end-to-end provenance of models and data, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

When AI is deployed without governance integration, no formal structure exists to assign control ownership, coordinate risk management activities, or align AI decision-making with organizational objectives. This structural void produces divergent, fragmented, and potentially conflicting risk management efforts.

Why C is Correct: According to ISACA AAIR, unclear ownership is the greatest organizational risk from AI operating outside governance structures. Without designated owners, controls may be applied inconsistently across business units, different teams may implement conflicting approaches, and no one is responsible for ensuring AI activities align with enterprise objectives. This governance vacuum creates unmanaged risks and organizational incoherence.

Why A is Wrong: Regulatory compliance documentation gaps are significant but are a downstream symptom of poor governance rather than the root organizational risk. Documentation failures can be remediated more easily than fundamental ownership gaps.

Why B is Wrong: Technical-business alignment is an important concern but represents a strategic planning challenge rather than the greatest organizational risk from absent governance. Alignment can be achieved through business case processes without full governance integration.

Why D is Wrong: Executive approval difficulty is an organizational change management challenge. It reflects organizational politics rather than a structural risk from absent governance. Approval processes function independently of AI governance integration.

Algorithm selection is a foundational risk management decision in AI development. The wrong algorithm for a given use case can produce inaccurate, unreliable, or harmful outputs regardless of the quality of training data or computational resources applied.

Why D is Correct: The ISACA AAIR model development guidance identifies use case alignment as the most critical algorithm selection criterion. Supervised and unsupervised learning are suited to fundamentally different problem types—supervised learning requires labeled training data and learns mappings to known outputs; unsupervised learning discovers patterns in unlabeled data. Selecting algorithms whose capabilities match the use case ' s structure and objectives prevents systematic performance failures and misapplied AI.

Why A is Wrong: Generalization capability is an important model quality criterion but represents one of many algorithmic properties. Strong generalization on the wrong problem type still produces poor results. Use case alignment precedes generalization as a selection criterion.

Why B is Wrong: Requiring supervised learning for all training projects is an inappropriate blanket policy. Many valuable use cases—anomaly detection, customer segmentation, exploratory analytics—are better served by unsupervised approaches. Mandating supervised learning prevents optimal use case matching.

Why C is Wrong: Computational cost is a resource management consideration. Optimizing for cost at the expense of use case fit risks deploying inappropriate models that produce unreliable outputs, creating far greater costs through remediation or harm.

Autonomous agents creating HR system identities that exist outside the organization ' s federated identity management system create invisible, unmanaged access pathways. These shadow identities bypass the centralized access governance controls designed to enforce least privilege, monitor access activity, and enable rapid deprovisioning.

Why D is Correct: According to ISACA AAIR identity and access management guidance for autonomous AI systems, identities not incorporated into the federated system pose the greatest risk because they are invisible to access governance processes. Federated identity management provides centralized provisioning, deprovisioning, monitoring, and policy enforcement. Autonomous identities outside this system can accumulate inappropriate access rights, persist after their legitimate purpose expires, and be used for unauthorized actions—entirely outside the organization ' s visibility.

Why A is Wrong: Breach identification delays are a consequence of the visibility gap created by ungoverned identities, not the root risk. The primary risk is the existence of invisible access pathways; delayed detection is a downstream effect.

Why B is Wrong: Ineffective credential management is a specific implementation problem with known credentials. The greater risk here is identities that the credential management system doesn ' t know about at all—complete invisibility is worse than imperfect management.

Why C is Wrong: Increased staffing for human validation is an operational resource impact. While relevant to managing autonomous agent oversight, staffing requirements are a manageable operational concern, not the greatest governance risk from ungoverned identities.

AI governance frameworks that are disconnected from organizational culture and risk tolerance face adoption resistance and produce policies that are either too restrictive or too permissive. Tailored governance is more likely to be embraced by stakeholders and produce risk policies calibrated to the organization ' s actual risk appetite.

Why B is Correct: The ISACA AAIR Study Guide emphasizes that governance tailored to culture and risk tolerance produces two primary benefits: stakeholders are more likely to accept and follow governance policies that reflect their own values and operational realities, and the resulting policies are appropriately calibrated to actual risk appetite rather than generic standards. Together, these produce more effective, sustainable governance.

Why A is Wrong: Model explainability is a technical property of individual AI systems, not a governance tailoring outcome. Regulatory compliance may improve with tailored governance but is a compliance benefit, not the primary benefit of cultural alignment.

Why C is Wrong: Automation of risk assessment and accountability clarity are process improvements that may result from better governance design but are not the primary benefit of cultural and risk tolerance alignment.

Why D is Wrong: Training programs and reskilling are workforce development activities. While governance reform may highlight training needs, skills development is an enabling activity rather than the primary benefit of culturally tailored governance.

Credit scoring AI systems make high-stakes financial decisions that directly affect individuals ' access to credit. Post-implementation review for such systems must confirm that the system performs within ethical, legal, and regulatory boundaries—particularly regarding fairness and explainability.

Why B is Correct: According to ISACA AAIR post-implementation review guidance for high-stakes AI, confirming explainability and fairness is the most critical review element for credit scoring systems. Anti-discrimination laws (Equal Credit Opportunity Act, Fair Housing Act) require that credit decisions be explainable and not discriminatory. Fairness testing detects whether the system produces disparate outcomes across demographic groups, while explainability ensures individual decisions can be justified if challenged.

Why A is Wrong: Access token logging is a security audit trail mechanism. While important for access governance, it does not address the primary regulatory and ethical obligations of a credit scoring system regarding decision quality and fairness.

Why C is Wrong: Stakeholder communication of performance metrics is a governance reporting activity. Metric communication does not confirm the system is making fair, explainable decisions—it only reports on performance indicators.

Why D is Wrong: User ease of learning and use is a user experience and adoption concern. System usability does not determine whether credit scoring decisions are accurate, fair, or legally compliant—which are the primary post-implementation concerns.

Risk scenario development in AI requires that scenarios be grounded in organizational context, business processes, and actual threat landscapes. Risk scenarios must reflect the specific systems, data flows, and stakeholder concerns relevant to the organization.

Why D is Correct: According to the ISACA AAIR Study Guide, engaging key stakeholders is the cornerstone of effective risk scenario development. Stakeholders bring domain knowledge, business context, and awareness of operational dependencies that technical practitioners may lack. This collaborative approach ensures scenarios address real-world consequences, organizational risk appetite, and business-critical functions—making them actionable and relevant.

Why A is Wrong: Adversarial testing in a sandbox validates controls but does not by itself produce contextually relevant risk scenarios. It is a technical activity, not a scenario development process.

Why B is Wrong: Peer benchmarking provides useful threat intelligence but cannot replace stakeholder engagement. Industry peer data may not reflect the organization ' s specific AI architecture or risk tolerance.

Why C is Wrong: Data flow diagrams are useful supporting artifacts but describe technical pathways rather than capturing the organizational and business context required for relevant risk scenarios.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. A deployed model must remain aligned with the business requirements for which it was approved. Validation helps detect unintended behavior that may be technically plausible but operationally harmful, inappropriate, or outside the intended use case. This makes option A, To mitigate risk from unintended model behavior, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Open-source AI components should be traceable so the organization can verify origin, dependencies, integrity, licensing, and maintenance history. Geography and cost are secondary, and documentation ownership alone does not establish trustworthy provenance. This makes option A, Traceability for open-source AI artifacts, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, program management connects risk identification, control selection, treatment, monitoring, resilience, third-party oversight, and reporting to enterprise risk objectives. Risk scenario identification should focus on the severity of potential adverse effects on critical stakeholders and organizational objectives. Technical details such as encryption or dataset volume are controls or implementation factors, while impact drives scenario significance. This makes option C, Severity of adverse effects on critical stakeholders and objectives, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Within the ISACA Advanced in AI Risk framework, life-cycle controls should protect data quality, model design, testing, validation, monitoring, change management, and secure retirement of AI systems. Training from sources with different update frequencies and quality can introduce conflicting, stale, or incomplete information, leading to inconsistent model outputs and operational decisions. Cost and integration issues are secondary to unreliable decision quality. This makes option A, Inconsistency in model outputs and operational decisions, the strongest answer. The other choices describe narrower technical, operational, performance, or administrative considerations and do not address the primary risk-management objective in the scenario as directly. A risk practitioner should select the response that most effectively reduces the stated exposure while preserving appropriate oversight, traceability, and alignment with organizational risk tolerance and business requirements.

Chatbot accuracy in customer service depends on correctly identifying customer intent and generating appropriate responses. Both intent classification accuracy and training data quality directly determine chatbot performance over time.

Why D is Correct: According to ISACA AAIR model performance management guidance, measuring intent-classification error rates provides precise diagnostic information about where the chatbot misunderstands customer inquiries, while refining training datasets based on those errors continuously improves classification accuracy. This closed-loop approach—measure specific errors, improve the underlying data that drives them—is the most effective mechanism for sustained high accuracy.

Why A is Wrong: Increasing model temperature increases output randomness and diversity, which is counterproductive for accuracy in customer service contexts where consistent, precise answers are required. Precision and recall provide useful metrics but increased temperature actively undermines accuracy.

Why B is Wrong: Vendor benchmarking compares performance against generic standards. Customer service chatbots must be optimized for the specific organization ' s terminology, products, and customer base—generic thresholds may not capture the accuracy requirements of a specific deployment.

Why C is Wrong: Explainable AI techniques improve decision transparency but do not directly enhance classification accuracy. Code reviews address software quality, not the model ' s ability to accurately interpret customer intent.

Even when an AI system is initially assessed as within risk tolerance, its risk profile evolves as the system encounters new data, the operational environment changes, and model performance drifts. Controls that were effective at deployment may become insufficient as these changes accumulate.

Why C is Correct: The ISACA AAIR operational monitoring guidance identifies continuous monitoring for data and performance drift as the most important mechanism for maintaining control effectiveness over time. Drift detection provides early warning when the AI system begins behaving differently from its validated state—enabling timely control adjustments before risk tolerance is breached. This is particularly critical because AI systems can degrade gradually in ways not visible without active monitoring.

Why A is Wrong: Framework alignment establishes the control baseline but does not actively verify that controls remain effective as the system evolves. Frameworks provide structure; monitoring provides assurance.

Why B is Wrong: Security and risk awareness training is an important human capability development activity but does not detect technical changes in AI system behavior. Training does not substitute for technical monitoring.

Why D is Wrong: Periodic compliance reviews occur at scheduled intervals and may miss drift that develops between review cycles. Continuous monitoring provides real-time detection that periodic reviews cannot match.