CCNA Ai Governance And Risk Questions

Adversarial perturbation testing deliberately applies small, crafted input changes to measure whether predictions shift, directly quantifying robustness. It targets the model's decision boundary under malicious manipulation, which is the specific threat the audit must assess.

The four-fifths rule states that a selection rate for any protected group that is less than 80% of the rate for the highest group may indicate disparate impact. A 72% ratio falls below this threshold, requiring the auditor to examine whether the model relies on features that correlate with gender. This investigation is the primary concern because it determines whether the model violates employment discrimination law.

Real-time content filtering can block policy-violating responses, while human-in-the-loop review for high-risk interactions adds a layer of human judgment. Together, they provide continuous assurance that the chatbot adheres to policies and regulations. This combination addresses both automated and nuanced cases, offering the highest level of assurance among the options.

Operational performance degradation covers model drift, latency spikes, throughput loss and availability failures once an AI system is in production. Governing it explicitly satisfies the requirement to manage risks affecting reliability, cost and service continuity across the model lifecycle.

SHAP assigns each input feature a Shapley value derived from cooperative game theory, quantifying its marginal contribution to a specific prediction. This yields consistent, locally faithful attributions even for deep networks, satisfying explainability requirements that simpler global feature-importance scores cannot meet.

Ethics and compliance policies codify acceptable use, risk tolerance and regulatory obligations, giving the governance framework its enforceable baseline. Without documented policy, oversight bodies lack criteria to approve, restrict or retire AI systems, so this component directly satisfies the stem's demand for robust governance structure.

Retaining training data that remains re-identifiable, without access controls, breaches privacy principles because personal information persists beyond its lawful purpose. Anonymisation or strict access governance is required, so this practice directly violates data protection obligations during pre-processing.

Azure Machine Learning Model Monitor continuously evaluates deployed models, detecting data drift and tracking data quality metrics, and surfaces them through a central dashboard. This directly satisfies the Chief Risk Officer's requirement for consolidated drift and quality oversight.

SageMaker Lineage Tracking automatically records each training job's inputs, outputs and associated entities, producing an auditable graph linking models to their data sources. This directly satisfies the reproducibility requirement by evidencing lineage and versioning for every training job during AI risk assessment.

GDPR governs processing of personal data and requires anonymisation or a lawful basis; unanonymised PII in training data breaches its data protection principles. The scenario names PII specifically, which is the exact category GDPR regulates, making it the applicable regulation.

Human in the loop is a governance principle that ensures meaningful human control over AI decisions. It can take forms such as human review of flagged cases, approval of high-risk decisions, or the ability to override or reverse automated outcomes. The key is that the human has real authority and information to intervene, not merely a nominal role. This definition aligns with ISACA's emphasis on accountability in AI governance.

Defined communication protocols ensure timely, coordinated disclosure to internal teams, regulators, affected users and the public during an AI incident. This satisfies the stem's requirement for a core response component, since containment and recovery depend on clear escalation paths and stakeholder notification obligations, particularly for AI systems with safety, privacy or compliance impact.

Model Validation follows Model Training in the AI model lifecycle. After training completes, the model is evaluated against held-out data to confirm accuracy, fairness and generalisation before deployment, ensuring it meets defined performance criteria prior to release.

Independent validation subjects models to scrutiny by parties separate from developers, satisfying the stem's MRM pillar requirement. This separation of duties provides objective assessment of methodology, assumptions and outputs, which is the governance control that prevents developer bias from going unchallenged.

Post-deployment performance and drift monitoring validates that models continue performing within approved tolerances after release, detecting degradation or data drift. This satisfies MRM's requirement for ongoing monitoring controls, distinct from pre-deployment validation and development-stage testing.

Human-in-the-loop inserts a person into the decision path so consequential or low-confidence outputs are reviewed before action. This oversight catches model errors, satisfies accountability requirements and mitigates harm, which purely automated pipelines cannot guarantee on their own.

Training data provenance and lineage records where data originated, how it was collected and transformed, and its movement through the pipeline. This satisfies the inventory's requirement to document data-related risk factors, enabling traceability, bias investigation and reproducibility across the model's lifecycle.

A Model Card is a structured document disclosing a model's features, limitations and training data, supporting AI compliance through transparency and accountability. It enables auditors and stakeholders to assess intended use, bias risk and provenance, satisfying governance and documentation obligations.

