CLAUDE.md Hierarchy, Scoping, and Modular Organisation: Practice Questions — Claude Code Configuration & Workflows (Claude Certified Architect)

Practice Questions on CLAUDE.md Hierarchy, Scoping, and Modular Organisation

These multiple-choice questions focus on configuring CLAUDE.md files for effective project memory and instruction management within Claude Code workflows. Understanding hierarchy, scoping, and modular organisation is essential for designing maintainable and scalable agentic applications.

1. Which of the following best describes the purpose of a hierarchical CLAUDE.md file structure in a project?

   • A. To store all instructions in a single file for simplicity
   • B. To separate instructions by scope and enable modular reuse
   • C. To duplicate instructions across files for redundancy
   • D. To avoid using subdirectories and keep all files flat

   Correct answer: B

   Explanation: Hierarchical CLAUDE.md files separate instructions by scope (e.g., global, module-specific) enabling modular reuse and easier maintenance.

2. When scoping instructions within CLAUDE.md files, which practice helps avoid unintended overrides?

   • A. Using global instructions only at the root level
   • B. Placing all instructions in the deepest subdirectory
   • C. Defining path-specific instructions with clear scope boundaries
   • D. Mixing unrelated instructions in the same file

   Correct answer: C

   Explanation: Defining path-specific instructions with clear scope boundaries prevents conflicts and unintended overrides in modular organisation.

3. What is a recommended approach to modular organisation of CLAUDE.md files in a large project?

   • A. Create one monolithic CLAUDE.md file for the entire project
   • B. Split CLAUDE.md files by functional components or features
   • C. Use random file names unrelated to their content
   • D. Avoid using CLAUDE.md files and rely on inline prompts

   Correct answer: B

   Explanation: Splitting CLAUDE.md files by functional components or features supports modularity and easier updates.

4. How should custom commands or skills be organised within the CLAUDE.md hierarchy?

   • A. Embed all custom commands in the root CLAUDE.md file
   • B. Place custom commands in dedicated subfolders with their own CLAUDE.md files
   • C. Avoid custom commands to reduce complexity
   • D. Store commands in unrelated folders to keep them hidden

   Correct answer: B

   Explanation: Organising custom commands in dedicated subfolders with their own CLAUDE.md files improves clarity and modularity.

5. Which of the following is a key benefit of applying path-specific conventions in CLAUDE.md files?

   • A. It increases the risk of conflicting instructions
   • B. It allows different parts of the project to have tailored context and behaviour
   • C. It forces all agents to use the same instructions regardless of context
   • D. It eliminates the need for project memory files

   Correct answer: B

   Explanation: Path-specific conventions enable tailored context and behaviour for different project areas, enhancing flexibility.

6. In the context of CLAUDE.md modular organisation, what is the best practice when updating instructions shared across multiple modules?

   • A. Update each module’s CLAUDE.md file separately
   • B. Maintain shared instructions in a common parent CLAUDE.md file
   • C. Copy and paste instructions into each module’s file
   • D. Avoid updating shared instructions to prevent errors

   Correct answer: B

   Explanation: Keeping shared instructions in a common parent file ensures consistency and reduces duplication.

7. Why is iterative refinement important when organising CLAUDE.md files hierarchically?

   • A. It allows for continuous improvement and adaptation of instructions as project needs evolve
   • B. It prevents any changes once the initial structure is set
   • C. It discourages modular organisation
   • D. It requires rewriting all instructions from scratch frequently

   Correct answer: A

   Explanation: Iterative refinement supports adapting the CLAUDE.md hierarchy and instructions to changing project requirements.

More in this topic

Iterative Refinement Techniques — Claude Code Configuration & Workflows (Claude Certified Architect)CLAUDE.md Hierarchy, Scoping, and Modular Organisation: Common Mistakes — Claude Code Configuration & Workflows (Claude Certified Architect)Path-Specific Rules for Conditional Convention Loading: Practice Questions — Claude Code Configuration & Workflows (Claude Certified Architect)CLAUDE.md Hierarchy, Scoping, and Modular Organisation: Quick Reference — Claude Code Configuration & Workflows (Claude Certified Architect)Custom Slash Commands and Skills — Claude Code Configuration & Workflows (Claude Certified Architect)CLAUDE.md Hierarchy, Scoping, and Modular Organisation — Claude Code Configuration & Workflows (Claude Certified Architect)CI/CD Integration — Claude Code Configuration & Workflows (Claude Certified Architect)Claude Code Configuration & Workflows — Claude Certified Architect - FoundationPath-Specific Rules for Conditional Convention Loading — Claude Code Configuration & Workflows (Claude Certified Architect)Path-Specific Rules for Conditional Convention Loading: Quick Reference — Claude Code Configuration & Workflows (Claude Certified Architect)Plan Mode vs Direct Execution — Claude Code Configuration & Workflows (Claude Certified Architect)CLAUDE.md Hierarchy, Scoping, and Modular Organisation: Worked Example — Claude Code Configuration & Workflows (Claude Certified Architect)Path-Specific Rules for Conditional Convention Loading: Worked Example — Claude Code Configuration & Workflows (Claude Certified Architect)Path-Specific Rules for Conditional Convention Loading: Common Mistakes — Claude Code Configuration & Workflows (Claude Certified Architect)