AI0-001 AI Security Practice Question
A company deploys an LLM chatbot that has access to a database of customer orders. They want to prevent the LLM from revealing order details unless the user is authenticated as the owner. Which security control should be implemented?
⚠ Common exam trap
The AI0-001 exam often tests the misconception that output filtering or input sanitization alone can prevent data leakage, when in fact they fail to address the root cause—lack of authentication and authorization at the API or model access layer.
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
✓
Access controls on the model and API
Access controls on the model and API (Option D) are the correct security control because they enforce authentication and authorization at the API gateway or model endpoint level, ensuring that only the authenticated owner can query their own order details. This prevents unauthorized users from invoking the LLM to retrieve sensitive data, regardless of the prompt content. Without such access controls, the LLM would have no inherent mechanism to verify user identity before processing requests.
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
Why it's wrong here
Output filtering inspects responses for sensitive patterns but cannot determine whether the requester owns the order, so legitimate-looking output still leaks data. It is tempting because filtering catches accidental disclosure, and it would be correct where the risk is model-generated sensitive content rather than per-user authorisation of database records.
- ✗
Rate limiting
Why it's wrong here
Rate limiting caps request volume per client but grants no identity check, so any authenticated or anonymous user could still query another customer's order details. It is tempting because throttling mitigates abuse and denial-of-service, and it would be the right control where the concern is excessive request frequency rather than data ownership.
- ✗
Input validation and sanitization
Why it's wrong here
Sanitising inputs blocks injection payloads but cannot enforce per-user authorisation, so an authenticated attacker could still craft prompts that retrieve other customers' orders. It is tempting because input validation is a standard defence against prompt injection, and it would be correct where the risk is malicious characters rather than unauthorised data access.
- ✓
Access controls on the model and API
Why this is correct
Enforcing access controls on the model and API authenticates each caller and authorises order lookups against ownership, so the LLM only returns details the requesting user legitimately owns. This blocks unauthorised disclosure at the interface rather than relying on prompt instructions.
About these practice questions
This AI0-001 question is part of Courseiva's 962-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.