Without independent validation, high-impact models escape scrutiny by parties outside the development team, so bias, drift and failure modes remain undetected until production impact occurs. This directly satisfies the consequence of removing that control from the MRM framework.

With a 0.5% fraud rate, a model can achieve 99.5% accuracy by simply predicting 'no fraud' for all transactions. Monitoring only overall accuracy would not reveal that fraudulent transactions are being missed. This is a classic pitfall with imbalanced datasets. The auditor should recommend using precision, recall, or F1-score to detect false negatives.

Generative models produce fluent output without grounding in verified fact, so they can fabricate plausible but false content. Predictive models output scores or classes from fixed features and cannot invent novel text, making hallucination and misinformation generation unique to generative AI.

An AI Policy codifies governance expectations, defining acceptable use, accountability, risk assessment and compliance requirements so teams develop and deploy AI systems responsibly. It gives structured, enforceable guidance rather than leaving ethical and regulatory decisions to individual judgement.

Assigning explicit roles and responsibilities to the AI Governance Committee and model owners creates named accountability, ensuring every AI system has an owner answerable for its risks and decisions. This directly establishes the organisational accountability the stem asks for, unlike broader policy statements.

Ethics derives from societal values and moral expectations, which may exceed or precede legislation, whereas compliance is bounded by enforceable legal and regulatory requirements. This axis of difference explains why an action can be legal yet unethical, satisfying the question's demand for the key distinction.

Quantitative thresholds translate risk appetite into measurable limits for model performance and ethical impact, giving the board objective criteria for governance decisions. This satisfies the requirement to define appetite concretely rather than as qualitative statements, enabling consistent monitoring and escalation.

Drift can shift a model's learned decision boundaries as live data diverges from training data, producing discriminatory outcomes that were absent at validation. Auditors must monitor post-deployment outputs across demographic segments to detect emergent bias rather than relying solely on pre-release testing.

A Model Card documents a model's intended use, design, performance and known limitations in a standardised format, giving external regulators the transparency evidence the AI Transparency requirement demands. It is the recognised artifact for disclosing model characteristics to third parties.

Input validation and sanitisation screen incoming training records for malformed, anomalous or adversarial samples before they enter the dataset. Rejecting or cleaning poisoned entries at ingestion stops corrupted data from skewing the retail model's learned parameters, directly mitigating data poisoning.

Manual review before execution satisfies HITL by inserting a human decision point between model output and consequential action, which is precisely where high-risk errors cause harm. Unlike post-hoc auditing or sampling, pre-execution review blocks the action until a person approves it, matching the stem's requirement for a best-practice control.

Partitioning isolates training data by tenant or purpose, and feature selection excludes identifiers and sensitive attributes, directly limiting what a model can memorise and expose. This constrains leakage at the data layer rather than detecting it afterwards.

Internal AI policy and guidelines count as governance inputs because they are artefacts fed into AI systems' development and operation, shaping decisions before outputs emerge. They satisfy the stem's requirement by governing data, model selection and usage constraints upstream, unlike monitoring reports or audit findings, which are governance outputs generated after deployment.

An AI Ethics Board provides governance oversight, reviewing AI initiatives against corporate values and societal norms before deployment. This satisfies the stem's requirement for the primary function: assessing alignment rather than performing technical implementation, model training, or regulatory enforcement. It ensures ethical considerations are embedded in decision-making across the organisation's AI portfolio.

Standardised model risk assessment templates enforce consistent scoring criteria, evidence capture and documentation across every AI model reviewed. This satisfies the framework requirement by making risk evaluations repeatable and comparable, rather than relying on ad hoc analyst judgement.

An AI audit log records inputs, outputs, model changes, and user interactions over time, creating a traceable record for accountability and compliance. This satisfies the need to track and document all interactions and changes made to the AI system.

The Govern function establishes and enforces AI risk policies, assigning accountability and controls across the organisation. It provides the documented oversight evidence a board needs to confirm its AI policy is operationally enforced, unlike Map, Measure or Manage, which address context, analysis and treatment.

Assessing likelihood and severity quantifies each identified risk, satisfying the stem's requirement to evaluate impact rather than merely list hazards. This scoring underpins prioritisation and mitigation planning, and aligns with Microsoft Entra ID governance guidance for AI systems. Without it, an AI risk assessment cannot rank threats or justify controls.

