CCAR-F Agentic Architecture and Orchestration Practice Question
An organization is deploying an agentic system that must maintain long-running conversations over several days, involving hundreds of tool calls. What is the most critical architectural consideration for managing the 'messages' array to prevent exceeding Claude's context window?
⚠ Common exam trap
Candidates often assume models have infinite memory or that simply increasing context windows is the solution, failing to implement active management like pruning or summarization for long-running sessions.
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
✓
Implement a context management strategy like summarization or message pruning
Long-running agentic conversations can quickly exceed the context window of even large models like Claude 3.5 Sonnet. Architects must implement context management strategies, such as summarizing old turns or using a sliding window approach, to keep the most relevant information within the prompt while removing or distilling older, less relevant interactions to maintain performance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Clear the message history every time a tool returns a successful result
Why it's wrong here
Clearing the history after every successful tool call would cause the model to lose all context of its previous actions and the original user goal. Agentic behavior relies on the continuity of the conversation to understand what has been tried, what the results were, and what the next logical step should be.
- ✓
Implement a context management strategy like summarization or message pruning
Why this is correct
To handle long-running agents, architects must actively manage the message history. This involves summarizing earlier parts of the conversation into a concise 'memory' block and pruning old tool-use blocks that are no longer needed for the current reasoning step, ensuring the model stays within its token limits while retaining key info.
- ✗
Always use the 'system' role to store the entire history of tool outputs
Why it's wrong here
Storing history in the system prompt is inefficient and does not solve the context window problem, as those tokens still count toward the total limit. Furthermore, tool results are semantically intended for the 'user' role in the Anthropic API structure, and misplacing them can degrade the model's ability to follow the tool-use protocol.
- ✗
Switch to a smaller model version when the context window reaches 50% capacity
Why it's wrong here
Switching to a smaller model usually results in a smaller context window, which would worsen the problem. Additionally, smaller models may lack the reasoning capability required to handle the complex history that filled the context in the first place. Context management should focus on data density rather than model switching.
About these practice questions
One of 271 original CCAR-F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCAR-F practice question is part of Courseiva's free Anthropic 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 CCAR-F exam.