Claude Certified Architect – Foundations Practice Question 30: Context Editing Tool Results
Claude Certified Architect, Foundations · Test 3 · question 10 of 10
A long-running research agent calls search and file-reading tools dozens of times per task. After many turns, the conversation nears the context window limit mostly because of old, bulky tool results the agent no longer needs. The team wants to keep recent work and the agent's conclusions while freeing space automatically. What should they do?
Show answer and explanation
Answer:
Context editing (a beta feature) includes a tool result clearing strategy that removes old tool results when the conversation passes a configured threshold, while preserving a set number of recent tool uses. It targets exactly this agentic growth pattern. Server-side compaction or summarization is a related option for condensing history.
- A is wrong: caching reduces cost and latency of reused prefixes, but cached tokens still occupy the context window. - B is wrong: blind truncation can remove the user's goal or key conclusions and can break tool_use and tool_result pairing. - D is wrong: max_tokens limits output length; it does not enlarge the context window.
Reference: Context editing