CCAR-F objective 5.4 · Domain 5 · 15% of the exam
Codebase Exploration and Context Degradation
One constraint generates the rest: the window fills fast and performance falls as it does. Exploring a large codebase is the classic way to fill it, and the fix is delegating the exploration so only the findings come back, since the subagent reads in its own window and the main context grows by a summary rather than a transcript. Scoping the request is the other acceptable fix, so a well-formed stem says which constraint decides. Worth knowing about compaction: it replaces older messages with a summary, and the project-root instruction file is re-injected on every request while a nested one is not.
5 questions · answers and explanations shown as you go · free, no sign-up
The rest of domain 5: Context Management and Reliability
This domain is 15% of a scored form, about 10 of the 65 questions, spread across 6 objectives. Drill the whole domain or pick another objective below.
One objective is a narrow slice. A full-length timed mock is what tells you whether the whole thing holds together.
Sit a timed mock →