Without a defined decommissioning process, retired models remain deployed and continue serving predictions, so outdated or insecure versions persist in production. This directly satisfies the stem's missing lifecycle control, since Microsoft Entra ID and monitoring cannot compensate for absent retirement governance. The impact is sustained exposure to model drift and unpatched vulnerabilities.

Mapping each use case to the enterprise AI risk appetite ensures that risk tolerance is consistently applied across the AI portfolio. Approval by the AI governance committee provides oversight and accountability. This directly addresses the gap where use cases are approved without reference to the risk appetite statement, aligning with ISACA AAIA guidance on integrating risk appetite into AI governance.

A bias audit inspects training data for skewed representation and historical prejudice, directly targeting the unfairness and discrimination risk arising from imbalanced datasets. Because model outputs inherit these statistical distortions, auditing the data corrects the root cause rather than merely detecting downstream symptoms, satisfying the scenario's requirement to mitigate unfairness at source.

Fairness assessment examines whether error rates, false positive and false negative rates, and accuracy differ across protected groups such as sex, race, or age. Disparate error rates directly reveal bias, making this a core quantitative fairness metric.

Data poisoning targets the training phase by corrupting the labelled dataset used to fit the model, so the model learns attacker-chosen patterns. It satisfies the stem's training-phase constraint, unlike inference-time attacks such as prompt injection or model evasion, which manipulate inputs after deployment.

Statistical drift between production inputs and the training baseline signals that the data distribution the model sees has shifted away from what it learned. This covariate shift typically precedes accuracy loss, making it the earliest reliable indicator of degrading reliability on the dashboard.

The auditor's primary responsibility is to report the finding to the appropriate governance body with sufficient evidence for it to act. Escalating through the AI governance committee ensures the violation is assessed against the organization's risk appetite and that remediation is authorized at the right level. This preserves auditor independence while triggering the formal response process defined in the governance framework.

A centralized AI governance committee provides oversight, sets policies, and ensures consistent risk management across all AI initiatives. Representation from key stakeholders ensures diverse perspectives and alignment with enterprise objectives. This directly addresses the lack of central oversight by creating a governing body responsible for AI-related decisions and accountability.

Disparate Impact compares favourable outcome rates between protected and reference groups, flagging models whose decisions disproportionately disadvantage a protected class. Validating it satisfies the stem's requirement to confirm the model is not violating protected class regulations during production fairness auditing.

Microsoft Defender for Cloud Apps discovers and governs unsanctioned cloud apps and services, including AI model APIs, by analysing network traffic. It surfaces Shadow AI usage that endpoint or identity tools alone would miss, giving the visibility the scenario requires.

Validation performed by the developing team lacks organisational independence, so reviewers may rationalise their own design choices and overlook defects. This self-review bias compromises the objectivity and integrity of the validation process, which the audit stem flags as the concern.

A non-compliant model must be remediated immediately or withdrawn from production, because continued operation exposes the organisation to regulatory, ethical and reputational harm. This satisfies the governance requirement that non-compliant systems cannot remain in live service pending review.

The Model Manager or Product Owner owns the model through its lifecycle, so they translate governance policy into day-to-day practise: approving changes, monitoring performance and enforcing controls. This satisfies the daily-operations responsibility, which sits with operational ownership rather than the governance board or internal audit.

Contractual enforcement is the only mechanism that binds an external provider to the firm's governance requirements, since the firm cannot apply its internal controls directly to third-party infrastructure. The SLA translates policy obligations into auditable, enforceable commitments, satisfying the compliance constraint the scenario demands.

SHAP values assign each feature a contribution for a single prediction, giving the local, per-decision explanation the audit requires. They work with non-linear models, unlike global surrogate methods, satisfying the requirement for individual credit decision transparency.

The AI Risk Assessment documents potential harms, likelihood and severity before deployment, feeding mitigation into design. Identifying and evaluating risks pre-deployment satisfies governance requirements, unlike post-incident review or ongoing monitoring, which occur after the model is already live.

Federated learning trains models across devices without centralising raw data, so each device keeps its data locally and shares only model updates. This directly satisfies the governance requirement for data privacy, since sensitive records never leave the endpoint or reach a central repository.

