Claude Certified Architect Foundations Practice Exam Questions and Answers – Part 21/24

Answer: B. Set tool_choice to {"type": "any"} while providing all extraction tools.

Setting tool_choice to any forces Claude to use one of the provided tools, resolving the conversational-summary failure mode. Auto allows conversational responses, while forcing a specific schema breaks extraction when the document type is unknown.

Answer: B. Declare a client extraction tool with an input_schema for the release note fields, require that tool call, and read the tool_use input object.

Declaring an extraction tool with a JSON schema ensures Claude emits structured arguments in a reliable tool_use block. Parsing raw assistant text often fails because the model might include unwanted conversational commentary before the data.

Answer: B. Continue the loop whenever stop_reason is "tool_use", return matching tool_result blocks, and use the response only when stop_reason is "end_turn".

The client tool loop must continue whenever stop_reason is tool_use, returning matching tool_result blocks. Treating a tool_use response as the final answer breaks the execution chain and causes the agent to miss required steps.

Answer: C. Start Claude Code in plan mode, have it inspect the affected areas, review the proposed plan, then approve an editing mode.

Plan mode lets Claude research dependencies and propose a design before modifying source files. For risky migrations, starting in an editing mode like acceptEdits often causes broad, unintended rewrites that require costly rework.

Answer: B. Add an application-level gate that blocks submit_record unless validate_record has succeeded for the same record.

Adding an application-level gate enforces the required validation step before submission, making the workflow deterministic. Relying on system instructions is unreliable because the model might still attempt to guess values and submit prematurely.

Answer: A. Define a strict client tool for the resolution record with an input_schema and force that tool with tool_choice.

Strict tool use constrains the output to the declared schema, guaranteeing valid JSON. Forcing the tool call via tool_choice prevents Claude from falling back to free text, which easily breaks parsing when models add conversational prose around raw JSON payloads.

Answer: B. Route follow-up work through the coordinator and require subagents to return structured final results for any additional delegation.

The coordinator pattern keeps the parent agent as the single control point for task routing and error handling. Letting subagents message each other directly creates circular dependencies and hidden state changes that make debugging and provenance tracking nearly impossible.

Answer: B. Route each request through a coordinator step that selects only the specialists whose descriptions match the current issue.

A routing coordinator analyzes the request and delegates only to relevant specialists. This prevents context window pollution from unnecessary account-recovery details while maintaining the separation of concerns needed to resolve ambiguous billing issues accurately.

Answer: B. Delegate the exploratory search to the built-in Explore subagent with explicit scope and conventions, then implement from its summarized findings.

The Explore subagent runs in a separate context window to handle verbose search operations. It returns a concise summary to the parent conversation, preserving the main context window for the actual implementation work and preventing token limits from losing target schemas.

Answer: A. Route the nightly archive reprocessing through the Message Batches API, and keep interactive validation on synchronous Messages API calls.

The Message Batches API provides significant cost savings for asynchronous workloads that can tolerate delayed processing. Keeping interactive validation on synchronous API calls ensures users receive immediate validation feedback without waiting for batch processing windows.

Answer: A. Keep shared conventions in the root CLAUDE.md and let each package owner add @ imports for only that package's relevant standards in its package CLAUDE.md.

Layering root instructions with package-level configurations uses the import feature to load only relevant domain standards automatically. When Claude Code starts in a package directory, it reads the local files and ancestors without loading sibling package configurations, preventing context bloat.

Answer: B. Add allowed-tools: Read Grep Glob to the skill's SKILL.md frontmatter.

The allowed-tools field in the SKILL.md frontmatter enforces hard execution limits at the system level. Relying on prompt instructions to avoid edits is a soft constraint, whereas explicitly listing read-only tools guarantees the skill cannot modify files or run shell commands.

Answer: D. Require field-level confidence outputs and calibrate review thresholds using labeled validation examples.

Field-level confidence allows routing only the riskiest parts of a generated change to human reviewers. Aggregate acceptance rates hide specific failures, so you must calibrate against a labeled validation set to turn raw scores into a reliable gating signal.

Answer: D. Update the tool and field descriptions with accepted input formats, example queries, edge cases, and usage boundaries.

Tool descriptions and field descriptions are the strongest levers for helping Claude choose and call tools reliably. Forcing tool use or routing more traffic would only increase incorrect calls, so you must clarify acceptable inputs and boundaries directly in the tool metadata.

Answer: C. Run /memory in each affected session and compare the listed CLAUDE.md, CLAUDE.local.md, user-level, and managed policy memory files.

Running the /memory command explicitly lists all active CLAUDE.md and policy files loaded for the current working directory. If the package-specific file is missing from this list, the model cannot see those instructions, which immediately explains the inconsistent behavior.