# CCAR-F Practice: Claude Code workflows | Your AI Department > 40 free CCAR-F practice questions on Claude Code workflows (20% of the exam), with study notes and explanations. Source: https://youraidept.com/network/ccar-f-practice-questions/claude-code-workflows CCAR-F domain drill # CCAR-F practice questions: Claude Code workflows. 40 original questions on Claude Code workflows, which carries 20% of the Claude Certified Architect – Foundations exam per the published guide. Study notes first, then the questions with an explanation for each. When this domain feels solid, take [the timed CCAR-F practice exam](https://youraidept.com/network/ccar-f-practice-exam) and check the domain breakdown. ## What to know about Claude Code workflows - CLAUDE.md as project memory: what belongs in it (commands, conventions, gotchas) and what does not (long documents the model can read on demand). - The explore, plan, code, commit rhythm from Anthropic's best-practices guide, and plan mode as a way to separate thinking from editing. - Slash commands, skills, and subagents: reusable prompts versus delegated work with its own context. - Hooks: deterministic shell steps that run before or after tool calls, used for formatting, linting, blocking dangerous commands, and notifications. - Permission modes and allow lists, and why the default asks before writes and shell commands. - MCP server configuration at project and user scope, and headless use in CI and scripts with the print flag. - Context hygiene: clearing and compacting, and why long sessions degrade without it. ## Claude Code workflows questions All domains (40) Claude Code workflows (40) Claude Code workflows What belongs in a project's CLAUDE.md file? - Build and test commands, project conventions, and gotchas Claude needs on every task, kept short - Environment variables and service credentials the project needs, so Claude can run commands without asking - The full architecture documentation and API references, so Claude has complete knowledge in every session - A running log of past sessions and their outcomes, so Claude can pick up where the last one ended Check answer ### Show answer Answer: Build and test commands, project conventions, and gotchas Claude needs on every task, kept short. CLAUDE.md is standing project memory: short, high-value instructions loaded into every session. Long documents cost context on every task and are better read on demand; secrets do not belong in a checked-in file; session history is what memory files or notes are for. Claude Code workflows A team wants every file Claude Code edits to be run through the formatter, without relying on the model to remember. Which mechanism is right? - A custom slash command that formats the tree, which the developer runs at the end of a session - A formatting subagent that the main session delegates to once the edits are complete - A CLAUDE.md instruction asking Claude to run the formatter after each edit it makes - A PostToolUse hook matched to the edit tools that runs the formatter on the changed file Check answer ### Show answer Answer: A PostToolUse hook matched to the edit tools that runs the formatter on the changed file. Hooks are deterministic shell steps tied to tool events; they run whether or not the model remembers. A CLAUDE.md note is advisory, and a slash command or subagent still depends on someone invoking it. Claude Code workflows How would you run Claude Code non-interactively inside a CI job? - A subagent launched from a developer's local session, with the CI job waiting on its result - Print mode with the -p flag, passing the prompt and a restricted allowed-tools list - An interactive session on the runner with the permission mode set to accept every action - A plan-mode session, since planning does not edit files and so needs no approvals Check answer ### Show answer Answer: Print mode with the -p flag, passing the prompt and a restricted allowed-tools list. Print mode runs a single prompt headlessly and exits, and restricting tools keeps a CI run from taking actions nobody reviewed. An interactive session with accept-all permissions has no human present and no bound on what runs. Claude Code workflows A session has been running for hours and answers are getting worse and slower. What is the first thing to try? - Switch the session to a larger model so it can hold more of the accumulated conversation - Paste the full transcript so far back in as a new user message so nothing is lost - Compact or clear the context, then re-brief the task with only what the next step needs - Disable hooks for the rest of the session, since each hook adds latency to every tool call Check answer ### Show answer Answer: Compact or clear the context, then re-brief the task with only what the next step needs. Quality degrades as the window fills with stale material; compaction and clearing exist to fight exactly this. Pasting the transcript back doubles the bulk that caused the problem, and a larger model does not shrink the window's contents. Claude Code workflows A developer complains Claude Code re-explores the codebase every session. The cheapest fix is: - A subagent that explores the codebase and reports back at the start of each session - A memory file the developer pastes into the first message of every session - A longer first prompt each session that walks through the directory layout - A CLAUDE.md with the project's structure, commands, and conventions Check answer ### Show answer Answer: A CLAUDE.md with the project's structure, commands, and conventions. CLAUDE.md is loaded automatically and is the place for standing project knowledge. An exploring subagent still spends the exploration every session; a pasted file is CLAUDE.md done by hand. Claude Code workflows You want Claude Code to plan before it edits on a large refactor. Which feature matches? - Plan mode, which explores and proposes an approach before any file changes - Headless mode with a prompt asking for a written plan and no tool access - A PreToolUse hook that rejects edit calls until a plan file exists in the repository - A custom slash command that runs the test suite before each edit is applied Check answer ### Show answer Answer: Plan mode, which explores and proposes an approach before any file changes. Plan mode separates thinking from editing so you can review the approach first. A hook that blocks edits enforces a gate but gives you no plan to review; headless mode is for automation, not a review step. Claude Code workflows A repeated workflow, 'update the changelog from recent commits', should be one command. Which Claude Code feature? - A subagent dedicated to changelog work, invoked from the main session - A PostToolUse hook on git commit that appends the message to the changelog - A custom slash command or skill that captures the prompt and steps - An MCP server exposing a changelog tool that reads the git history Check answer ### Show answer Answer: A custom slash command or skill that captures the prompt and steps. Reusable prompts belong in slash commands or skills; hooks are for deterministic shell steps. A hook on commit fires per commit and cannot write a summarized changelog on demand; an MCP server adds a tool, not a reusable workflow. Claude Code workflows Which permission approach is right for a shared CI runner using Claude Code? - Accept every tool call automatically, since no developer is present to approve - Deny every tool so the run is a pure text response with no side effects - An explicit allow list of tools and commands, with no interactive approvals - Prompt the developer who pushed the commit for each tool approval via chat Check answer ### Show answer Answer: An explicit allow list of tools and commands, with no interactive approvals. Headless runs cannot ask a human, so the allowed surface is defined up front and kept narrow. Accepting everything removes the boundary; denying every tool leaves Claude unable to read the code it is meant to work on. Claude Code workflows Where does an MCP server configuration belong when it should apply to everyone working in the repository? - In each developer's user-level settings, synced through a dotfiles repository - In the project-scoped configuration checked into the repository - In a SessionStart hook that registers the servers when Claude Code launches - In the system prompt for the session, listed as servers Claude should connect to Check answer ### Show answer Answer: In the project-scoped configuration checked into the repository. Project scope travels with the repo; user scope is personal. A dotfiles sync approximates it but relies on every developer keeping up; the system prompt cannot register a server. Claude Code workflows A hook that blocks a tool call should communicate the reason. Why? - So the block is written into the transcript for the developer to review later on - So the hook's exit code can be mapped to the right billing category - So the model can override the block when the reason does not apply - So the model can adjust its plan instead of retrying the same blocked action Check answer ### Show answer Answer: So the model can adjust its plan instead of retrying the same blocked action. Feedback from a blocked call lets the model take a different path. Logging is a side benefit, not the point; a hook's reason is information for the model, not a mechanism to override the block. Claude Code workflows Which task is a good fit for a Claude Code subagent? - A large, self-contained investigation whose details would clutter the main session - Changing the permission settings so the main session can run a tool - Reading CLAUDE.md at the start of a session and summarizing its rules back to the user - Applying a one-line change that the main session has already located Check answer ### Show answer Answer: A large, self-contained investigation whose details would clutter the main session. Subagents isolate context. Delegate work whose transcript you do not need in the main thread. A one-line change is cheaper to make directly, and CLAUDE.md is already loaded for the main session. Claude Code workflows A team notices Claude Code sometimes runs the test suite three times in a row. Which is the right lever? - Removing the test command from the allowed tools and running tests in CI instead - Increasing the max turns so the session can finish before the loop is cut off - A hook or CLAUDE.md rule defining when tests run, plus a check of the loop for missing stop conditions - A stricter system prompt telling Claude to run the tests only once per task Check answer ### Show answer Answer: A hook or CLAUDE.md rule defining when tests run, plus a check of the loop for missing stop conditions. Repeated actions point to missing structure: explicit rules for when to run tests and clear stop conditions. Removing the command hides the symptom and slows feedback; more turns give the loop more room to repeat. Claude Code workflows What does the /compact style operation do in a long session? - Trims tool results from the transcript but keeps every user and assistant turn - Summarizes the conversation so far to free context while keeping the essentials - Switches to a model with a larger window so the session can continue - Restarts the session with the same CLAUDE.md loaded and an empty conversation history Check answer ### Show answer Answer: Summarizes the conversation so far to free context while keeping the essentials. Compaction trades detail for headroom, which is what long sessions need. It summarizes the whole conversation, not just tool results; a clean restart is what /clear does, and it loses the essentials compaction keeps. Claude Code workflows A developer wants Claude Code to stop before committing so they can review. Best approach? - A CLAUDE.md line asking Claude to confirm with the user before running git commit - Keep commit outside the allowed actions, or gate it with a hook that requires confirmation - A PostToolUse hook on git commit that opens the diff for the developer to review - Run the whole session in plan mode so no commands execute until the developer approves the plan Check answer ### Show answer Answer: Keep commit outside the allowed actions, or gate it with a hook that requires confirmation. Review points are enforced through permissions and hooks, not memory. A PostToolUse hook fires after the commit already exists; plan mode blocks all edits, not just the commit. Claude Code workflows Which of these belongs in CLAUDE.md rather than a subagent or a skill? - The linter command and a note that the tests need the local database running - The API keys for the staging environment so tests can run end to end - A 200-page design document describing every subsystem in the product and how they connect - A weekly status report template the team fills in every Friday Check answer ### Show answer Answer: The linter command and a note that the tests need the local database running. Short, always-relevant operational facts are CLAUDE.md material. Long documents are loaded on demand; a report template is a skill or slash command; keys do not go in a checked-in file. Claude Code workflows You need Claude Code to review a pull request in CI and post comments, with no ability to push code. Which controls? - Interactive mode on the runner so a reviewer can approve each tool call - Print mode with full permissions, relying on the prompt to say 'do not push code' - Print mode with a read-only tool allow list and the git push command denied - Plan mode, since planning cannot push code and can still read the diff Check answer ### Show answer Answer: Print mode with a read-only tool allow list and the git push command denied. Least privilege for automation: read-only tools plus explicit denies on writes. Relying on the prompt is advisory; interactive mode has no reviewer present in CI. Claude Code workflows A Claude Code session is asked to fix a bug and, without being asked, refactors three unrelated files. What reduces this? - A larger context window so Claude can see why the other files are unrelated - A PostToolUse hook that reverts any edit outside the file named in the prompt - Running the fix headless so there is no room for exploratory editing - Explicit scope in the prompt, CLAUDE.md conventions about minimal diffs, and plan mode for review Check answer ### Show answer Answer: Explicit scope in the prompt, CLAUDE.md conventions about minimal diffs, and plan mode for review. Scope discipline comes from explicit instructions and a review step before edits. A revert hook is a blunt tool that also blocks legitimate changes in a second file; headless mode removes the review, not the drift. Claude Code workflows What is the purpose of a PreToolUse hook? - Compact the context when a tool result is too large - Inspect or block a tool call before it executes - Run a command after the model has finished its response - Swap the model for a cheaper one on routine tool calls Check answer ### Show answer Answer: Inspect or block a tool call before it executes. Pre hooks gate actions; post hooks react to them. Running after the response is a Stop hook; compaction and model choice are not what hooks control. Claude Code workflows A monorepo has several services with different test commands. Where should that live for Claude Code? - A subagent per service that carries that service's commands in its own prompt - The first message of each session, restated whenever the service changes - CLAUDE.md, with a short per-service map of test commands and conventions - The repository README, which Claude Code reads automatically at session start Check answer ### Show answer Answer: CLAUDE.md, with a short per-service map of test commands and conventions. Project memory holds per-area commands and loads on every session. The README is not loaded automatically, and restating commands in chat is manual and easy to forget. Claude Code workflows Which hook event would you use to run a security scan on every file Claude writes? - A slash command the developer runs after each session to scan changed files - A PreToolUse hook on the Read tool, so files are scanned before Claude opens them - A PostToolUse hook matched to the Write and Edit tools, run after each change lands - A Stop hook that scans the whole working tree once when Claude finishes its turn and reports findings Check answer ### Show answer Answer: A PostToolUse hook matched to the Write and Edit tools, run after each change lands. Post hooks react to completed writes, so the scan sees the file as written. A Stop hook runs once per turn and misses intermediate writes; a PreToolUse hook on Read never sees writes at all. Claude Code workflows A developer wants Claude Code to ask before running any command that touches the network. Which setting? - Permission rules that allow safe commands and require confirmation for matching network commands - A CLAUDE.md instruction telling Claude to ask for confirmation before any command that reaches the network - A PostToolUse hook on Bash that inspects the command for network calls and logs a warning - Plan mode for the whole session, so every command is proposed before it is executed Check answer ### Show answer Answer: Permission rules that allow safe commands and require confirmation for matching network commands. Granular permission rules gate specific commands. A PostToolUse hook runs after the command has already executed, and a CLAUDE.md line is guidance rather than enforcement. Claude Code workflows What is the benefit of committing project-scoped MCP configuration to the repo? - It lets the repo's MCP servers override the user's own server settings for the project - Every contributor gets the same integrations without manual setup on each machine - Claude Code caches the server tool lists in git, which speeds up session start - Server credentials travel with the code, so contributors do not need their own tokens Check answer ### Show answer Answer: Every contributor gets the same integrations without manual setup on each machine. Shared config travels with the code, so integrations are consistent across the team. Credentials should stay out of the repo, in environment variables or user-level config. Claude Code workflows Claude Code proposes a plan that touches an unrelated module. What is the right response in plan mode? - Accept the plan, then revert the unrelated edits during code review - Revise the plan's scope before any edits are made to the tree - Run the test suite first to see whether the extra module is affected - Exit plan mode and let Claude discover the right scope as it edits Check answer ### Show answer Answer: Revise the plan's scope before any edits are made to the tree. Plan mode exists to correct scope before edits happen. Accepting and reverting later wastes work and risks missing an edit. Claude Code workflows Which is a sensible use of a Claude Code skill? - A packaged procedure like 'write a release note from merged PRs' with its own instructions and helper files - A per-task override that switches the session to a different model for that procedure - A place to store the API keys and tokens the procedure needs, loaded only when invoked - A replacement for CLAUDE.md that holds all project conventions and commands in a single file loaded on demand Check answer ### Show answer Answer: A packaged procedure like 'write a release note from merged PRs' with its own instructions and helper files. Skills package reusable procedures with their supporting files. Project conventions belong in CLAUDE.md, and secrets belong in environment configuration, not in a skill. Claude Code workflows You want a nightly job where Claude Code triages new issues and labels them. Which pieces? - Print mode in a scheduled job with a read-only tool set plus one allowed labeling action - A PostToolUse hook that fires whenever a new issue is created and labels it in place - A subagent with full permissions, invoked from a cron entry with the issue list as input - An interactive session left open overnight with auto-accept enabled for all tool calls Check answer ### Show answer Answer: Print mode in a scheduled job with a read-only tool set plus one allowed labeling action. Headless, scheduled, and least-privilege. Hooks respond to Claude's own tool calls, not to external events, and full permissions are more than a labeling job needs. Claude Code workflows A PreToolUse hook exits with code 2 on a tool call. What should happen? - Claude Code ends the session so the developer can inspect the hook's output manually - The call is blocked and the hook's message is surfaced so the model can adjust - The hook is disabled for the rest of the session and the call is retried once - The call proceeds and the hook's stderr is shown to the user, as with other non-zero exits Check answer ### Show answer Answer: The call is blocked and the hook's message is surfaced so the model can adjust. Exit code 2 is the blocking exit: the action stops and the hook's stderr is fed back to the model. Other non-zero codes surface the message to the user and let the call continue. Claude Code workflows Which practice keeps a long Claude Code session productive? - Pasting the previous session's transcript at the start so no earlier decision is lost - Keeping one session open so the model keeps every file it has read - Clearing or compacting between unrelated tasks and re-briefing the next task - Disabling hooks mid-session so tool calls complete with less overhead Check answer ### Show answer Answer: Clearing or compacting between unrelated tasks and re-briefing the next task. Fresh context per task keeps attention on what matters. Pasting transcripts or holding every file read fills the window with material the next task does not need. Claude Code workflows What should a team review when a Claude Code change is opened as a pull request? - The test output only, because a green suite proves the change is correct - The diff, the tests it ran, and whether the scope matched the request - Whether the CLAUDE.md conventions were followed, with the diff left to CI - The commit message and the model version, since the diff itself was generated Check answer ### Show answer Answer: The diff, the tests it ran, and whether the scope matched the request. Review automated changes like any other: the diff, the evidence, and the scope. A green suite does not prove the change did what was asked. Claude Code workflows Which is the right place for a rule like 'never edit files under vendor/'? - A README section, since Claude Code reads project documentation before it edits - CLAUDE.md for guidance plus a hook or permission deny rule for enforcement - A comment at the top of each vendored file saying the file is not to be edited - A dedicated subagent that owns vendor/ and rejects edit requests from the main session Check answer ### Show answer Answer: CLAUDE.md for guidance plus a hook or permission deny rule for enforcement. Guidance plus enforcement: CLAUDE.md explains the rule and a deny rule or hook makes it hold. File comments and READMEs are only read if Claude happens to open them. Claude Code workflows How do subagents help with a large migration in Claude Code? - They share the main session's context, so every slice sees the same file history and the same earlier decisions - They run without tools, so they can plan slices while the main session performs the edits - They bypass the test suite for each slice so the migration completes faster - Each handles a bounded slice in its own context and returns a summary, keeping the main session coherent Check answer ### Show answer Answer: Each handles a bounded slice in its own context and returns a summary, keeping the main session coherent. Bounded slices with summaries back keep the coordinator's window clean. Subagents have separate contexts and can use tools; sharing context is the problem they solve. Claude Code workflows A team wants Claude Code to follow its commit message convention every time. Which approach is reliable? - State the convention in CLAUDE.md with an example, and validate with a hook on commit - Delegate all commits to a subagent whose prompt contains the convention - Tell Claude Code once at the start of the session and rely on it for the rest of the work - Let Claude Code infer the convention from the existing git log before it commits Check answer ### Show answer Answer: State the convention in CLAUDE.md with an example, and validate with a hook on commit. Guidance plus enforcement. Inferring from the log works until the log has inconsistent history, and a chat instruction does not survive the session. Claude Code workflows Which is a good reason to use headless Claude Code inside a GitHub Action? - Exploring an unfamiliar codebase, since the runner has a clean checkout to learn from - Pair programming on a feature branch, with the Action re-running after every push - Repeatable, reviewable automation such as summarizing a PR, with a fixed tool allow list - Interactive debugging of a failing build, where the developer talks to Claude in the CI logs Check answer ### Show answer Answer: Repeatable, reviewable automation such as summarizing a PR, with a fixed tool allow list. Headless suits repeatable, bounded jobs with a fixed allow list. Debugging and exploration need a person in the loop. Claude Code workflows A hook blocks a command but Claude Code keeps retrying variations. What is missing? - A stricter permission rule that denies the Bash tool entirely for the session - A longer CLAUDE.md section repeating the rule the hook is enforcing - A clear block message that says what is disallowed and what to do instead - A second hook on the Stop event that ends the turn after the first block Check answer ### Show answer Answer: A clear block message that says what is disallowed and what to do instead. Blocks need explanations to redirect behavior. Without a reason the model treats the block as a transient failure and tries again. Claude Code workflows What is the difference between a slash command and a skill in practice? - Slash commands need an MCP server behind them; skills run entirely from Markdown - Skills run in a separate subagent context by default; slash commands run inside the main session with its full history - Slash commands are built in; skills are only available through installed plugins - A slash command is a reusable prompt you invoke; a skill packages a procedure with instructions and supporting files Check answer ### Show answer Answer: A slash command is a reusable prompt you invoke; a skill packages a procedure with instructions and supporting files. Commands are prompts; skills are packaged procedures with their own files. Neither needs an MCP server, and both can be project-defined. Claude Code workflows Which permission stance fits a developer's laptop versus a shared CI runner? - Allow everything in CI since nobody is there to answer prompts, and deny most on the laptop - The same rules in both, so behavior is predictable regardless of where it runs - Deny all writes in both and let a human apply the changes Claude proposes - Interactive approvals on the laptop; a narrow pre-approved allow list with no prompts in CI Check answer ### Show answer Answer: Interactive approvals on the laptop; a narrow pre-approved allow list with no prompts in CI. Human present versus not present: approvals where someone can answer, a narrow allow list where nobody can. Allowing everything in CI is the opposite of what an unattended runner needs. Claude Code workflows Claude Code keeps reading the same large log file into context on every task. Fix? - A CLAUDE.md note to grep the log for specific patterns rather than reading it whole, or a tool that returns matches - Increase the session's context budget so the full log fits without truncation each time - Compact the session after each read so the earlier copies of the log leave the context before the next task starts - Move the log's contents into the project CLAUDE.md so it is loaded once at startup and cached Check answer ### Show answer Answer: A CLAUDE.md note to grep the log for specific patterns rather than reading it whole, or a tool that returns matches. Targeted retrieval over bulk reads. Compaction removes the copies after the cost has been paid, and putting the log in CLAUDE.md loads it on every session. Claude Code workflows Which statement about CLAUDE.md scope is correct? - CLAUDE.md is read only from the home directory, so project rules go in settings.json - Files can live at the project root and in subdirectories, applying to work in those areas - One CLAUDE.md file per repository is allowed, and it must sit at the repository root - Subdirectory CLAUDE.md files replace the root file entirely when Claude works in that area Check answer ### Show answer Answer: Files can live at the project root and in subdirectories, applying to work in those areas. Scoped memory files per area, layered with the root file rather than replacing it. Claude Code workflows What should a team do before letting Claude Code run database migrations in a shared environment? - Ask Claude Code to review the migration SQL itself for mistakes before running it against the database - Disable hooks for the migration step so nothing interrupts a long-running command - Grant the Claude Code process admin rights so the migration cannot fail on permissions - Gate the migration command behind approval, run it against a staging copy first, and log the run Check answer ### Show answer Answer: Gate the migration command behind approval, run it against a staging copy first, and log the run. Irreversible actions get gates and rehearsal. Self-review by the same model is weaker than a staging run and a human approval. Claude Code workflows A developer asks Claude Code to 'make the tests pass' and it edits the tests to always pass. What prevents this? - Removing the test files from the working tree during the task so only the source files are editable by the model - Explicit instructions that tests define behavior and must not be weakened, plus review of test diffs - A longer timeout, so the model has time to fix the code rather than the tests - Running in plan mode so the model proposes edits but never applies them Check answer ### Show answer Answer: Explicit instructions that tests define behavior and must not be weakened, plus review of test diffs. State the constraint and review test changes. Plan mode stops all edits, including the fix that was asked for. Claude Code workflows When is a subagent overkill? - For parallel research across several independent parts of the codebase - For a one-line lookup the main session can answer directly - For a large investigation that would fill the main session with file contents - For isolating a noisy tool's output away from the main conversation Check answer ### Show answer Answer: For a one-line lookup the main session can answer directly. Delegate for scope and isolation, not trivia. The other three are the cases subagents exist for. ## Next - [Timed CCAR-F practice exam](https://youraidept.com/network/ccar-f-practice-exam): 60 questions in 120 minutes, scored against the 720 pass mark. - [All CCAR-F practice questions](https://youraidept.com/network/ccar-f-practice-questions) with a domain filter. - [The CCAR-F exam page](https://youraidept.com/network/ccar-f): format, weights, registration, study path. ### Other CCAR-F domains - [Agentic architecture (52 questions)](https://youraidept.com/network/ccar-f-practice-questions/agentic-architecture) - [Prompt engineering (40 questions)](https://youraidept.com/network/ccar-f-practice-questions/prompt-engineering) - [Tool design and MCP (35 questions)](https://youraidept.com/network/ccar-f-practice-questions/tool-design-and-mcp) - [Context management (33 questions)](https://youraidept.com/network/ccar-f-practice-questions/context-management) ## FAQ ### How much of the CCAR-F exam is Claude Code workflows? + 20% of the marks, per the published CCAR-F exam guide. The full domain list with weights is on the CCAR-F exam page. ### Are these real CCAR-F exam questions? + No. They are 40 original scenario questions written from the blueprint for this domain. Reproducing exam content would violate the candidate agreement. ### How should I study Claude Code workflows for CCAR-F? + Read the domain notes on this page, answer the questions with explanations hidden, then take the timed CCAR-F practice exam and check the per-domain breakdown for this domain. ## Who wrote this ### [Matei Olaru](https://youraidept.com/about/matei-olaru) CEO, Your AI Department Former public-company CEO, corporate attorney, and World Bank consultant. Runs the YAID Network and the partner relationship with Anthropic. ### [Michael Greenberg](https://youraidept.com/about/michael-greenberg) AI Product Lead, Your AI Department AI at Google, Meta, and Samsung. Six patents. Leads member support and the certification prep guidance. Your AI Department is a registered Claude Partner Network company. Our members sit these exams under our partner standing. Facts on this page were last checked on October 15, 2026. ## Ready to sit CCAR-F for real? Registration needs a Claude Partner Network organization. [YAID Network](https://youraidept.com/network) members register under our partner standing. $149 per quarter, exam fee separate. [Apply to join YAID ↗](https://youraidept.com/network/apply?ref=drill)[How registration works →](https://youraidept.com/network/register-for-claude-certification)