Home / Claude Certified Architect – Foundations / Objective 5.1

Domain 5: Context Management & Reliability · 15% of the exam · Full exam outline

5.1 Manage conversation context to preserve critical information across long interactions

What this objective covers

Progressive summarization risks: condensing numerical values, percentages, dates, and customer-stated expectations into vague summaries. The "lost in the middle" effect: models reliably process information at the beginning and end of long inputs but may omit findings from middle sections. How tool results accumulate in context and consume tokens disproportionately to their relevance (e.g., 40+ fields per order lookup when only 5 are relevant). The importance of passing complete conversation history in subsequent API requests to maintain conversational coherence. Extracting transactional facts (amounts, dates, order numbers, statuses) into a persistent "case facts" block included in each prompt, outside summarized history. Extracting and persisting structured issue data (order IDs, amounts, statuses) into a separate context layer for multi-issue sessions. Trimming verbose tool outputs to only relevant fields before they accumulate in context (e.g., keeping only return-relevant fields from order lookups). Placing key findings summaries at the beginning of aggregated inputs and organizing detailed results with explicit section headers to mitigate position effects. Requiring subagents to include metadata (dates, source locations, methodological context) in structured outputs to support accurate downstream synthesis. Modifying upstream agents to return structured data (key facts, citations, relevance scores) instead of verbose content and reasoning chains when downstream agents have limited context budgets.

Practice questions

Question 1easy

Hours into a session, an agent's history holds dozens of raw tool results from calls made early on that it no longer needs to reread. The team wants the least disruptive, low-risk way to reclaim context. What fits best?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Moving the same tokens elsewhere in the request does not reduce context. The results would still be read on every turn.

Once a tool result is far back in the history the agent rarely needs the raw output again, which makes clearing it one of the safest, lightest forms of compaction.

Expanding stale results adds tokens rather than freeing them, the opposite of what the team needs.

A blank restart frees space but throws away the decisions and progress in the history too. That is far more disruptive than removing only the stale tool output.

Question 2easy

Early in a long Claude Code session you set up a local database; the current work is a CSV export endpoint, and the context window is nearly full. You want the summary that replaces the history to keep the export endpoint decisions. What should you do?

Included in Master: master every domain.See plans