LLM Application Security practice test
Model output as untrusted input, rendering and exfiltration channels, retrieval with real access control, vector and embedding weaknesses, knowledge-base poisoning, sensitive data in prompts and logs, guardrails and their honest evaluation, misinformation, and denial of wallet. The pool for this topic holds 11 easy, 16 medium and 13 hard items. Each answer comes with its reasoning and a link to the question or concept page it was drawn from.
Sample items with answers
Whatever reaches the context, including attacker-controlled documents, can influence what the model writes. If that output goes into HTML, SQL, a shell or a file path without validation and encoding, the attacker gets a classic injection by way of the model. OWASP lists this as LLM05.
If injected instructions make the model write an image whose URL contains conversation data, the browser requests it automatically and the attacker's server logs the data. Several assistants were vulnerable to this. Blocking images from non-allowlisted hosts closes the channel.
After the test
Choosing from options is easier than reasoning it out in front of a panel. These pages make you reason it out: