Claude Certified Architect Foundations Practice Exam Questions and Answers – Part 13/16

Answer: D. Add an orchestration-level prerequisite that rejects report-generation delegation until required results and source mappings are present.

An orchestration-level prerequisite reliably enforces workflow ordering by checking shared state before allowing downstream delegation. Prompt instructions are probabilistic and can be ignored, making them insufficient for mandatory dependency checks between subagents.

Answer: D. Configure a PreToolUse hook for the publishing tool that blocks calls missing the required citation manifest.

A PreToolUse hook intercepts the tool call before execution, providing deterministic enforcement to block unauthorized side effects. A PostToolUse hook fires after execution completes, meaning the draft would already be published before the check could reject it.

Answer: D. Provide the missing methodology sources, and allow an unavailable value when no cited source is in context.

The extraction failed because the methodology information was completely absent from the provided context. Structured output and strict tool use enforce schema compliance for existing text, but they cannot manufacture missing facts or recover unread documents.

Answer: C. Add a PreToolUse hook for Bash that rejects publishing commands missing an approved ticket ID.

A PreToolUse hook intercepts Bash commands before execution, deterministically blocking publishing commands that lack a ticket ID. Relying on context rules or few-shot examples remains probabilistic and cannot guarantee that unauthorized commands are prevented.

Answer: B. Append the assistant tool_use response, then send one following user message containing both tool_result blocks matched by tool_use_id.

The application must preserve the assistant turn containing the tool use requests, then return the outputs as tool result blocks in the next user message. Matching each result to its original tool use ID ensures Claude correctly interprets the execution feedback.

Answer: D. Add diverse few-shot examples that show issue and non-issue reviews, with brief reasoning that marks the decision boundary.

Providing diverse few-shot examples teaches Claude the underlying judgment pattern rather than just memorizing surface wording. Including both issues and non-issues establishes clear decision boundaries, helping the model apply the criteria accurately to novel refactors.

Answer: D. Update the lookup tool description to require clarification when multiple candidate tickets are returned.

Updating the tool description to require clarification makes the ambiguity explicit to Claude. Selecting the newest or highest-ranked ticket relies on risky heuristics, whereas asking for a unique identifier guarantees the correct ticket is targeted.

Answer: D. Move a concise findings-and-source map to the start of the synthesis prompt and keep detailed evidence under labeled sections.

Moving a concise findings map to the start directly mitigates the lost-in-the-middle effect where models ignore buried details. Simply increasing output length or adding reminders addresses adjacent symptoms without fixing the core context positioning problem.

Answer: D. Return a tool_result with is_error: true and JSON content containing errorCategory, isRetryable, a clear message, and a suggested valid key format.

Returning a tool result with is_error true and structured JSON provides the exact recovery metadata needed. Generic failures do not give Claude enough context to correct the malformed input and retry successfully.

Answer: C. Add 3 to 5 relevant, diverse, structured examples showing varied source formats and the expected extracted output.

Adding diverse few-shot examples teaches Claude the extraction patterns needed across varied document structures. Simply lowering temperature or demanding no nulls does not solve the core comprehension gap when parsing tables and release notes.

Answer: B. Add a PreToolUse command hook for Bash that validates target paths and blocks out-of-workspace commands with feedback.

A blocking PreToolUse hook enforces the workspace boundary deterministically before the Bash command executes. PostToolUse hooks or system prompts react after the fact, which violates the strict requirement to stop out-of-workspace actions before they run.

Answer: C. Have the main agent spawn the reviewers with Agent, pass each reviewer its needed context, collect summarized results, and synthesize follow-ups centrally.

Claude Code subagents run in isolated context windows and return summarized results to the caller. Keeping synthesis and routing in the main agent matches the documented hub and spoke pattern, avoiding the pitfalls of cross-chatting subagents.

Answer: D. Re-add the server with –scope project and commit the generated .mcp.json using environment-variable placeholders.

Project scope writes an MCP server configuration file to the repository root for easy team sharing. Using environment variable placeholders inside this file keeps sensitive credentials out of source control while standardizing the setup across user machines.

Answer: C. Turn the workflow into a prompt template, run representative edge-case evals with the same structured-output request shape, refine and re-run the prompt, then batch only after a synchronous dry run succeeds.

Running representative edge-case evaluations addresses both quality and parsing issues before submitting large batches. Relying solely on strict schema validation or blind prompt improvements ignores real-world failures that a synchronous dry run easily catches.

Answer: D. Use explicit prompt chaining with file-level review calls, then run a separate integration call over the local findings.

Explicit prompt chaining breaks the review into smaller, inspectable steps, which reduces attention dilution from large contexts. A final integration call focuses on cross-file consistency after each file receives dedicated local analysis.