Claude Certified Architect – Foundations Practice Question 10: Cache Breakpoint Placement
Claude Certified Architect, Foundations · Test 1 · question 10 of 10
A chat application sends the same large request prefix on every turn: 40 tool definitions, a 12,000-token system prompt with policies, and then the growing conversation. Cache hit rates are low. Engineers find that a timestamp is inserted at the top of the system prompt on each request, and that the cache_control marker is placed on the latest user message only. Which fix gives the best cache reuse?
Show answer and explanation
Answer:
C is correct. The cache prefix is built in the order tools, then system, then messages, and it matches only if everything up to the breakpoint is identical. A timestamp at the top of the system prompt changes the prefix on every request, so nothing after it can hit the cache. Move volatile content (timestamp, per-request data) after the stable content, and place cache_control breakpoints at the end of stable sections, such as the end of the system prompt, plus one on the latest message so the growing conversation is cached too.
A is wrong because modifying tool definitions invalidates the entire cache, tools included, so it makes things worse. B is wrong because a large stable prefix is exactly where caching saves the most cost and latency. D is wrong because a breakpoint caches only the prefix up to and including that block, so marking the first tool would not cover the system prompt or messages.
Reference: Prompt caching - Claude Platform Docs