Accountability is a cornerstone of AI governance, especially in healthcare where model errors can directly affect patient safety. Assigning responsibility to a named clinical leader ensures that someone with both authority and clinical expertise is answerable for the model's performance and its impact on care decisions. This control enables escalation, remediation, and alignment with the organization's risk appetite. ISACA's governance principles emphasize clear ownership of AI risks.

The AI policy defines which systems, data and processes fall within audit boundaries, while the Risk Management Framework supplies the risk criteria and control expectations used to judge them. Together they establish scope; standards and regulations inform obligations but do not themselves bound the audit.

Bias assessment and mitigation requirements directly satisfy the ethical alignment constraint by mandating documented evaluation of training data and model outputs for discriminatory patterns. This ensures AI systems undergo systematic fairness testing before deployment, addressing protected characteristics and preventing disparate impact — a core governance control that an AI Policy must specify to demonstrate regulatory and ethical compliance.

High-stakes loan decisions demand transparency and contestability, so the audit framework requires explainability. XAI tools such as SHAP or LIME expose which features drove each prediction, letting auditors and applicants challenge outcomes. This satisfies the stem's constraint that a black-box model be interpretable before deployment.

NeMo Guardrails intercepts prompts and completions, applying programmable rails that block unsafe, off-topic or policy-violating content. This enforces safety boundaries at runtime, directly satisfying the framework's need to mitigate harmful LLM input and output risk.

Defined escalation paths satisfy the plan's compliance requirement by routing ethical or performance incidents to accountable owners within set timeframes. This ensures AI failures are triaged, documented and remediated under governance controls, rather than handled ad hoc. Escalation ownership is what auditors expect to see evidenced in an AI incident response plan.

Broken lineage between feature store and training pipeline means the provenance of features cannot be traced, so metadata logging and transformation documentation are deficient. Without recorded transformations and versions, reproducibility and regulatory auditability of the model fail.

Automated re-training triggered by performance thresholds directly counters concept drift by refreshing the model whenever its mapping between inputs and outputs degrades. Unlike static retraining schedules, threshold triggers respond to actual distributional change, satisfying the requirement to mitigate drift in production where data distributions evolve unpredictably over time.

Concept drift occurs when the relationship between input features and the target variable changes over time. In fraud detection, fraudsters continuously adapt their tactics, so patterns that indicated fraud two years ago may no longer be valid. The model's degradation despite no change in code or data pipeline is a classic symptom of concept drift. The auditor should flag this as a model risk requiring retraining and ongoing monitoring.

Basic regulatory expectations require each inventory entry to identify an accountable model owner, the documented business purpose, and the model's current lifecycle status. These three fields establish accountability, intended use and operational state, which auditors need before assessing risk or compliance.

Likelihood and impact are fundamental to risk prioritization in any domain, including AI. Risks with high probability and severe consequences should be prioritized. This aligns with standard risk management frameworks and ISACA guidance. It ensures that resources are allocated to the most significant threats to business objectives.

Prompt injection succeeds because untrusted input reaches the model without filtering or adversarial testing. Inadequate input validation and absent red-team exercises let crafted prompts override instructions, so the governance failure is the missing validation and testing controls around the Inference API.

Trustworthy AI frameworks require reliability and consistent performance so the system behaves predictably across its lifecycle, satisfying the criterion that outputs remain dependable under expected operating conditions rather than degrading or drifting unpredictably over time.

Versioning records each model iteration with its training data, parameters and artefacts, so any past version can be reconstructed and its decisions traced. This directly satisfies the audit requirement for reproducibility and auditability of historical model versions during review.

Board-level governance sets direction rather than managing operational controls. It ensures AI initiatives align with corporate strategy and the board's stated risk appetite, satisfying the stem's demand for the primary objective at that oversight tier.

Board-level oversight means governing direction and risk appetite, not operational detail. Approving the annual AI strategy alongside its risk mitigation plans exercises that authority, ensuring AI initiatives align with organisational objectives and acceptable risk tolerances.

Independent model validation reports evidence that a party separate from development assessed the model's methodology, assumptions and outputs. This provides the objective, documented scrutiny auditors need to confirm that model governance controls operated effectively throughout the life cycle.

Systemic bias in a core lending model causes discriminatory credit decisions across protected groups, breaching fair-lending regulation and affecting many customers. That enterprise-wide harm and legal exposure elevates it to High severity, triggering immediate board notification.