Home / Claude Certified Architect – Foundations / Objective 3.1

Domain 3: Claude Code Configuration & Workflows · 20% of the exam · Full exam outline

3.1 Configure CLAUDE.md files with appropriate hierarchy, scoping, and modular organization

What this objective covers

The CLAUDE.md configuration hierarchy: user-level (~/.claude/CLAUDE.md), project-level (.claude/CLAUDE.md or root CLAUDE.md), and directory-level (subdirectory CLAUDE.md files). That user-level settings apply only to that user—instructions in ~/.claude/CLAUDE.md are not shared with teammates via version control. The @import syntax for referencing external files to keep CLAUDE.md modular (e.g., importing specific standards files relevant to each package). .claude/rules/ directory for organizing topic-specific rule files as an alternative to a monolithic CLAUDE.md. Diagnosing configuration hierarchy issues (e.g., a new team member not receiving instructions because they're in user-level rather than project-level configuration). Using @import to selectively include relevant standards files in each package's CLAUDE.md based on maintainer domain knowledge. Splitting large CLAUDE.md files into focused topic-specific files in .claude/rules/ (e.g., testing.md, api-conventions.md, deployment.md). Using the /memory command to verify which memory files are loaded and diagnose inconsistent behavior across sessions.

Practice questions

Question 1easy

A developer starts Claude Code at the root of a monorepo. packages/billing/CLAUDE.md holds billing conventions, but right after launch /context does not list it under Memory files. What explains this?

Included in Sample: sample every domain.See plans

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

That variable is real, but it governs directories added with --add-dir, which sit outside the working directory. A package inside the repository does not need it.

CLAUDE.md files do not replace one another; discovered files are concatenated. A root file could not suppress the billing file.

CLAUDE.local.md is the personal, gitignored variant. Its name has nothing to do with whether a nested file is discovered.

Only files at and above the launch directory load at startup. A CLAUDE.md below it joins the conversation once Claude reads, writes or edits a file in that subdirectory, so its absence from the launch list is expected.

Question 2easy

A tech lead wrote the team's naming conventions in ~/.claude/CLAUDE.md on her own laptop. A new hire clones the repository, and Claude ignores those conventions in his sessions. What is the cause?

Included in Master: master every domain.See plans