Part 9g — Question Bank: Domain 7, Developer Productivity & Operational Enablement (Q141–Q150)
Original practice questions; not official or leaked. Claude Code settings change often: verify specifics in current docs. Q147 is multi-response (Select TWO, 5 choices).
Q141 · D7 · Objective: Configure shared team tooling and standards · Difficulty: Intermediate
Scenario: A 40-engineer team uses Claude Code. Each developer re-explains build commands, conventions, and test rules every session. Question: What is the best fix? A. Maintain a project-level CLAUDE.md in version control with build/test commands, conventions, architecture notes, and "do not" rules, reviewed like code. B. Ask each developer to paste a long prompt each session. C. Store the guidance in a wiki no one links to. D. Rely on the model remembering previous sessions. Correct answer: A Explanation: Shared, versioned project memory gives every session consistent context. Why not the others: B is manual and inconsistent; C isn't loaded into context; D is unreliable. Architectural principle: Encode team knowledge where the tool reads it. Ref: Claude Code docs: memory / CLAUDE.md
Q142 · D7 · Objective: Configure shared team tooling and standards · Difficulty: Advanced
Scenario: Security wants to prevent the coding agent from reading secrets files or running destructive shell commands, for every developer. Question: What is the strongest approach? A. Add "don't read secrets" to CLAUDE.md only. B. Trust developers to deny prompts. C. Commit shared permission rules (deny for secret paths and dangerous commands, allow-list for routine ones), and use managed or organization-level settings where policy must not be overridden; add hooks for enforcement and audit. D. Disable the tool for the team. Correct answer: C Explanation: Deterministic permission rules and managed policy enforce what instructions can only request. Why not the others: A is advisory; B is inconsistent; D abandons the productivity goal. Architectural principle: Enforce with configuration, not advice. Ref: Claude Code docs: permissions, settings, hooks
Q143 · D7 · Objective: Establish developer workflows with AI assistance · Difficulty: Intermediate
Scenario: A developer asks the agent to refactor a large module in one request. The result is a huge, hard-to-review diff with subtle regressions. Question: Which workflow is better? A. Accept the diff without review because tests exist. B. Run the same request again. C. Plan first, make small incremental changes with tests run at each step, review diffs, and commit in reviewable units. D. Disable tests to speed up. Correct answer: C Explanation: Small verified steps keep changes reviewable and errors contained. Why not the others: A removes review; B repeats the problem; D removes the safety net. Architectural principle: Incremental, verified change. Ref: Claude Code best practices
Q144 · D7 · Objective: Establish developer workflows with AI assistance · Difficulty: Advanced
Scenario: The team wants an agent to review pull requests in CI. Question: Which design is most appropriate? A. Let the agent merge PRs automatically. B. Give the CI job broad production credentials. C. Skip human review once the agent approves. D. Run it with read-only repo access and minimal scoped credentials, post comments for humans to act on, treat PR content as untrusted input, and keep human approval required for merge. Correct answer: D Explanation: Least privilege plus untrusted-input handling and human approval limit risk. Why not the others: A and C remove oversight; B violates least privilege. Architectural principle: Least privilege and human gate in automation. Ref: Claude Code docs (headless/CI); Prep Lesson 5
Q145 · D7 · Objective: Create operational runbooks and support processes · Difficulty: Intermediate
Scenario: At 2 a.m. the on-call engineer sees a spike in refusals and escalations from the production assistant. Question: Which runbook content helps most? A. A general description of how LLMs work. B. Symptom-based triage steps: check recent prompt/model/retrieval changes, provider status, rate-limit and error dashboards; mitigation (rollback, fallback, feature flag); escalation contacts; and post-incident steps. C. The vendor's marketing page. D. A list of all prompts. Correct answer: B Explanation: Runbooks should enable fast diagnosis and safe mitigation. Why not the others: A, C, and D don't guide action. Architectural principle: Operational documentation is action-oriented. Ref: Prep Lesson 5
Q146 · D7 · Objective: Create operational runbooks and support processes · Difficulty: Advanced
Scenario: The assistant's behavior changed after a "minor" prompt tweak, and nobody can tell which version is live. Question: What practice would have prevented the confusion? A. Version prompts and configuration, tag each release, log the version with every request, and maintain a changelog and rollback path. B. Edit prompts in the admin UI without records. C. Keep prompts in personal notes. D. Avoid logging versions for privacy. Correct answer: A Explanation: Traceable versions allow correlating behavior with changes and rolling back. Why not the others: B–D remove traceability. Architectural principle: Version everything that changes behavior. Ref: Prep Lesson 5
Q147 · D7 · Objective: Train and onboard teams · Difficulty: Intermediate
Question (Select TWO): Which practices best onboard a team to a new AI-assisted workflow? A. Provide a short guided path with hands-on exercises on the team's real repos and a documented "what to trust, what to verify" guide. B. Mandate usage without training. C. Create feedback channels and a champions group to collect issues, share patterns, and update standards. D. Forbid asking questions to save time. E. Remove all documentation to keep it flexible. Correct answers: A, C Explanation: Practice on real work and a feedback loop create adoption and shared standards. Why not the others: B, D, and E hinder learning. Architectural principle: Enable through practice and feedback. Ref: Prep Lesson 5
Q148 · D7 · Objective: Configure shared team tooling and standards · Difficulty: Advanced
Scenario: Teams want to reuse a standard code-review procedure with reference checklists and scripts, loaded only when relevant to avoid bloating context. Question: Which mechanism fits best? A. Put the whole procedure in every prompt. B. Package it as an Agent Skill, using progressive disclosure so only the short description is loaded until needed. C. Email the procedure to everyone. D. Paste it into each conversation by hand. Correct answer: B Explanation: Skills load details on demand, keeping context small and sharing consistent procedures. Why not the others: A bloats context; C and D are manual. Architectural principle: Progressive disclosure for reusable procedures. Ref: Agent Skills docs
Q149 · D7 · Objective: Establish developer workflows with AI assistance · Difficulty: Intermediate
Scenario: A team wants a deterministic action every time the agent edits a file, such as running the formatter, which must not depend on the model remembering. Question: Which feature is most suitable? A. A hook configured to run on the relevant tool event. B. A line in CLAUDE.md asking nicely. C. A reminder in chat. D. A weekly manual run. Correct answer: A Explanation: Hooks run deterministically at lifecycle events. Why not the others: B and C depend on model compliance; D is not per-edit. Architectural principle: Use deterministic mechanisms for guaranteed behavior. Ref: Claude Code docs: hooks
Q150 · D7 · Objective: Create operational runbooks and support processes · Difficulty: Advanced
Scenario: Leadership asks how to know whether the AI-assisted workflow improves engineering outcomes, without incentivizing gaming. Question: Which approach is best? A. Count lines of code generated. B. Track balanced outcome measures (cycle time, review rework, defect escape rate, developer satisfaction) against a pre-adoption baseline, and review them with qualitative feedback. C. Count prompts per developer. D. Rely on anecdotes. Correct answer: B Explanation: Balanced outcome metrics against a baseline show real impact and resist gaming. Why not the others: A and C measure activity; D lacks rigor. Architectural principle: Measure outcomes, not activity. Ref: Prep Lesson 5