# CCAR-F Practice: Context management | Your AI Department > 33 free CCAR-F practice questions on context management (15% of the exam), with study notes and explanations. Source: https://youraidept.com/network/ccar-f-practice-questions/context-management CCAR-F domain drill # CCAR-F practice questions: Context management. 33 original questions on Context management, which carries 15% of the Claude Certified Architect – Foundations exam per the published guide. Study notes first, then the questions with an explanation for each. When this domain feels solid, take [the timed CCAR-F practice exam](https://youraidept.com/network/ccar-f-practice-exam) and check the domain breakdown. ## What to know about Context management - The context window is a budget: system prompt, conversation, tool definitions, tool results, and the response all share it. - Context rot: quality falls as the window fills with stale material. Compaction, summarization, and clearing exist to fight it. - Load context when it is needed rather than up front. Give the agent lightweight identifiers (file paths, record ids, URLs) and let it fetch what it needs. - Structured note-taking and memory files as persistence across sessions; subagents as a way to isolate context for a subtask and return only the conclusion. - Prompt caching: what makes a prefix cacheable, why stable system prompts and tool definitions go first, and the cost effect. - Retrieval versus stuffing: when to search and load a slice versus pasting a whole corpus, and how chunking and citations interact. ## Context management questions All domains (33) Context management (33) Context management You want prompt caching to work across many requests that share a large system prompt and tool set. How should the prompt be ordered? - Volatile user content first, then the system prompt and tool definitions, with a cache breakpoint at the very end - Everything inside one user message in a fixed order, so the whole request is cached as one block - Tools first, then the user content, then the system prompt, with a breakpoint after each section - Stable content first (system prompt, tool definitions), a cache breakpoint after it, volatile content last Check answer ### Show answer Answer: Stable content first (system prompt, tool definitions), a cache breakpoint after it, volatile content last. Caching matches prefixes. Stable material goes first so the cached prefix is reused; anything that changes per request goes after it. A breakpoint at the very end after volatile content caches a prefix that no other request will match. Context management A coordinator delegates research to a subagent. What should the coordinator pass, and what should it get back? - The whole conversation so far, and the subagent's complete transcript back, so nothing is lost - A pointer to the coordinator's memory file, and the subagent's full transcript back for review - A complete, self-contained brief with everything the subagent needs, and only the conclusion back - A one-line task title, since the subagent shares the coordinator's context and can look up the rest Check answer ### Show answer Answer: A complete, self-contained brief with everything the subagent needs, and only the conclusion back. Subagents start with a clean context. Give them a complete brief and take back the result, not the working, to keep the coordinator's window lean. Passing the whole conversation both ways defeats the purpose of delegation; a pointer to a memory file leaves the subagent without the task. Context management What is 'context rot'? - A caching bug in which a stale cached prefix is served after the system prompt has changed - The gradual loss of tool results when compaction summarizes older turns - The decline in response quality as the window fills with stale or irrelevant content - The drift in a model's behavior over weeks as the provider updates it Check answer ### Show answer Answer: The decline in response quality as the window fills with stale or irrelevant content. Recognizing context rot is why compaction and clearing exist. It is about what is in the window now, not a caching fault or model updates; compaction is the cure, not the cause. Context management An agent needs occasional access to a 500-page manual. Best approach? - Load the whole manual into every prompt and rely on prompt caching to keep it cheap - Summarize it once into a few pages and give the agent only the summary - Index it and retrieve relevant sections on demand, giving the model identifiers it can fetch - Split it into ten chunks and run a subagent per chunk on every question Check answer ### Show answer Answer: Index it and retrieve relevant sections on demand, giving the model identifiers it can fetch. Just-in-time retrieval keeps the window lean and accurate. Caching makes the full manual cheaper but not free, and 500 pages of mostly irrelevant text still degrades attention; a one-time summary loses the details the occasional question needs. Context management Which content should sit at the start of the prompt for prompt caching to help? - The conversation history, since it is the largest part of the request - The user's latest question, so the model reads it before the long material - The stable system prompt and tool definitions - The most recent tool results, since those are reused across turns Check answer ### Show answer Answer: The stable system prompt and tool definitions. Cache hits depend on a stable prefix. Tool results and the latest question change every turn, so placing them first breaks the prefix for every request. Context management A long-running agent needs to remember decisions across sessions. Which mechanism fits? - A longer system prompt that lists the decisions made so far - A larger max_tokens value so the agent can restate all of its decisions in each response - Prompt caching on the previous session's transcript so it is cheap to include - A memory file or structured notes the agent reads at start and updates as it works Check answer ### Show answer Answer: A memory file or structured notes the agent reads at start and updates as it works. Persistence across sessions needs an explicit store the agent maintains. Caching a transcript keeps it cheap to send but does not curate it, and the cache expires; a system prompt edited by hand is memory the agent cannot update. Context management Why hand a subagent a task instead of doing everything in one context? - The subagent's working context stays separate and only its conclusion returns, preserving the main window - Subagents can call tools the main session is not allowed to use - Subagents run on a different model, so the main session's model stays available - Subagents share the main session's context, so they start with full knowledge of the task Check answer ### Show answer Answer: The subagent's working context stays separate and only its conclusion returns, preserving the main window. Context isolation is the main benefit of delegation. Subagents do not share the main context, which is the point; the model and tool set can be configured but are not why you delegate. Context management A prompt includes the full history of a two-hour support chat. Most of it is resolved. What should you do? - Summarize the resolved parts and keep the open issue verbatim - Keep the last twenty messages and drop everything before them - Drop the history and restate the open issue in a fresh prompt - Keep the full history, since the model may need context from resolved issues Check answer ### Show answer Answer: Summarize the resolved parts and keep the open issue verbatim. Summarize the settled, keep the live. Keeping everything wastes the window on closed threads; a fixed tail of twenty messages may cut through the middle of the open issue. Context management Which is a symptom that a context window is being wasted? - Responses that arrive faster than the previous session's - Frequent cache hits on the system prompt across many consecutive requests from the same client - Large tool results the model never uses and repeated boilerplate in every turn - Short prompts that leave most of the window empty Check answer ### Show answer Answer: Large tool results the model never uses and repeated boilerplate in every turn. Unused bulk and repetition are the usual waste. Cache hits and fast responses are signs of a healthy prompt; empty headroom is not waste. Context management What is the trade-off of aggressive summarization in an agent loop? - Summaries make later turns slower because the model must reconstruct the details - Headroom and speed at the cost of detail, so keep exact values and identifiers later steps need - Summaries break tool use because tool_result blocks cannot be summarized - Summaries are safe as long as the summary is written by a larger model Check answer ### Show answer Answer: Headroom and speed at the cost of detail, so keep exact values and identifiers later steps need. Summaries lose detail; preserve what downstream steps depend on. Later turns are usually faster with a shorter context, not slower, and tool results can be summarized like anything else. Context management Which information should be kept verbatim through compaction? - The earliest turns, since they set up the task - Resolved errors and their stack traces, in case they recur - Identifiers, exact values, and the current task definition - The greetings and pleasantries, since tone carries across turns Check answer ### Show answer Answer: Identifiers, exact values, and the current task definition. Precision-critical items survive; chatter does not. The earliest turns matter only for the task definition, which is what is kept; resolved errors are exactly what a summary can compress. Context management A team wants to cut cost on a chat product with a long, stable system prompt and many short user turns. First lever? - Prompt caching on the system prompt and tool definitions - Batching user turns so several are answered in one request - Switching to a smaller model for every turn after the first - Trimming the system prompt to a few lines so every request is smaller Check answer ### Show answer Answer: Prompt caching on the system prompt and tool definitions. Caching the stable prefix is the cheapest win for that shape. Trimming the system prompt may cost quality; batching turns breaks the chat experience; a smaller model changes the product. Context management What does 'give the agent lightweight identifiers' mean in context engineering? - Pass file paths, record ids, and URLs so the agent can fetch details when needed instead of front-loading everything - Replace user names with anonymous ids before content reaches the model - Use short variable and file names in the code the agent works on so tokens are saved - Give each tool a short alias so the tool list occupies fewer tokens Check answer ### Show answer Answer: Pass file paths, record ids, and URLs so the agent can fetch details when needed instead of front-loading everything. Identifiers enable on-demand retrieval. Short names and tool aliases save a handful of tokens; anonymization is a privacy measure, not a context strategy. Context management How should an architect decide the context budget for a step in a workflow? - From what the step must read and produce, leaving headroom for tool results and reasoning - Split the total window evenly across the steps in the workflow - Reuse the budget from the last project that used the same model - Use the model's maximum on every step so no step runs out of room Check answer ### Show answer Answer: From what the step must read and produce, leaving headroom for tool results and reasoning. Budget from the step's real needs, with headroom. An even split starves the heavy steps and pads the light ones; the maximum on every step invites bloat and cost. Context management A prompt is 150k tokens and quality is uneven. What is the first question to ask? - Whether a newer model with a larger context window would handle the same 150k tokens more evenly - Whether raising max_tokens would give the model more room to work through the material - How much of that context the task needs, and whether retrieval or summarization could replace the bulk - Whether the prompt has a clear persona so the model knows how to weigh the material Check answer ### Show answer Answer: How much of that context the task needs, and whether retrieval or summarization could replace the bulk. Budget the context from what the task needs; retrieval or summarization usually replaces the bulk. A larger window carries the same irrelevant material, and max_tokens affects output, not input. Context management What goes in a memory file that an agent maintains across sessions? - Every tool result, so the agent can avoid repeating calls it already made - Decisions, open items, and pointers to sources, kept short and current - Full transcripts of each session so nothing is lost between runs - Credentials and endpoints the agent needs, so it can start without setup Check answer ### Show answer Answer: Decisions, open items, and pointers to sources, kept short and current. Durable, compact state. Transcripts and tool results bloat the file, and credentials belong in secure configuration. Context management Which practice supports prompt caching across many users of the same app? - Randomize the order of instructions so no single prefix dominates the cache - Disable the system prompt and pass all instructions in the first user message - Put each user's profile at the start of the system prompt so it is cached per user - A shared stable prefix, with user-specific content after the cache breakpoint Check answer ### Show answer Answer: A shared stable prefix, with user-specific content after the cache breakpoint. Shared prefix first, user content after. Putting the profile first makes every user's prefix different, so nothing is shared. Context management How should long tool outputs be handled in an agent loop? - Kept in full, since dropping any part of a tool result risks losing something the task needs - Moved into the system prompt so they are cached and do not consume the conversation budget - Deleted after the turn that used them, since the model has already acted on them - Truncated or summarized to the essentials, keeping identifiers so details can be re-fetched Check answer ### Show answer Answer: Truncated or summarized to the essentials, keeping identifiers so details can be re-fetched. Keep the essentials and the pointers. Full outputs crowd out later reasoning, and deleting them outright loses details a later step may need. Context management What is a reasonable trigger for compaction in a long session? - Approaching the context budget or finishing a subtask - Only when a tool call fails, since errors usually mean the context is polluted - Only when the user asks, since the model cannot judge when to compact - After every message, so the window stays as small as possible Check answer ### Show answer Answer: Approaching the context budget or finishing a subtask. Compact at natural boundaries or near limits. Compacting every message loses detail constantly for no benefit. Context management Why can a smaller, curated context beat a larger one? - Less irrelevant material means better attention to what matters, alongside lower cost - The claim does not hold; more context is better as long as it fits inside the model's window - Models are trained on short prompts, so long prompts fall outside the distribution - Smaller contexts are cheaper, and the cost saving is the only real difference Check answer ### Show answer Answer: Less irrelevant material means better attention to what matters, alongside lower cost. Relevance beats volume: irrelevant material competes for attention. Cost is a bonus, not the only difference. Context management An agent must reference a style guide on every task. Where does it belong? - Pasted into each user message so it is always the most recent input - Summarized to one line in the system prompt to save tokens - In the stable prefix so it caches, or loaded once per session - Returned through a tool result on the first turn of each task Check answer ### Show answer Answer: In the stable prefix so it caches, or loaded once per session. Stable reference content lives in the cached prefix. Pasting it into each message duplicates it and defeats caching. Context management What should be true of the summary you carry forward after compaction? - It is as short as possible, ideally one sentence describing the goal - It keeps the full tool results, since those are the hardest to reconstruct - It restates the system prompt so the instructions survive the reset - It preserves task definition, decisions, exact values, and next steps Check answer ### Show answer Answer: It preserves task definition, decisions, exact values, and next steps. Preserve state, drop chatter. The system prompt persists on its own, and a one-line goal loses the decisions and values later steps need. Context management Which is a symptom of context overflow rather than a bad prompt? - The model asks for information that was never provided in the conversation - Late-conversation instructions ignored and earlier details contradicted - Answers that are shorter than usual and skip the requested formatting - Slower responses and higher cost per turn as the conversation grows Check answer ### Show answer Answer: Late-conversation instructions ignored and earlier details contradicted. Overflow shows as lost or contradicted details. Asking for missing information is a sign of too little context, and slower responses are a cost symptom, not a quality one. Context management How do subagents relate to context budgets? - They share the coordinator's budget, so each subagent reduces what is left for the rest - Each has its own budget, so heavy subtasks do not consume the coordinator's window - They have no budget of their own and rely on the coordinator to compact for them - They double the coordinator's window, since each subagent adds its own context to it Check answer ### Show answer Answer: Each has its own budget, so heavy subtasks do not consume the coordinator's window. Separate budgets per subagent; only the returned summary lands in the coordinator's window. Context management An agent's context contains three copies of the same document from repeated tool calls. What is the fix? - Tell the model in the system prompt to ignore repeated documents and use the first copy - Increase the context window so the duplicates fit alongside the rest of the task - Deduplicate tool results and cache the document by identifier so it loads once - Add a compaction step after every tool call so older copies are summarized away Check answer ### Show answer Answer: Deduplicate tool results and cache the document by identifier so it loads once. Deduplicate and cache. Asking the model to ignore copies still pays for them, and compacting every call loses detail. Context management What is the value of a 'scratchpad' or notes file for a long task? - It gives the model a place to write longer prompts for itself on the next turn - It lets tools run faster because their results are written to disk instead of context - Durable working memory outside the window, so progress survives compaction and restarts - It replaces the need for compaction, since the window stops growing once notes are kept Check answer ### Show answer Answer: Durable working memory outside the window, so progress survives compaction and restarts. External working memory that survives compaction. Notes do not stop the window from growing; they make compaction safe. Context management Which order helps prompt caching for a multi-tenant assistant with shared instructions? - Shared instructions and tools first, tenant data after the breakpoint - Tenant data in the system prompt and shared instructions in the user turn - Tenant data first so each tenant's cache is warm from the first token - Alternate shared and tenant content so both are covered by the cache Check answer ### Show answer Answer: Shared instructions and tools first, tenant data after the breakpoint. Shared prefix, tenant suffix. Tenant data first makes the prefix unique per tenant, so nothing is shared. Context management A workflow step needs only two fields from a large upstream result. Best practice? - Merge the step into the upstream one so no data has to be passed between them - Pass the whole upstream result so the step has the full context available if it turns out to need more - Extract the two fields and pass only those, keeping an identifier to fetch more if needed - Summarize the upstream result in prose and pass the summary to the step Check answer ### Show answer Answer: Extract the two fields and pass only those, keeping an identifier to fetch more if needed. Pass what the step needs plus a pointer. A prose summary may drop the exact values the step depends on. Context management What does compaction risk if done carelessly? - Slower responses, since the model must re-read the summary before it can act - Dropping exact values, identifiers, or the current task definition that later steps need - More tool calls, since the model re-fetches everything the summary mentions - Cache misses on the next turn, since the compacted conversation prefix no longer matches the cached one Check answer ### Show answer Answer: Dropping exact values, identifiers, or the current task definition that later steps need. Preserve precision-critical state. Cache misses are a real but minor cost next to losing the task definition. Context management An agent must consult a policy document on every decision. Which approach balances cost and accuracy? - Keep it in the cached prefix, or retrieve the relevant section per decision - Paste the full document into each user turn so it is always the freshest input - Summarize it once at session start and rely on the summary for every decision - Load it through a tool call on each decision so it never occupies the prefix Check answer ### Show answer Answer: Keep it in the cached prefix, or retrieve the relevant section per decision. Cached prefix or targeted retrieval. A one-time summary loses the detail decisions depend on, and pasting per turn pays full price every time. Context management Which is a symptom of too little context rather than too much? - Responses slow down and cost per turn rises as the conversation grows longer - Cache misses increase because the shared prompt prefix changes from one turn to the next as history grows - The model asks for information it should have, or guesses at details that were never provided - Instructions from early in the conversation are contradicted late in the conversation Check answer ### Show answer Answer: The model asks for information it should have, or guesses at details that were never provided. Missing inputs show as guessing or asking. Contradictions late in a conversation are the overflow symptom. Context management How should you size retrieval chunks for a technical manual? - As large as the context window allows, so each retrieved chunk carries the full surrounding material of the manual with it - One sentence each, so retrieval can match the exact line the question is asking about - Whole chapters, since a manual's own structure already groups the related material together and keeps procedures whole - Large enough to hold one complete idea, like a procedure or section, and small enough to keep only relevant material in context Check answer ### Show answer Answer: Large enough to hold one complete idea, like a procedure or section, and small enough to keep only relevant material in context. Complete ideas, minimal noise. Single sentences lose the procedure they belong to, and chapters carry mostly irrelevant material. Context management A coordinator agent's window is filling with subagent chatter. What is the structural fix? - Have subagents return only structured results and keep their transcripts out of the coordinator - Compact the coordinator's context after each subagent returns so the accumulated chatter is summarized away - Disable logging in the subagents so their tool output is not echoed back - Use fewer subagents so less of their output reaches the coordinator's window Check answer ### Show answer Answer: Have subagents return only structured results and keep their transcripts out of the coordinator. Return results, not transcripts. Compacting after the fact pays for the chatter first; fewer subagents reduces capability rather than fixing the leak. ## Next - [Timed CCAR-F practice exam](https://youraidept.com/network/ccar-f-practice-exam): 60 questions in 120 minutes, scored against the 720 pass mark. - [All CCAR-F practice questions](https://youraidept.com/network/ccar-f-practice-questions) with a domain filter. - [The CCAR-F exam page](https://youraidept.com/network/ccar-f): format, weights, registration, study path. ### Other CCAR-F domains - [Agentic architecture (52 questions)](https://youraidept.com/network/ccar-f-practice-questions/agentic-architecture) - [Claude Code workflows (40 questions)](https://youraidept.com/network/ccar-f-practice-questions/claude-code-workflows) - [Prompt engineering (40 questions)](https://youraidept.com/network/ccar-f-practice-questions/prompt-engineering) - [Tool design and MCP (35 questions)](https://youraidept.com/network/ccar-f-practice-questions/tool-design-and-mcp) ## FAQ ### How much of the CCAR-F exam is context management? + 15% of the marks, per the published CCAR-F exam guide. The full domain list with weights is on the CCAR-F exam page. ### Are these real CCAR-F exam questions? + No. They are 33 original scenario questions written from the blueprint for this domain. Reproducing exam content would violate the candidate agreement. ### How should I study context management for CCAR-F? + Read the domain notes on this page, answer the questions with explanations hidden, then take the timed CCAR-F practice exam and check the per-domain breakdown for this domain. ## Who wrote this ### [Matei Olaru](https://youraidept.com/about/matei-olaru) CEO, Your AI Department Former public-company CEO, corporate attorney, and World Bank consultant. Runs the YAID Network and the partner relationship with Anthropic. ### [Michael Greenberg](https://youraidept.com/about/michael-greenberg) AI Product Lead, Your AI Department AI at Google, Meta, and Samsung. Six patents. Leads member support and the certification prep guidance. Your AI Department is a registered Claude Partner Network company. Our members sit these exams under our partner standing. Facts on this page were last checked on October 15, 2026. ## Ready to sit CCAR-F for real? Registration needs a Claude Partner Network organization. [YAID Network](https://youraidept.com/network) members register under our partner standing. $149 per quarter, exam fee separate. [Apply to join YAID ↗](https://youraidept.com/network/apply?ref=drill)[How registration works →](https://youraidept.com/network/register-for-claude-certification)