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

Answer: B. Return structured MCP errors with categories, retryability, and user-safe details so the agent can choose recovery, clarification, or escalation.

Returning structured MCP errors with categories and retryability gives the agent the exact context needed to choose appropriate local recovery steps. Uniform failure text forces the model to guess, causing unnecessary escalations and frustrating retries on non-retryable failures.

Answer: C. Use plan mode to map relevant flows and compare implementation points before allowing file modifications.

Using plan mode lets the agent map complex flows and identify the correct abstraction layer before modifying files. Proceeding with direct execution relies on trial and error, which risks breaking shared dependencies and causes avoidable rollback work on legacy systems.

Answer: B. Run a representative pilot batch, analyze validation failures and null patterns, refine the prompt, then submit the full workload.

Running a representative pilot batch exposes real formatting variations and failure modes before they impact the full workload. Refining the prompt based on pilot validation results maximizes first-pass success, whereas bulk submission or increasing max_tokens ignores underlying template issues.

Answer: B. Send a follow-up request containing the source document, failed extraction, and precise validator messages for targeted correction.

Targeted correction feeds specific validator feedback back to the model, directly addressing the defect. Loosening the schema weakens validation, while blind retries lack the context needed to fix semantic errors.

Answer: D. Add a PostToolUse hook that converts each tool result into canonical dates, status labels, and tier fields before Claude sees it.

A PostToolUse hook deterministically normalizes tool outputs before the model reasons over them. Relying on prompt instructions to translate formats is fragile and risks hallucinations during complex support cases.

Answer: B. Analyze each source in a focused pass with structured findings, then run a separate cross-source integration pass before reporting.

Separating local analysis from cross-source synthesis uses prompt chaining to reduce attention dilution. A dedicated integration pass resolves contradictions and preserves caveats before report generation begins.

Answer: A. Run a separate Claude review instance with the source document, extracted fields, and rubric, excluding the original extraction reasoning.

A separate review instance prevents the model from inheriting assumptions from the original extraction rationale. Self-critique in the same conversation often reinforces prior reasoning instead of objectively catching subtle placement errors.

Answer: B. Add targeted examples showing complete actionable findings with document location, affected field, issue description, severity, and suggested correction.

Targeted few-shot examples teach the exact structure and specificity required for actionable reviewer notes. General instructions alone fail because they lack the concrete formatting needed to ensure consistent downstream ticketing.

Answer: C. Have subagents report unresolved failures with attempted section, failure type, partial fields, and recovery suggestions for coordinator handling.

Reporting failures with recovery suggestions lets the coordinator handle errors without discarding successful partial work. Returning empty objects is an anti-pattern because it falsely masks unresolved failures as successful extractions.

Answer: B. Add a detected_pattern field to each structured finding, then analyze dismissal rates by pattern during feedback review.

A structured pattern field preserves the specific source construct or extraction trigger behind each finding. When reviewers dismiss findings, the team can aggregate by pattern and identify which prompts, schemas, or validations need improvement.

Answer: D. Resume the session, identify the changed policy and tool files, and request targeted re-analysis before continuing implementation decisions.

Resuming the session preserves useful investigation context while explicitly invalidating parts likely to be stale. Targeted re-analysis lets Claude refresh its understanding of the changed policy and tool schema before continuing implementation decisions.

Answer: D. Assign each subagent a distinct issue boundary and shared case facts, then synthesize their non-overlapping findings centrally.

Assigning distinct boundaries and shared facts leverages parallel specialization without redundancy. On the exam, remember that uncontrolled subagent messaging or broad prompts cause overlapping loops and conflicting recommendations.

Answer: A. Return MCP tool errors with isError plus category, retryability, and safe messages distinguishing transient, validation, business, and permission failures.

Categorized tool errors give the agent signals to choose appropriate recovery paths like retrying timeouts or clarifying invalid inputs. Generic error messages fail because they force the model to guess recovery steps blindly.

Answer: A. Include verified customer identity, relevant order records, prior findings, and exact investigation goal in each subagent prompt.

Passing verified identity, relevant data, and the exact goal directly in the prompt gives subagents the context they need to act accurately. Subagents do not automatically inherit the parent conversation history or prior tool results.

Answer: A. Add a coordinator-side prerequisite that blocks report-generation Task calls until synthesis returns a structured citation manifest and success status.

Enforcing a deterministic prerequisite ensures the report agent cannot start until synthesis provides a structured manifest. Relying on the report agent to guess if synthesis completed creates fragile workflows and risks generating incomplete reports.