5.4 · Lesson 4 of 4
Maintain and Update Configurations
What you need to know
A Project is a living asset. You maintain its knowledge, and stale or cluttered configurations produce confidently wrong results. Replace outdated files, prune what no longer applies, and assign clear ownership for quality.
Stale knowledge, wrong answers
Claude cannot tell that a file has been superseded. When an old document remains in a Project, answers draw on it with full confidence. Treat configuration as something you actively maintain — on a schedule and after any policy, product, or process change.
Replace and prune
- Replace outdated files instead of stacking the new version next to the old one.
- Prune content that no longer applies — noise and contradictions degrade results.
- Name which document wins when topics overlap.
Own the quality
Name an owner who is accountable for keeping instructions and knowledge current. A three-line maintenance checklist and a review date turn “someone should update this” into an actual habit.
Worked example
A Project has five files; two are outdated or overlapping. Five questions whose answers differ between old and new versions expose which file Claude used. After removing or replacing the stale files and adding an instruction that names the winning document and the owner, the same questions draw only from current material.
Exam traps
Claude will prefer the newest file automatically
Duplicate versions cause inconsistent answers. Remove the outdated one.
Add more files when quality drops
More knowledge is not better if it is noisy or contradictory. Prune first.
Blame the model before checking configuration
When output quality drops, check instructions and knowledge first.
Shared Project with no owner or review date
Ownership and a review schedule are part of the configuration.
Practice scenario
A shared Project starts giving outdated product answers. Two versions of the same guide sit in knowledge. What is the correct fix?
Build exercise
Audit and Refresh a Project's Knowledge
5.4 · Advanced · ~40 min · claude.ai
What you will practise
- Why stale knowledge produces confidently wrong answers.
- How to replace outdated files cleanly.
- How to remove noise that competes with the right source.
- Why the Project owner is accountable for quality.
Run the Domain 5 audit exercise until reruns use current files only and the Project has a named owner and review date.
Open Domain 5 exercisesPath: /learn/claude-associate/exercises/5-configuration-knowledge
Sources
- CCAO-F Exam Guide v1.0 — Domain 5 task statement 5.4 — Maintain and Update Configurations
- evggzzz/ccao-f-guide — task 5.4 Knowledge/Skills — replace, prune, ownership (rewritten)
- Amey-Thakur associate-foundations cheat sheet — knowledge maintenance — distilled into site voice
- docs/ccao-f-implementation-plan.md — Domain 5 lesson map