The supplied exam source marks D . Claude prompt caching is designed for repeated prompt prefixes, not semantic caching of generated answers. High-value cache candidates include stable system prompts, long instructions, tool definitions, shared background documents, repeated examples, and the previously accumulated prefix of a multi-turn conversation.
Anthropic explains that prompt caching reuses a matching prompt prefix and can substantially reduce processing time and input-token cost on subsequent requests. The cache operates across the request structure—tools, system content, and messages up to the relevant cache boundary. It is particularly useful for prompts with many examples, large repeated context, repetitive instructions, and long multi-turn conversations.
B describes response caching , which is a separate application-level technique and is not what Anthropic's prompt caching feature does. C targets the portion that usually changes most, making it a poor general cache boundary. A is incorrect because multi-turn workloads are a major prompt-caching use case.
Therefore, maximize reusable stable prefixes and place changing request-specific content after them where practical.
Relevant Claude Developer topics: Claude API Mechanics, prompt caching, cache prefixes, token-cost optimization, static context, system prompts, multi-turn conversations, and API efficiency .
===============
