Home / Claude Certified Developer – Foundations / Objective 3.1

Domain 3: Claude Code · 3% of the exam · Full exam outline

3.1 Claude Code Operation

What this objective covers · 3% of the exam

Claude Code core components (Rules, Skills, Commands, Agents, Agent Memory), features (session management, built-in and custom slash commands, headless mode, streaming mode, auto-mode), the CLAUDE.md hierarchy, repository initialization, and settings.json configuration.

Practice questions

Question 1easy

A developer creates .claude/rules/frontend/components.md with no YAML frontmatter, expecting it to load only when Claude works on frontend files. What actually happens?

Included in Sample: sample every domain.See plans

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

Scoping comes from a paths glob in the frontmatter, not the folder; without paths the rule loads every session.

Rules files without paths do load, at launch.

Subfolders in .claude/rules are only for organization; they do not scope anything.

Rules files are not invoked by name; that is Skill behavior.

Question 2easy

A developer wants to allow a few extra commands for their own use in one project without affecting teammates or committing the change. Where should the setting go?

Included in Sample: sample every domain.See plans

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

The project file is committed, so the change would apply to everyone who clones the repo.

User settings apply to every project on the machine, not just this one.

Local project settings are personal overrides for one project and are git-ignored automatically.

Enterprise managed settings are set by admins for the whole organization.