Developer Productivity & Operational Enablement

Question 1 · 7.1

A bank requires that Claude Code never read files under any secrets/ directory, on every developer machine and in every repository. Developers must not be able to relax this.

Where should this rule be configured?

• AIn each repository’s CLAUDE.md, stated as a clear, emphasised instruction.
• BAs an allow list in each repo’s .claude/settings.json that omits secrets/.
• CAs a Read deny rule for secrets/** in managed settings.
• DIn each developer’s ~/.claude/settings.json, installed by onboarding.

Question 2 · 7.1

A team wants every engineer to connect to the company’s internal issue-tracker MCP server with their own personal token. The server definition should be shared, so nobody has to configure it by hand.

Which setup is most appropriate?

• AAdd the server at user scope on each laptop during onboarding.
• BCommit .mcp.json with a shared service-account token in the headers.
• CPaste each engineer’s token into CLAUDE.md so Claude can pass it.
• DCommit .mcp.json with a ${TRACKER_TOKEN} header and have each user set it.

Question 3 · 7.1

Which two statements about how Claude Code combines settings across scopes are correct? (Select 2.)

• APermission lists such as permissions.allow merge across settings files.
• BA deny rule in any scope blocks an action that another scope allows.
• CThe more specific file path in a rule always wins over a broader rule.
• DProject local settings override managed settings for that one repository.
• EUser settings override the committed project settings file.

Question 4 · 7.1

An organisation’s security team wants to stop engineers installing plugins from arbitrary GitHub repositories, while still letting them use the company’s own internal plugin catalogue.

What should the architect recommend?

• AAsk engineers in the onboarding guide to use only the internal catalogue.
• BSet strictKnownMarketplaces in managed settings to allow only the internal marketplace.
• CAdd the internal marketplace to extraKnownMarketplaces in every repository.
• DDisable all plugins and copy the skills into each repository by hand.

Question 5 · 7.2

A fintech team says Claude Code’s changes often compile but break edge cases, and reviewers now spend longer on each pull request than before adoption.

Which change is most likely to improve the workflow?

• ASwitch every session to the largest available model.
• BAdd a longer CLAUDE.md section describing common edge cases in prose.
• CRequire Claude to run the relevant tests before finishing, enforced by a Stop hook.
• DLimit Claude to writing comments and let engineers write all the code.

Question 6 · 7.2

A platform team wants every file Claude edits to be formatted with the team’s formatter, with no exceptions, across all repositories that use a shared setup.

What is the best mechanism?

• AA PostToolUse hook on edits, distributed in the team’s plugin.
• BA line in each repository’s CLAUDE.md asking Claude to run the formatter.
• CA skill named /format that engineers invoke at the end of a session.
• DA nightly CI job that reformats the default branch.

Question 7 · 7.2

An organisation plans to run the Claude Code GitHub Action on a schedule across 200 repositories to triage new issues. Finance is worried about unpredictable spend.

Which configuration best addresses the concern?

• ARun it without limits at first to learn how many turns triage really needs.
• BUse a personal OAuth token so runs count against a subscription instead of the API.
• CMove triage to engineers’ laptops so CI minutes aren’t used.
• DSet --max-turns, workflow timeouts and concurrency limits, and scope allowed tools.

Question 8 · 7.2

A team must update 900 files for a breaking API change. Which approach reflects Claude Code’s guidance for large migrations?

• AOne long interactive session that edits all 900 files in sequence.
• BList the files, pilot a few, then loop claude -p per file with scoped tools and a check.
• CAsk Claude to write a regex that performs the change across the codebase.
• DRun 900 parallel sessions with bypassPermissions so none of them stall.

Question 9 · 7.3

A developer says Claude Code keeps ignoring the rule “use pnpm, never npm”, which is in a CLAUDE.md inside the web/ subdirectory. They started the session from the repository root and asked Claude to add a dependency.

What should they check first?

• AReinstall Claude Code in case the memory loader is corrupted.
• BMove the rule into managed settings so it cannot be overridden.
• CRun /context to see whether that CLAUDE.md has loaded yet.
• DRepeat the rule in capital letters three times in the root CLAUDE.md.

Question 10 · 7.3

During an incident, an SRE wants Claude Code to investigate elevated error rates using the company’s observability MCP server and the production Kubernetes cluster.

Which setup best balances speed and safety?

• AStart with bypassPermissions so Claude isn’t slowed down by prompts.
• BRead-only credentials and tools, plan mode, and a human approving any remediation.
• CGive Claude cluster-admin so it can restart pods as soon as it finds the cause.
• DKeep Claude out of incidents entirely and use it only for the post-mortem.

Question 11 · 7.3

A team’s internal MCP server shows as connected in /mcp but lists zero tools. Which two steps does Claude Code’s guidance suggest? (Select 2.)

• ASelect Reconnect for the server from /mcp.
• BIf still zero, run claude --debug=mcp and read the server’s stderr in the debug log.
• CMove the server definition into .claude/settings.json under mcpServers.
• DRaise MAX_MCP_OUTPUT_TOKENS so the tool list fits.
• EAdd mcp__* to the allow list in permissions.

Question 12 · 7.3

A security team asks the platform team to “turn on full logging” of every Claude Code prompt and tool output across the company, to support future investigations.

What is the most appropriate response?

• AEnable all content-logging variables fleet-wide; more data is always safer.
• BDecline any telemetry, because OpenTelemetry cannot be centrally configured.
• CRely on each developer’s /usage screen instead of central telemetry.
• DDeploy metrics and events centrally, and enable content logging only for a defined, approved purpose.