Claude Certified Architect Foundations Practice Exam Questions and Answers – Part 19/20

Answer: B. Run a prompt chain that reviews files in focused passes, then runs a separate integration pass over the collected findings.

A prompt chain reduces attention dilution by reviewing files in focused passes before running a dedicated integration pass. Running independent reviewers without a synthesis step fails because no one reconciles the cross-file findings.

Answer: A. Commit a .mcp.json file that references Bearer ${GITHUB_TOKEN} in headers, and set GITHUB_TOKEN in each CI and developer environment.

Project scoped configuration belongs in the tracked file while environment variables keep secrets out of version control. Option C fails because Claude Code requires the specific variable syntax to expand headers properly during the connection.

Answer: C. Run an interactive planning session where Claude uses AskUserQuestion, writes a self-contained SPEC.md, then implement it from a fresh session.

Holding an interactive planning session lets Claude ask clarifying questions and produce a self-contained specification before any code is written. Avoid jumping straight into implementation for ambiguous features, because starting a fresh session from a detailed spec keeps execution focused.

Answer: A. Configure a maintained Jira MCP server for Jira operations, and implement a custom MCP server for the release-readiness workflow.

Using a maintained Model Context Protocol server for standard tools reduces integration debt, while building a custom server encapsulates complex private business logic. Avoid hardcoding REST procedures via Bash, because standard servers provide a much cleaner and more maintainable interface.

Answer: A. Track precision and recall by category, then tighten or disable the noisy style criteria using flagged and non-flagged examples.

Tracking precision and recall by category isolates the noisy style criteria responsible for eroding developer trust. A strong exam cue is to avoid aggregate metrics here, because an overall acceptance rate hides the specific category causing false positives.

Answer: A. Resume the baseline session with the SDK fork option enabled for each strategy, then track the new session IDs.

Forking a specific session creates a new branch that starts with a copy of the original history, leaving the baseline unchanged. Remember that simply resuming normally modifies the tracked history, whereas forking is the explicit mechanism for isolated branching.

Answer: D. Add context: fork in SKILL.md and keep the audit as explicit task instructions.

Using the fork context setting isolates verbose discovery work inside a subagent so the main conversation only receives the useful result. Remember that standard compaction or memory instructions do not prevent context flooding the way forking a side task does.

Answer: B. Persist an application-defined JSON state manifest, then load it on restart and inject it into coordinator and subagent prompts.

Persisting an application-defined state manifest and injecting it into the prompts explicitly recovers the verified facts after a crash. Do not rely on local transcript files or session memory for critical recovery, because replacement workers often cannot access them.

Answer: C. Move source-check.md into .claude/commands/ in the repository and commit that file.

Committing the command file inside the project commands directory makes it a version-controlled asset that all teammates receive upon cloning. Personal commands stored in the home directory are always private to the individual user and invisible to the repository.

Answer: C. Create a .claude/rules/testing.md file with paths globs for test files and store the shared testing conventions there.

Using a rules file with path globs ensures these conventions are loaded dynamically only when matching test files are read. A key exam cue is to avoid duplicating instructions in multiple files or placing them globally in the root memory, which wastes context.

Answer: A. Define testable report and skip rules that focus comments on production bugs, security flaws, broken edge cases, and subtle regressions.

Defining strict report and skip rules creates clear category boundaries, filtering out subjective stylistic feedback in favor of high-impact bugs. Requiring numerical confidence scores fails because it still leaves the model trying to quantify inherently subjective stylistic opinions.

Answer: B. Create .claude/skills/case-review/SKILL.md with context: fork, allowed-tools for Read and Grep, and argument-hint: [case-id].

Claude Code skills require a dedicated folder containing a SKILL.md file to properly register custom workflows and parse YAML frontmatter. Setting context to fork creates an isolated subagent for background note generation, while allowed tools prevents permission prompts and argument hint guides developers.

Answer: C. Add a coordinator step that inspects the case, invokes only needed subagents, and passes each a self-contained task summary.

Introducing a coordinator step allows the system to dynamically route simple requests away from unnecessary specialized subagents, immediately reducing latency. Because subagents operate with isolated context, the coordinator must always pass a self-contained summary to invoke them correctly.

Answer: B. Add 3 to 5 structured examples that map varied guide formats to the expected JSON fields.

Adding diverse few-shot examples directly teaches the model how to map varied input formats like shell blocks and checklists into the required schema. Strengthening the negative instruction alone fails because the model currently lacks the structural mapping needed to extract the values.

Answer: C. Return a CallToolResult with isError: true and include structured failure details in the result content.

Returning a CallToolResult with the error flag set to true explicitly signals an application-level failure to the agent, preventing false success claims. Returning a normal result with an error field risks the model ignoring the structured payload and hallucinating a positive outcome.