Domain 7: Developer Productivity & Operational Enablement
This domain is about rolling Claude out to engineering and operations teams: configuring Claude Code so a whole team shares the same setup and rules, using it to speed up everyday work, and letting it help with debugging and incidents safely. Its questions ask where a setting belongs, which workflow fits, and how much access Claude should have.
7% of the exam3 guide lines · 6 practice questionsGuide v1.0
Other domains: D1 · D2 · D3 · D4 · D5 · D6 · D7
7.1 · Configure Claude tools and environments for teams (e.g., Claude Code)
Guide line: “Configure Claude tools and environments for teams (e.g., Claude Code)”
Claude Code reads its configuration from several layers. CLAUDE.md files are memory: instructions loaded into context at the start of a session, such as coding standards, build and test commands, and architecture notes. A project CLAUDE.md is committed to the repository so the whole team shares it; a personal one in the user's home folder (~/.claude/CLAUDE.md) applies only to that person. CLAUDE.md is guidance the model reads, not enforcement.
Enforcement lives in settings. The committed .claude/settings.json holds permission rules (allow, ask or deny for tools, commands and file paths) and hooks: commands that run at fixed points, such as before a tool runs (and can block it) or after a file is edited (for example, to run the formatter). .claude/settings.local.json holds personal project settings and is not committed. A committed .mcp.json shares MCP server definitions with the team; secrets are referenced as environment variables so they never enter git. Shared slash commands and Skills in the repository give everyone the same workflows.
Managed settings are deployed by administrators to every machine and sit at the top of the order: users and projects cannot override them. Use them for organisation policy, such as denying access to secret files, blocking risky commands or limiting which MCP servers may be used. Below them come command-line options, then local project settings, then shared project settings, then user settings. A deny rule beats an allow rule.
Know this
- CLAUDE.md is instructions the model reads; permissions and hooks are enforced by Claude Code itself.
.claude/settings.jsonis committed and shared;.claude/settings.local.jsonis personal and not committed.- A committed
.mcp.jsonshares MCP servers; tokens are referenced through environment variables. - Managed settings have the highest precedence and cannot be overridden by users or projects.
- Deny rules take precedence over allow rules.
- Hooks run every time at their event; a hook before a tool call can block that call.
- Shared slash commands and Skills in the repo give the team the same workflows.
Mind map
| When the stem says… | Pick | Why |
|---|---|---|
| An organisation-wide rule nobody may loosen | Managed settings | Highest precedence; users cannot override |
| A team convention, such as the test command or style | Project CLAUDE.md | Shared guidance that travels with the repo |
| Something must happen or be blocked every time | Hook or permission rule in .claude/settings.json | Enforced, not just suggested |
| The team shares an MCP server that needs a token | .mcp.json with an environment-variable reference | Shared setup, no secret in git |
| One repository needs a restriction its own team owns | Deny rule in that project's settings | Managed settings are for organisation policy, not one team's choice |
Worked example
Situation: A software company wants every developer to run tests the same way, auto-format edited files, and never let Claude Code read production credentials. Some developers like a terse output style.
Decision: Test commands and conventions go in the project CLAUDE.md; the formatter runs from a hook in .claude/settings.json; the credentials deny rule goes in managed settings; output style stays in each developer's user settings.
Why: Each need goes to the layer that matches who owns it and how firmly it must hold. Putting the credentials rule in CLAUDE.md is tempting, but it is only an instruction and a developer could remove it.
Practice
A bank's security team requires that Claude Code never reads files matching .env or anything under secrets/, in any repository, and that individual developers cannot loosen this rule. About 400 developers use Claude Code across 60 repositories. Where should the rule be configured?
- A deny rule in each repository's committed
.claude/settings.json. - A deny rule in managed settings deployed to every developer's machine.
- An instruction in each repository's CLAUDE.md not to open secret files.
- A blocking hook in each developer's user settings that checks file paths.
Show answer
Answer: B. The deciding facts: the rule covers every repository, and developers must not be able to loosen it. Only managed settings apply everywhere and cannot be overridden.
- A ❌ Works for one team's repository, but it must be copied into 60 repos and any developer with commit access could change it.
- B ✅ A deny rule in managed settings deployed to every developer's machine.
- C ❌ Works as guidance, but the model reads it as an instruction; nothing enforces it.
- D ❌ Works technically, but user settings are under each developer's control, so they could remove it.
A platform team wants Claude Code to use its internal ticketing MCP server whenever anyone works in the payments repository. The server needs an API token, and each developer already has a personal token in an environment variable. The setup should arrive automatically when someone clones the repository. What should the team do?
- Ship a setup script that adds the server to each developer's user config.
- Explain in the repo's CLAUDE.md how each developer should add the server.
- Add the server to managed settings so it is set up on every machine.
- Commit a
.mcp.jsonthat reads the token from that variable.
Show answer
Answer: D. The deciding facts: the server belongs to one repository and must arrive on clone, with no secret in git. A committed .mcp.json does both, using an environment-variable reference for the token.
- A ❌ Works, but it needs an extra manual step and applies the server to every project, not just payments.
- B ❌ Works as documentation, but each developer must still set it up by hand.
- C ❌ Works for an organisation-wide server, but this one belongs to a single repository.
- D ✅ Commit a
.mcp.jsonthat reads the token from that variable.
7.2 · Improve developer workflows using AI-assisted tooling
Guide line: “Improve developer workflows using AI-assisted tooling”
AI assistance helps most where work is repetitive, well defined and checkable: a first-pass code review on every pull request, test generation, documentation, large refactors and migrations (such as moving from one library version to another across hundreds of files), and onboarding, where a new developer asks Claude to explain an unfamiliar codebase.
For team-wide consistency, run Claude Code in CI (continuous integration, the pipeline that runs on every change) rather than relying on each developer. In CI it runs non-interactively: given a prompt, it does the work and exits, with no one typing. It can return structured output such as JSON so the pipeline can post findings as comments in a fixed format. The review criteria live in the repository, so every pull request is checked against the same list. Anthropic also provides a GitHub Actions integration for this pattern.
Two guardrails keep this safe and worthwhile. Humans still approve merges; Claude's review is a first pass, not the decision. And measure impact with outcome metrics such as cycle time (from first commit to merge) and escaped defects (bugs found after release), compared with before the rollout. Activity counts, such as lines generated, show usage, not value.
Know this
- In CI, Claude Code runs non-interactively from a prompt and can return JSON for the pipeline to use.
- Shared review criteria in the repo make every pull request get the same first-pass check.
- Humans keep approval of merges; an AI review is a first pass.
- Good targets: code review, tests, docs, migrations and onboarding.
- Measure outcomes (cycle time, escaped defects), not activity (lines generated, sessions).
- Large migrations work best split into many small, verifiable changes, each checked by tests.
Mind map
| When the stem says… | Pick | Why |
|---|---|---|
| A consistent automated review on every pull request | Claude Code in CI, non-interactive, structured output | Runs the same way every time without relying on people |
| A developer wants help before they push | Local Claude Code with a shared review command | Fast feedback for one person |
| Leadership asks if it is worth the cost | Cycle time and escaped defects before and after | Outcomes, not usage |
| Hundreds of files need the same library upgrade | Claude-driven migration in small batches, tests on each | Repetitive and checkable |
| Someone suggests auto-merging what Claude approves | Keep human approval | The first pass is not the decision |
Worked example
Situation: A fintech's 30 engineers spend days on review, and new joiners take a month to become productive.
Decision: Add a Claude Code review step in CI that checks each pull request against the team's checklist and posts findings; give new joiners a shared onboarding command that explains the codebase. Track review turnaround and time to first merged change.
Why: Both are repetitive and benefit everyone the same way. Asking each engineer to review with Claude locally is tempting, but results depend on who remembers to do it.
Practice
A 40-person engineering team wants every pull request to get the same first-pass review against its own checklist, with findings posted as PR comments in a fixed format. Engineers will still approve every merge. Which setup fits best?
- Run Claude Code in CI on each pull request, non-interactively, with JSON output.
- Ask engineers to review with Claude Code locally before opening a pull request.
- Put the checklist in CLAUDE.md so Claude applies it whenever engineers use it.
- Have Claude Code approve and merge pull requests that pass the whole checklist.
Show answer
Answer: A. The deciding facts: every pull request, the same check, a fixed comment format. Only an automated CI step guarantees all three; JSON output lets the pipeline post findings consistently.
- A ✅ Run Claude Code in CI on each pull request, non-interactively, with JSON output.
- B ❌ Works for fast personal feedback, but it depends on each engineer remembering to do it.
- C ❌ Works as guidance during interactive use, but nothing runs it on every pull request.
- D ❌ Works for some low-risk changes elsewhere, but the stem keeps engineers approving every merge.
Three months ago an engineering director rolled out Claude Code for test generation and library migrations. The CFO now asks whether it is worth its licence cost compared with the time before rollout. Which two measures give the most useful evidence?
- Cycle time from first commit to merge, before and after the rollout.
- Lines of code produced by Claude Code each week across the team.
- A developer survey asking how much they enjoy using the tool.
- Escaped defects found after release, before and after the rollout.
- Number of Claude Code sessions each developer starts per week.
Show answer
Answer: A and D. The deciding fact: the CFO asks about value against a before-and-after baseline. Delivery speed and quality outcomes answer that; activity and sentiment do not.
- A ✅ Cycle time from first commit to merge, before and after the rollout.
- B ❌ Works as a usage signal, but more lines can mean worse code, so it says nothing about value.
- C ❌ Works for adoption and morale, but enjoyment is not a business outcome.
- D ✅ Escaped defects found after release, before and after the rollout.
- E ❌ Works to track adoption, but usage is not value.
7.3 · Support debugging and operational issue resolution
Guide line: “Support debugging and operational issue resolution”
In debugging, Claude Code can read the code, run the failing test, add logging, and reproduce the problem before proposing a fix. The habit to insist on is finding the root cause, the real reason for the failure, rather than masking the symptom, for example by adding a retry around a flaky test. Asking Claude to reproduce the failure and explain it before editing code keeps fixes honest.
In operations, Claude helps on-call engineers by reading observability data: logs, metrics, traces, recent deployments and runbooks (step-by-step guides for known problems). These are usually connected through MCP servers (Model Context Protocol, the standard way to give Claude tools and data). Read-only tools let Claude correlate signals, match the incident to a runbook and draft a summary and a proposed fix, far faster than people pasting log excerpts into a chat.
Investigation is low risk; changes to production are not. So the tools Claude uses to investigate are read-only, and any remediation (restarting a service, changing a setting, rolling back) goes through human approval, using the normal change process so it is logged. Teams may later automate a few low-risk, well-tested runbook steps, but that is a deliberate decision, not a default.
Know this
- Give Claude read-only access to logs, metrics, traces and runbooks, often through MCP servers.
- Remediation actions in production need human approval and go through the normal, logged change process.
- Ask Claude to reproduce a bug and explain the cause before it edits code.
- Masking a symptom (retries, skipped tests) is not a fix.
- Separate read tools from write tools so investigation never holds write access.
- A clear incident summary with evidence and a proposed fix speeds up the human decision.
Mind map
| When the stem says… | Pick | Why |
|---|---|---|
| On-call wants help triaging incidents | Read-only MCP access to logs, metrics and runbooks | Fast investigation with no production risk |
| Claude proposes a production change | Engineer approves and applies it through the change process | High-impact actions need a human and a record |
| A test fails intermittently | Reproduce, find the root cause, then fix | Retries hide the bug |
| A low-risk, well-tested runbook step runs many times a week | Consider approved automation for that step only | Approval for every repeat adds little safety |
| Engineers paste logs into a chat by hand | Connect the sources through MCP | Faster and complete, with less copying |
Worked example
Situation: An e-commerce site's checkout errors spike at night. On-call engineers spend the first 30 minutes of each incident collecting logs and searching for the runbook.
Decision: Connect read-only MCP servers for logs, metrics, deployment history and the runbook wiki. Claude drafts the triage summary and proposed fix; the on-call engineer approves and runs any change.
Why: Claude removes the slow gathering work while people keep control of production. Giving Claude write access to apply fixes itself is tempting at 3 a.m., but one wrong action could widen the outage.
Practice
An on-call team wants Claude to help with incidents: read recent logs, metrics and traces, find the matching runbook, and propose a fix. The SRE lead insists that nothing in production changes without an engineer's approval. Which setup fits best?
- Give Claude read access to the log platform only, and let engineers find runbooks and metrics themselves.
- Have on-call engineers paste log excerpts and runbook sections into a chat with Claude during incidents.
- Connect read-only MCP tools for logs, metrics and runbooks, and have an engineer apply any fix.
- Let Claude apply runbook fixes automatically in production and notify the on-call engineer afterwards.
Show answer
Answer: C. The deciding facts: Claude must see logs, metrics and runbooks together, and every production change needs approval. Read-only tools for all three, with engineers applying fixes, meets both.
- A ❌ Works and is safe, but Claude cannot correlate metrics or match runbooks, which is the help the team asked for.
- B ❌ Works, but it is slow and depends on people choosing the right excerpts mid-incident.
- C ✅ Connect read-only MCP tools for logs, metrics and runbooks, and have an engineer apply any fix.
- D ❌ Works for some low-risk auto-remediation, but it breaks the stated rule that nothing changes without approval.
A developer asks Claude Code to fix a test that fails in CI about one run in five. Claude's first attempt wrapped the failing check in a retry, and the test now passes. The team's standard is that flaky tests are fixed at their root cause. What should the developer do next?
- Keep the retry, since the test now passes and the build is green again.
- Have Claude rerun the test repeatedly, read CI logs and explain the cause.
- Mark the test as skipped in CI and open a ticket to investigate it later.
- Add a CLAUDE.md rule against retries in tests, then ask Claude to try once more.
Show answer
Answer: B. The deciding fact: the standard is a root-cause fix, and a retry only hides the failure. Reproducing it and explaining the cause comes before any code change.
- A ❌ Works to unblock the build, but it masks the bug and breaks the team's standard.
- B ✅ Have Claude rerun the test repeatedly, read CI logs and explain the cause.
- C ❌ Works as a temporary measure under deadline pressure, but it postpones the fix the standard requires.
- D ❌ Works to prevent repeats, but on its own it still skips the diagnosis and Claude may mask the bug another way.
Source of the guide lines: Claude Certified Architect – Professional Exam Guide, v1.0 (Anthropic). Explanations and questions are ours, written fresh. · CCA-P start here