IAPP AIGP Practice Test 85
Question 840
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. The development team must show evidence before promoting the next model version. A material exception remains unresolved. Which containment decision best protects affected parties?
- Escalate unresolved critical findings and restrict risky releases until assurance gaps close.
- Restore the last valid feature pipeline or model while investigating the failure.
- Restrict unvalidated downstream claims until model documentation is corrected.
- Withhold production promotion until required launch controls pass.
Explanation
Correct Answer
B:Restore the last valid feature pipeline or model while investigating the failure. Correct. It limits further reliance or exposure while the risk remains unresolved. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Escalate unresolved critical findings and restrict risky releases until assurance gaps close. Not selected. That response contains a different failure mode and leaves the stated risk unresolved. It belongs with Periodic independent audits: Independent audit contributes objective scrutiny that ordinary self-monitoring cannot replace. The present case instead concerns Root-cause analysis of model failures.
C:Restrict unvalidated downstream claims until model documentation is corrected. Not selected. That response contains a different failure mode and leaves the stated risk unresolved. It belongs with Model cards and limitations: Model cards communicate evidence, limits and proper interpretation to deployment teams. The present case instead concerns Root-cause analysis of model failures.
D:Withhold production promotion until required launch controls pass. Not selected. That response contains a different failure mode and leaves the stated risk unresolved. It belongs with Release readiness checklist: A release gate is a risk acceptance decision supported by evidence, not a calendar milestone. The present case instead concerns Root-cause analysis of model failures.
Question 841
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. Model assurance reviewers need a documented control before approving continued experimentation. Before selecting a remedy, what should the accountable reviewer investigate first?
- Inspect retraining triggers, dataset changes, performance evidence and promotion permissions.
- Identify realistic misuse paths, privileged tools, high-risk prompts and known failure classes.
- Correlate model, dataset, feature pipeline and upstream service versions with the first failure time.
- Review release artifacts, version pins, rollback dependencies and user communication plans.
Explanation
Correct Answer
C:Correlate model, dataset, feature pipeline and upstream service versions with the first failure time. Correct. It establishes the relevant factual risk boundary before implementation. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Inspect retraining triggers, dataset changes, performance evidence and promotion permissions. Not selected. That check primarily diagnoses a different governance issue. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Root-cause analysis of model failures.
B:Identify realistic misuse paths, privileged tools, high-risk prompts and known failure classes. Not selected. That check primarily diagnoses a different governance issue. It belongs with Red-team exercise design: Adversarial testing probes how a system can fail under purposeful misuse rather than normal usage. The present case instead concerns Root-cause analysis of model failures.
D:Review release artifacts, version pins, rollback dependencies and user communication plans. Not selected. That check primarily diagnoses a different governance issue. It belongs with Version deprecation and rollback: Model lifecycle governance needs controlled retirement and rollback, not irreversible swaps. The present case instead concerns Root-cause analysis of model failures.
Question 842
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. Model assurance reviewers need a documented control before approving continued experimentation. What action should the accountable team prioritize to govern this use responsibly?
- Run structured cross-functional causal analysis before changing thresholds or retraining blindly.
- Create an AI-specific incident category with escalation to business owners and risk management.
- Implement data, concept and performance drift monitoring with ownership and trigger thresholds.
- Run controlled red-team tests with measurable objectives and protected test artifacts.
Explanation
Correct Answer
A:Run structured cross-functional causal analysis before changing thresholds or retraining blindly. Correct. It directly reduces or governs the specific documented risk. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
B:Create an AI-specific incident category with escalation to business owners and risk management. Not selected. That action treats another control objective, not the specific gap described. It belongs with AI incident classification: A system can be operationally available while causing a serious output-quality incident. The present case instead concerns Root-cause analysis of model failures.
C:Implement data, concept and performance drift monitoring with ownership and trigger thresholds. Not selected. That action treats another control objective, not the specific gap described. It belongs with Monitoring and drift: AI monitoring must measure model behavior and data context, not only infrastructure availability. The present case instead concerns Root-cause analysis of model failures.
D:Run controlled red-team tests with measurable objectives and protected test artifacts. Not selected. That action treats another control objective, not the specific gap described. It belongs with Red-team exercise design: Adversarial testing probes how a system can fail under purposeful misuse rather than normal usage. The present case instead concerns Root-cause analysis of model failures.
Question 843
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. Model assurance reviewers need a documented control before approving continued experimentation. What result would provide the strongest case-specific assurance?
- Replay representative failing cases against prior and current pipeline versions.
- Compare candidate and current models on safety and subgroup test suites before promotion.
- Check downstream integrators can distinguish validated use from unsupported extensions.
- Confirm the integrator can apply the necessary restrictions and escalation procedures.
Explanation
Correct Answer
A:Replay representative failing cases against prior and current pipeline versions. Correct. It yields measurable evidence that the case-specific safeguard works. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
B:Compare candidate and current models on safety and subgroup test suites before promotion. Not selected. That test would not demonstrate this particular risk has been addressed. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Root-cause analysis of model failures.
C:Check downstream integrators can distinguish validated use from unsupported extensions. Not selected. That test would not demonstrate this particular risk has been addressed. It belongs with Model cards and limitations: Model cards communicate evidence, limits and proper interpretation to deployment teams. The present case instead concerns Root-cause analysis of model failures.
D:Confirm the integrator can apply the necessary restrictions and escalation procedures. Not selected. That test would not demonstrate this particular risk has been addressed. It belongs with Public and downstream disclosure: Developer-to-deployer documentation transfers essential risk information across the AI supply chain. The present case instead concerns Root-cause analysis of model failures.
Question 844
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. Model assurance reviewers need a documented control before approving continued experimentation. Which TWO actions form the appropriate investigation-and-control pair for this case?
- Maintain staged rollout, backward-compatible versioning and an exercised emergency rollback path.
- Review required release artifacts: use-case scope, impact assessment, evaluation, security review and rollback plan.
- Correlate model, dataset, feature pipeline and upstream service versions with the first failure time.
- Run structured cross-functional causal analysis before changing thresholds or retraining blindly.
Explanation
Correct Answers
C:Correlate model, dataset, feature pipeline and upstream service versions with the first failure time. Correct. As the first, evidence-gathering half of the requested pair, this establishes the specific risk boundary. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
D:Run structured cross-functional causal analysis before changing thresholds or retraining blindly. Correct. As the second, implementation half of the requested pair, this directly applies the needed safeguard. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Maintain staged rollout, backward-compatible versioning and an exercised emergency rollback path. Not selected. It addresses a different governance mechanism, not the required assessment-and-control pair. It belongs with Version deprecation and rollback: Model lifecycle governance needs controlled retirement and rollback, not irreversible swaps. The present case instead concerns Root-cause analysis of model failures.
B:Review required release artifacts: use-case scope, impact assessment, evaluation, security review and rollback plan. Not selected. It addresses a different governance mechanism, not the required assessment-and-control pair. It belongs with Release readiness checklist: A release gate is a risk acceptance decision supported by evidence, not a calendar milestone. The present case instead concerns Root-cause analysis of model failures.
Question 845
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. A material training or architecture change makes the previous technical approval insufficient. What should the AI governance lead examine before changing the system?
- Identify realistic misuse paths, privileged tools, high-risk prompts and known failure classes.
- Inspect retraining triggers, dataset changes, performance evidence and promotion permissions.
- Correlate model, dataset, feature pipeline and upstream service versions with the first failure time.
- Map threat actors, exposed interfaces, model assets, data and attack paths.
Explanation
Correct Answer
C:Correlate model, dataset, feature pipeline and upstream service versions with the first failure time. Correct. It establishes the relevant factual risk boundary before implementation. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Identify realistic misuse paths, privileged tools, high-risk prompts and known failure classes. Not selected. That check primarily diagnoses a different governance issue. It belongs with Red-team exercise design: Adversarial testing probes how a system can fail under purposeful misuse rather than normal usage. The present case instead concerns Root-cause analysis of model failures.
B:Inspect retraining triggers, dataset changes, performance evidence and promotion permissions. Not selected. That check primarily diagnoses a different governance issue. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Root-cause analysis of model failures.
D:Map threat actors, exposed interfaces, model assets, data and attack paths. Not selected. That check primarily diagnoses a different governance issue. It belongs with AI security threat modeling: AI security includes attacks against data, models, prompts and inference services. The present case instead concerns Root-cause analysis of model failures.
Question 846
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. A material training or architecture change makes the previous technical approval insufficient. What is the most directly applicable governance control for this situation?
- Run controlled red-team tests with measurable objectives and protected test artifacts.
- Run structured cross-functional causal analysis before changing thresholds or retraining blindly.
- Require controlled retraining with versioned data, independent evaluation and approval before deployment.
- Implement data, concept and performance drift monitoring with ownership and trigger thresholds.
Explanation
Correct Answer
B:Run structured cross-functional causal analysis before changing thresholds or retraining blindly. Correct. It directly reduces or governs the specific documented risk. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Run controlled red-team tests with measurable objectives and protected test artifacts. Not selected. That action treats another control objective, not the specific gap described. It belongs with Red-team exercise design: Adversarial testing probes how a system can fail under purposeful misuse rather than normal usage. The present case instead concerns Root-cause analysis of model failures.
C:Require controlled retraining with versioned data, independent evaluation and approval before deployment. Not selected. That action treats another control objective, not the specific gap described. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Root-cause analysis of model failures.
D:Implement data, concept and performance drift monitoring with ownership and trigger thresholds. Not selected. That action treats another control objective, not the specific gap described. It belongs with Monitoring and drift: AI monitoring must measure model behavior and data context, not only infrastructure availability. The present case instead concerns Root-cause analysis of model failures.
Question 847
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. A material training or architecture change makes the previous technical approval insufficient. What should an independent reviewer test before signing off on this specific risk?
- Compare candidate and current models on safety and subgroup test suites before promotion.
- Replay representative failing cases against prior and current pipeline versions.
- Check downstream integrators can distinguish validated use from unsupported extensions.
- Test access control, suspicious query detection and poisoning resistance in controlled exercises.
Explanation
Correct Answer
B:Replay representative failing cases against prior and current pipeline versions. Correct. It yields measurable evidence that the case-specific safeguard works. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Compare candidate and current models on safety and subgroup test suites before promotion. Not selected. That test would not demonstrate this particular risk has been addressed. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Root-cause analysis of model failures.
C:Check downstream integrators can distinguish validated use from unsupported extensions. Not selected. That test would not demonstrate this particular risk has been addressed. It belongs with Model cards and limitations: Model cards communicate evidence, limits and proper interpretation to deployment teams. The present case instead concerns Root-cause analysis of model failures.
D:Test access control, suspicious query detection and poisoning resistance in controlled exercises. Not selected. That test would not demonstrate this particular risk has been addressed. It belongs with AI security threat modeling: AI security includes attacks against data, models, prompts and inference services. The present case instead concerns Root-cause analysis of model failures.
Question 848
A model's accuracy drops after release and teams debate whether the cause is new data, a configuration change or an upstream schema break. A material training or architecture change makes the previous technical approval insufficient. What is the most relevant fallback when the promised safeguard cannot be demonstrated?
- Suspend onboarding where missing disclosures would make safe deployment impossible.
- Roll back to the previous validated model if retraining degrades accepted thresholds.
- Restore the last valid feature pipeline or model while investigating the failure.
- Reduce reliance on the model or revert to baseline when drift invalidates trusted performance.
Explanation
Correct Answer
C:Restore the last valid feature pipeline or model while investigating the failure. Correct. It limits further reliance or exposure while the risk remains unresolved. AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults.
Incorrect Answers
A:Suspend onboarding where missing disclosures would make safe deployment impossible. Not selected. That response contains a different failure mode and leaves the stated risk unresolved. It belongs with Public and downstream disclosure: Developer-to-deployer documentation transfers essential risk information across the AI supply chain. The present case instead concerns Root-cause analysis of model failures.
B:Roll back to the previous validated model if retraining degrades accepted thresholds. Not selected. That response contains a different failure mode and leaves the stated risk unresolved. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Root-cause analysis of model failures.
D:Reduce reliance on the model or revert to baseline when drift invalidates trusted performance. Not selected. That response contains a different failure mode and leaves the stated risk unresolved. It belongs with Monitoring and drift: AI monitoring must measure model behavior and data context, not only infrastructure availability. The present case instead concerns Root-cause analysis of model failures.
Question 849
An AI provider presents its own quarterly dashboard as sufficient independent assurance for every consequential model. The development team must show evidence before promoting the next model version. What should the AI governance lead examine before changing the system?
- Map threat actors, exposed interfaces, model assets, data and attack paths.
- Check audit independence, scope, criteria, sampling and access to underlying evidence.
- Review release artifacts, version pins, rollback dependencies and user communication plans.
- Inspect retraining triggers, dataset changes, performance evidence and promotion permissions.
Explanation
Correct Answer
B:Check audit independence, scope, criteria, sampling and access to underlying evidence. Correct. It establishes the relevant factual risk boundary before implementation. Independent audit contributes objective scrutiny that ordinary self-monitoring cannot replace.
Incorrect Answers
A:Map threat actors, exposed interfaces, model assets, data and attack paths. Not selected. That check primarily diagnoses a different governance issue. It belongs with AI security threat modeling: AI security includes attacks against data, models, prompts and inference services. The present case instead concerns Periodic independent audits.
C:Review release artifacts, version pins, rollback dependencies and user communication plans. Not selected. That check primarily diagnoses a different governance issue. It belongs with Version deprecation and rollback: Model lifecycle governance needs controlled retirement and rollback, not irreversible swaps. The present case instead concerns Periodic independent audits.
D:Inspect retraining triggers, dataset changes, performance evidence and promotion permissions. Not selected. That check primarily diagnoses a different governance issue. It belongs with Scheduled retraining governance: Retraining is a new model change that requires testing, traceability and accountable release. The present case instead concerns Periodic independent audits.
Question 850
An AI provider presents its own quarterly dashboard as sufficient independent assurance for every consequential model. The development team must show evidence before promoting the next model version. What is the most directly applicable governance control for this situation?
- Maintain staged rollout, backward-compatible versioning and an exercised emergency rollback path.
- Run structured cross-functional causal analysis before changing thresholds or retraining blindly.
- Schedule risk-based audits with appropriate independent challenge and documented findings management.
- Run controlled red-team tests with measurable objectives and protected test artifacts.
Explanation
Correct Answer
C:Schedule risk-based audits with appropriate independent challenge and documented findings management. Correct. It directly reduces or governs the specific documented risk. Independent audit contributes objective scrutiny that ordinary self-monitoring cannot replace.
Incorrect Answers
A:Maintain staged rollout, backward-compatible versioning and an exercised emergency rollback path. Not selected. That action treats another control objective, not the specific gap described. It belongs with Version deprecation and rollback: Model lifecycle governance needs controlled retirement and rollback, not irreversible swaps. The present case instead concerns Periodic independent audits.
B:Run structured cross-functional causal analysis before changing thresholds or retraining blindly. Not selected. That action treats another control objective, not the specific gap described. It belongs with Root-cause analysis of model failures: AI root-cause analysis must distinguish data drift, code defects, feedback loops and model faults. The present case instead concerns Periodic independent audits.
D:Run controlled red-team tests with measurable objectives and protected test artifacts. Not selected. That action treats another control objective, not the specific gap described. It belongs with Red-team exercise design: Adversarial testing probes how a system can fail under purposeful misuse rather than normal usage. The present case instead concerns Periodic independent audits.