Domain 7 — Claude Code (3.1%)

3.1% of the exam, roughly 2 questions. Deliberately light — this is the Architect exam's territory. Learn the shape, not the depth.

7.1 What lives where

The one conceptual point that carries marks: CLAUDE.md is context, not configuration. It shapes behaviour and guarantees nothing. A rule that must always hold belongs in permissions.deny or a hook.

7.2 Interaction modes

Permission modes set the approval baseline: default prompts on first use of each tool; plan explores read-only and produces a reviewable plan before any edit; acceptEdits auto-accepts file edits; bypassPermissions skips prompts and belongs only in isolated environments. Plan mode before a large refactor is the habit the exam rewards.

7.3 Running it programmatically

claude -p "Review this diff for security issues" \
  --output-format json \
  --allowedTools "Read,Grep" \
  --bare

-p runs non-interactively; --output-format gives text, json (result plus session ID and usage) or stream-json; --bare skips auto-discovery of hooks, skills, plugins, MCP servers and CLAUDE.md, which is what makes a CI run reproducible across machines. Exit code 0 on success, non-zero on failure.

← Previous: Domain 6 — Security and Safety  |  Next: Domain 8 — Eval, Testing and Debugging →