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

Answer: C. Run verbose repository discovery in an Explore subagent, returning concise findings before the main CI review produces structured comments.

This isolates the noisy discovery phase from the main review context while still preserving the important conclusions. The main review can then focus on applying judgment and producing actionable findings instead of carrying every intermediate search result and file excerpt.

Answer: A. Change intermediate handoffs so each extracted fact carries its source document, location, and supporting excerpt into final synthesis.

This preserves provenance at the same granularity as the extracted information, so downstream systems can trace each final field back to supporting evidence. It directly addresses the failure introduced by compression, where a summary keeps the conclusion but drops the source relationship needed for auditability.

Answer: C. Add targeted examples showing varied existing test structures and genuine gaps, including why each should be reported or skipped.

Targeted examples teach the model how to interpret ambiguous coverage evidence across different test organization patterns. Showing both acceptable existing coverage and genuine gaps helps the model generalize judgment instead of assuming unfamiliar test structures represent missing tests.

Answer: D. Start a new session, provide a structured summary of durable findings, and explicitly identify changed sources for fresh analysis.

Starting fresh avoids carrying forward stale tool results that remain embedded in the prior conversation context. A structured summary preserves durable decisions and research scope while forcing current sources to be reloaded and reanalyzed, rather than hoping the model ignores old data.

Answer: B. Have each subagent export structured state to a known location; the coordinator reloads and injects it when resuming.

Exporting structured state creates an explicit recovery mechanism independent of fragile conversational memory. On the exam, remember that asking Claude to reconstruct progress from transcripts is an anti-pattern; externalizing state is required for reliable agent resumption.

Answer: D. Return errorCategory and isRetryable per failure, marking permanent source issues non-retryable and transient timeouts retryable with clear messages.

Structured retry metadata allows agents to distinguish transient failures from permanent roadblocks. Marking permanent conditions as non-retryable prevents wasted latency, whereas asking the coordinator to infer retryability from prose introduces brittle natural language parsing.

Answer: A. Include the relevant verified customer facts, order details, and prior tool outputs directly in every delegated Task prompt.

Subagents operate with isolated context, meaning they only process information explicitly passed during invocation. Injecting verified facts and tool outputs directly into the task prompt guarantees accurate analysis, whereas relying on session memory or heuristic selection causes failures.

Answer: B. Use stratified random sampling across issue type, order age, seller channel, and resolution action for high-confidence auto-closures.

Stratified random sampling guarantees that rare but critical segments are represented in the review set. This allows you to measure hidden error rates in high-confidence closures, whereas simply increasing the uniform sample size or skipping high-confidence cases hides edge case failures.

Answer: C. Have each exploration subagent write key findings to scratchpad files at known paths, and require later prompts to reference them.

Writing key findings to scratchpad files creates durable state outside of noisy conversational context. Requiring later prompts to reference these files ensures exact knowledge reuse, whereas increasing the token budget fails to prevent degraded memory and hallucinations.

Answer: A. Run Claude Code with the -p or –print flag so it processes the prompt and exits after output.

Claude Code runs interactively by default, waiting for further input which causes CI timeouts. The dash p or print flag forces the script to process the prompt and exit immediately, whereas appending prompt instructions to avoid follow-up questions is unreliable.

Answer: D. Add explicit fallback enum values with companion detail fields so uncertain or novel categories are captured without forced misclassification.

Adding explicit fallback enum values with companion detail fields preserves schema validity while safely capturing uncertainty. This prevents semantic misclassification, whereas endlessly expanding enums or using free text degrades downstream reliability and breaks constraints.

Answer: A. Redesign the schema so unavailable source-dependent fields are nullable or optional, with instructions to return null unless directly evidenced.

Making source-dependent fields nullable directly addresses hallucination by allowing the model to represent missing information. Relying solely on stronger prompt wording often fails to prevent fabricated values when strict schema constraints force an output.

Answer: C. Generate a structured handoff with research topic, disputed claims, source citations, analysis performed, and recommended reviewer decisions.

A structured handoff gives the human reviewer the context needed to continue from the system's work instead of restarting the investigation. It captures the unresolved decision point, supporting evidence, prior analysis, and recommended next steps in a compact, actionable format.

Answer: A. When the API response has stop_reason tool_use, execute all tool_use blocks, append matching results, and continue until end_turn.

Executing all tool use blocks implements the agentic loop around the model's explicit control signal rather than assuming a single tool per response. Returning all matching results lets the coordinator reason over complete subagent outputs before synthesis.

Answer: C. Add a tool call interception hook that blocks process_refund above $500 and returns guidance to call escalate_to_human.

A tool call interception hook provides deterministic enforcement before the financial operation executes. It preserves normal autonomous refunds under the threshold while preventing policy-violating calls and redirecting the workflow to escalation.