AIGP - Understanding how to govern AI development (27% of the exam) - Section 3.6

Conduct continuous monitoring, periodic audits, red teaming and security testing of deployed AI systems, and manage and document incidents, issues and risks including model and data drift.

Conduct continuous monitoring, periodic audits, and red teaming on deployed AI systems to detect model drift, data drift, and emerging security risks. Manage and document incidents and issues according to a defined response process.

AI model monitoringred teamingmodel driftdata drift

Practice question for this objective

Free sampleUnderstanding how to govern AI developmenthard

Security testing of a deployed image-classification model focuses on one specific threat: an attacker who, at inference time, adds small perturbations to a submitted image that are imperceptible to a person yet cause the model to output the wrong label. The team wants the test procedure that directly probes resilience to this threat. Which testing approach targets it most precisely?

  • AInjecting mislabelled or corrupted records into the training corpus and observing how the retrained model behaves afterwards.
  • BIssuing many crafted queries to reconstruct the model's parameters or training data, then checking what an attacker could recover.
  • CReplaying historical production traffic at high volume to confirm the serving system keeps responding under heavy load.
  • DGenerating adversarial examples through small, targeted perturbations of inputs and measuring how often they flip the model's predictions. Correct
Match an inference-time evasion threat to adversarial-example testing, distinguishing it from data poisoning, model extraction, and load testing. The threat described is an evasion attack, where carefully perturbed inputs cause misclassification at inference time, so the precise test is to generate adversarial examples and measure how often they change the prediction; poisoning targets training data, extraction targets confidentiality, and load testing targets availability, none of which probe this specific weakness.

Why A is wrong: This describes a data-poisoning test, which is a real security concern but attacks the training stage, so it does not probe the inference-time perturbation threat in question.

Why B is wrong: Model-extraction and membership-inference testing addresses confidentiality, which is plausible under a security heading, but it targets information leakage rather than perturbation-induced misclassification.

Why C is wrong: Load and stress testing checks availability and performance, so it is tempting as a robustness measure, yet it does nothing to assess whether perturbed inputs can fool the classifier.

Why D is correct: Crafting perturbed inputs and measuring induced misclassification is the direct test for evasion attacks at inference time, which is exactly the threat described.

See more AIGP practice questions, answers explained.

Exam traps in Understanding how to govern AI development

Answers that look right on this material and are not. Each one is a distractor from a different question in the AIGP bank for this domain.

  • Concept drift is a change in the statistical distribution of the input features the system receives, while the relationship between those inputs and the target outcome stays fixed.

    Why it is wrong: This is tempting because it describes a genuine drift type, but it actually defines data drift (also called covariate shift), not concept drift, so it inverts the two concepts being distinguished.

  • Rely on the pre-launch red-team results, since they were obtained on the same product and the underlying base model provider has not announced any change to the foundation model in the interim.

    Why it is wrong: Treating the pre-launch results as still valid is tempting because the product name is unchanged, but fine-tuning and new tool access materially alter the system's behaviour and attack surface, so the prior testing no longer characterises the current system's risks.

  • Real-time alerting that pages the on-call team within minutes whenever request latency or error rates cross a configured operational threshold.

    Why it is wrong: Tempting because it is genuine assurance, but minute-by-minute threshold paging is exactly the always-on monitoring telemetry the audit is meant not to duplicate.

Examworthy is not affiliated with or endorsed by IAPP. Original, blueprint-aligned practice material only.