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

Answer: D. Add a PreToolUse command hook that denies approval commands when the passing artifact is absent.

A PreToolUse command hook runs before execution, providing deterministic control to block forbidden actions. PostToolUse fires too late, while relying on system prompts leaves enforcement up to unpredictable model compliance.

Answer: D. Change the tool wrapper to return compact, review-specific tool_result payloads with only the fields needed.

Tool results consume context window space, so shaping tool output before returning it preserves room for critical evidence. Prompt caching reduces latency, but cached tokens still count against the context limit.

Answer: D. Add an application-side guard that blocks over-threshold process_refund calls and routes the case to escalate_to_human.

The application boundary is the correct place to enforce non-negotiable business rules for client-executed tools. Validating the outgoing tool call before execution deterministically prevents high-impact errors that relying on prompts cannot guarantee.

Answer: B. Sample high-confidence findings within strata for change type, component, language, and finding category, then label errors and novel patterns separately.

Stratified sampling preserves visibility into high-confidence outputs while focusing limited reviewer capacity on meaningful production segments. Sampling by change type or language helps reveal hidden pockets of poor performance that aggregate metrics miss.

Answer: B. Return categorized tool_result errors with retryability, cause, attempted input, and suggested recovery.

Claude reasons directly from tool result content. Categorized errors allow the coordinator to distinguish retryable failures from valid empty results. Masking failures as empty sets removes the context needed for proper recovery.

Answer: C. Add three representative before-and-after examples, including edge cases, in a clearly tagged examples section.

Concrete input and output examples teach the desired transformation boundary much better than prose alone. Plan mode outlines strategy but does not enforce the specific formatting rules needed for consistent transformations.

Answer: D. Run Claude Code with the -p or –print flag and provide the review prompt non-interactively.

The print flag processes a prompt and exits without waiting for terminal input. Configuration files tell Claude what to know but do not prevent unattended pipelines from hanging when the system requests human interaction.

Answer: D. Move topic-specific guidance into Markdown files under .claude/rules/ and add paths frontmatter for rules that apply only to matching files.

Path scoped rules load only when Claude works with matching file patterns preventing deployment noise during test reviews. Imports still expand into context at launch so they organize files for humans without reducing actual context size.

Answer: D. Define a programmatic agents map keyed by subagent type, set each description and prompt, and give the documentation subagent a read-only tools allowlist.

The AgentDefinition uses the map key for routing and the tools field as a strict allowlist. Top level settings auto approve tools but do not restrict the subagent from using others making it unsafe for read only tasks.

Answer: C. Pass each prior subagent's complete structured findings directly into the review synthesis subagent's prompt.

Subagents are isolated instances so you must pass required facts into their prompts explicitly. Inferring details from parent history fails because the synthesis agent lacks access to that earlier conversation context.

Answer: B. Include the changed files, key diff excerpts, failing test output, and review criteria in the subagent prompt.

Non fork subagents start with isolated context so the delegation prompt must carry the necessary facts. Compacting the parent conversation does not pass context down and the agent cannot read transcripts automatically.

Answer: D. Run an explicit prompt chain with source-level review passes, then run a separate integration pass over the reviewed findings.

Prompt chaining creates inspectable intermediate artifacts for logging and dedicated conflict reconciliation. Relying on confidence scores or duplicating overloaded reviewers does not solve the underlying context rot degrading accuracy.

Answer: A. Return an insufficient information result and require a supporting quote before posting the finding.

Returning an insufficient information result correctly handles the missing supporting quote, as the provided source lacks transcript policy. Retrying the prompt cannot create policy evidence that was never supplied in the context.

Answer: A. Return tool results for both calls, flag lookup_order with is_error: true, and continue from partial context.

Flagging the timed-out tool with is_error true preserves the tool result protocol while giving Claude accurate context to escalate or retry. Masking the timeout as an empty list tricks the model into assuming no orders exist, causing flawed logic.

Answer: A. Run independent reviewer agents on section-specific claim-source bundles, then run a separate integration pass for conflicts and coverage gaps.

Running independent reviewer agents on section-specific bundles reduces self-reinforcing context errors. Relying on a single integration pass by the synthesis agent misses cross-section contradictions because it lacks independent verification.