AI0-001 AI Security Practice Question
An organization wants to detect if someone is trying to steal their proprietary machine learning model by querying its API. Which monitoring technique is MOST effective?
⚠ Common exam trap
Watch out — candidates often confuse generic security controls (rate limiting, input validation) with the specific detection technique needed for model extraction, overlooking that extraction attacks use legitimate, well-formed queries in a systematic pattern.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Monitoring for anomalous query patterns, such as high volume or systematic variations
Model extraction attacks rely on systematically querying the API to reconstruct the model's decision boundary. Monitoring for anomalous query patterns—such as high request volume, uniform input distributions, or systematic variations (e.g., grid-like sampling of feature space)—directly detects the behavioral signature of extraction attempts, unlike passive controls that do not address the attack vector.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Output filtering to remove sensitive information from responses
Why it's wrong here
Output filtering strips sensitive values from responses but does nothing to reveal that someone is systematically querying the API to reconstruct the model; the extraction attempt continues unnoticed. It is tempting because filtering is the right control when responses themselves leak confidential data such as personal information, whereas here the concern is the querying pattern, not response content.
- ✗
Rate limiting on the number of API requests per user
Why it's wrong here
Rate limiting caps request volume but cannot distinguish a legitimate high-volume client from an attacker probing the model; it throttles rather than detects, and slow extraction below the threshold is invisible. It is tempting because rate limiting genuinely mitigates brute-force and denial-of-service abuse, making it the correct choice when the requirement is protecting availability, not identifying model theft.
- ✓
Monitoring for anomalous query patterns, such as high volume or systematic variations
Why this is correct
Monitoring anomalous query patterns detects model extraction, where attackers probe an API with systematic input variations to reconstruct decision boundaries. High-volume or structured querying satisfies the scenario's requirement to identify theft attempts against the proprietary model, since legitimate users rarely exhibit such repetitive, exhaustive probing behaviour.
- ✗
Input validation to reject malformed requests
Why it's wrong here
Input validation only rejects syntactically malformed requests, so a thief submitting well-formed queries passes straight through and the extraction attempt goes undetected. It is tempting because validation hardens the API against injection and fuzzing attacks, and would be the right control when the goal is preventing malformed or hostile payloads rather than spotting systematic model-extraction patterns.
About these practice questions
One of 962 original AI0-001 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AI0-001 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI0-001 exam.