Claude Certified Architect Foundations Practice Exam Questions and Answers – Part 5/8

Answer: C. Run an agentic loop that inspects stop_reason, executes requested tools, appends tool results, and repeats until end_turn.

Implementing the core agentic loop lets Claude inspect the stop reason, execute requested tools, and append results until the turn naturally ends. Templatized responses fail because they bypass the model's reasoning capabilities over newly acquired tool context.

Answer: A. Retry with the source document, rejected extraction, and exact validator messages, instructing Claude to produce a corrected record only.

Providing the source document, the rejected extraction, and exact validator messages supports targeted self-correction. Asking the model to fix errors without the original text forces it to guess the correct values, leading to plausible but unsupported hallucinations.

Answer: B. Have subagents report successful empty searches separately from access failures, including attempted paths, queries, partial results, and suggested next steps.

The correct answer ensures subagents explicitly differentiate between a successful search with no matches and a failed search due to access errors. A practical exam cue is to select the option that maximizes error visibility and context recovery, avoiding silent failures where missing data mimics clean results.

Answer: C. Pass the relevant current test files into the review context and ask Claude to target only uncovered behaviors.

Providing existing test files gives Claude the necessary context to identify actual coverage gaps instead of suggesting redundant tests. Adding a prompt rule without context fails because Claude cannot know existing coverage without seeing the tests.

Answer: C. Return error details that include failure type, attempted order lookup, partial customer data, cached summaries, and suggested fallback actions.

Returning detailed error context enables the coordinator to distinguish isolated failures from total outages, allowing safe usage of cached data. Converting timeouts to empty results is a strong distractor because it masks actual errors and risks processing incomplete backend states.

Answer: C. Commit project-level CLAUDE.md guidance describing valuable test criteria, fixture conventions, and reusable helpers for CI-invoked Claude Code.

Committing project-level guidance ensures Claude Code consistently loads team preferences from ephemeral CI runners. Local configurations are a strong distractor because ephemeral environments lack access to maintainer laptops, making prompt-only adjustments ineffective for persistent context.

Answer: D. Rewrite the MCP tool descriptions to detail support-specific capabilities, accepted identifiers, returned fields, and when to use them instead of generic search.

Rewriting MCP tool descriptions gives Claude the precise context needed to prefer specialized tools over generic file searches. Disabling generic file search is a strong distractor because it removes useful agent flexibility instead of addressing the underlying tool selection signal.

Answer: C. Use plan mode to investigate dependencies and choose the migration path, then switch to direct execution for the agreed edits.

The correct answer uses plan mode to map dependencies safely before switching to direct execution for mechanical edits. When tackling workflow questions, remember that staying in plan mode for mechanical execution wastes time, while direct execution risks costly rework during discovery.

Answer: B. Route all subagent requests and results through the coordinator, which records context, errors, and final resolution inputs.

Routing communication through the coordinator preserves specialization while giving one component responsibility for observability, error handling, and final aggregation. This directly addresses the missing retry rationale and bypassed escalation notes because all handoffs become visible to the coordinator.

Answer: B. Have the coordinator assign each subagent a distinct concern and shared verified facts, then combine findings into one customer response.

Having the coordinator assign distinct concerns and shared facts keeps subagents focused on their specialization without redundant tool calls. Allowing direct messaging bypasses centralized observability, which often leads to missed issues and overlapping summaries during complex investigations.

Answer: D. Assign a stable custom_id derived from each document record, persist it with request metadata, and reconcile results using that identifier.

Message Batches support request and response correlation through custom_id values. Persisting a stable identifier with the submitted request lets the ingestion job map results correctly, whereas relying on output ordering fails when responses are processed after retries or partial failures.

Answer: B. Drive the loop from stop_reason, execute requested tools when it is tool_use, and return only when it is end_turn.

The agentic loop should be driven by stop_reason, executing tools when it equals tool_use and returning when end_turn occurs. Stopping the loop based on natural language text is fragile because Claude often outputs text alongside tool calls before actually finishing.

Answer: A. Move the accessibility guidance into a .claude/rules/ file with YAML frontmatter paths matching React component globs.

Path-specific rule files allow Claude Code to load guidance only when file paths match the declared glob patterns. Using generic root instructions or manual commands fails because it relies on the model correctly guessing file contexts rather than applying deterministic system rules.

Answer: A. Route every subagent handoff and result through the coordinator, which aggregates state, applies escalation rules, and delegates follow-up work.

A coordinator-controlled hub-and-spoke pattern preserves observability, consistent error handling, and controlled information flow across specialized subagents. Letting subagents communicate directly bypasses central escalation rules and creates blind spots in the execution trace.

Answer: D. Populate escalate_to_human with a structured handoff including customer ID, verified facts, root cause, amounts, attempted actions, and recommended next steps.

Structured escalation handoffs are essential when the human reviewer lacks access to the original conversation or tool outputs. The agent should send a compact, explicit payload including identifiers, verified facts, and recommended next steps. Relying on transcript links fails when reviewers lack system access.