Can you sit the AI-Assisted Development Certification today?

You have just started a session in a repository you have never worked in. Which first move is most likely to pay for itself?

• APaste in the file you think is broken, so Claude has it immediately
• BAsk for the biggest item on your backlog, to find out what the tool can do
• CAsk what the test command is and whether it currently passes
• DRun `/doctor` to confirm the model and the installation are right

A hook works on your machine and does nothing on a colleague's, after they have pulled your changes. Running `/hooks` on their machine shows nothing listed under that event. What is the most likely cause?

• AThey are in a permission mode that skips hooks, so nothing was registered
• BTheir session began before the change and needs restarting
• CIt is configured in a settings file that stays on your machine, so it never reached them
• DA hook applies only to the person who configured it, by design

You launch Claude Code in `packages/web` of a monorepo. The repository root has a CLAUDE.md saying commit messages use conventional commit format, and `packages/web/CLAUDE.md` says they should be plain sentences. What happens?

• ABoth files load and are concatenated, so nothing resolves the contradiction and Claude may follow either — the fix is to remove the conflict
• BThe nearer file wins, because CLAUDE.md files override each other from the working directory outwards
• COnly the root file loads, because Claude Code walks up the tree and stops at the first file it finds
• DClaude asks you which of the two applies before taking its first action

Claude tells you that every outbound request in this project goes through a retry wrapper that swallows one specific error. How should you treat the answer?

• AAs settled, because it was read out of your code rather than recalled from training
• BAs a well-informed lead — open the file it named and confirm it
• CAs unreliable until a test demonstrates the behaviour
• DAs reliable only if Claude also ran the test suite first

You start a session in a newly created worktree and the first thing it tries — running the test suite — fails immediately with missing modules and a missing configuration value. What is going on?

• AThe worktree is read-only until you approve the first write
• BWorktrees do not inherit your permission settings, so the test command was blocked silently
• CThe worktree shares files with your main checkout, so the run collided with something you were doing there
• DA worktree is a fresh checkout of tracked files, so dependencies are not installed and gitignored files such as `.env` are simply absent