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

Answer: A. Rewrite delegated prompts to state the support objective, known context, quality criteria, constraints, and required structured return format.

Subagents perform better when they understand the objective, constraints, and required return format rather than following brittle procedural scripts. Expanding step-by-step branches fails because it cannot anticipate every edge case, whereas goal-oriented prompts allow dynamic tool adaptation.

Answer: C. Grant the refund-policy subagent scoped access to lookup_order, while keeping process_refund and escalation routed through the coordinator.

Granting scoped read-only tool access to specialized subagents reduces latency without compromising safety or central oversight. Giving the subagent state-changing tools would violate least privilege principles and bypass the coordinator's ability to handle sensitive actions reliably.

Answer: C. Add enum values for ambiguous cases and a fallback category paired with a required free-text detail field.

Adding fallback enum values alongside a required free-text detail field preserves stable machine-readable categories without forcing inaccurate classifications. Unrestricted strings break downstream analytics, while closed enums force inaccurate predictions when handling unexpected inputs.

Answer: C. Detect source absence after validation, stop automated retries, mark extraction incomplete, and request the missing approval letter.

Retries cannot recover facts that are absent from the provided source context. Marking the extraction incomplete and requesting the missing approval letter prevents unsupported hallucinations from entering downstream systems, which is a core architectural principle.

Answer: D. Break down validation results by artifact category and generated field, then reduce review only for consistently reliable segments.

Aggregate acceptance rates can mask weak performance in specific artifact categories or fields. Segmenting validation results by artifact type allows you to reduce human review safely only where consistency is proven, rather than trusting uncalibrated global confidence scores.

Answer: A. Require each extracted obligation to carry source identifiers and excerpts, then merge duplicates while retaining every supporting reference.

The correct answer preserves data provenance by attaching source identifiers and excerpts to each extracted obligation, enabling safe consolidation. A strong exam cue is to always look for the option that maintains verifiable audit trails while allowing downstream data merging. Batch-level metadata lacks granular tracing.

Answer: B. Rewrite the review prompt to report demonstrable bugs, security risks, and test gaps, while skipping stylistic preferences without documented impact.

The correct answer aligns the prompt with objective issues like bugs and security risks, successfully filtering out subjective noise. When tackling CI integration questions, always prioritize options that narrow the evaluation scope to actionable, demonstrable problems over mere threshold adjustments.

Answer: A. Create a repository rule file with YAML path globs matching component and story files, then remove duplicated directory instructions.

The correct answer uses path-scoped repository rules to apply conventions dynamically based on file globs, eliminating drift from duplicated files. Root configurations require manual slicing, whereas custom commands fail if developers forget to invoke them during active development.

Answer: D. Have Claude maintain a repository scratchpad file recording discovered schemas, validators, edge cases, and file paths for future reference.

The correct answer uses a persistent scratchpad file to retain key architectural discoveries outside the volatile session context. When evaluating context degradation fixes, avoid relying on conversation compression tools, as these often omit critical implementation details needed for later success.

Answer: A. Use Glob with targeted filename patterns to list candidate policy and refund test files, then Read only the relevant matches.

Glob is the appropriate built-in tool when the selection criterion is a file path or filename pattern rather than file contents. Listing candidate paths first keeps context focused and avoids loading unrelated files before Claude knows which files matter.

Answer: A. Resume the named session, identify the changed policy and tool-schema files, and request targeted revalidation before implementing fixes.

Resuming the session while revalidating changed files preserves useful investigation context and explicitly corrects stale assumptions. Asking for a single confidence score is a fragile cue because it lacks deterministic file verification, which might lead to implementing fixes based on outdated schemas.

Answer: D. Add a PostToolUse hook that transforms lookup_order outputs into a canonical support-case structure before Claude receives them.

A PostToolUse hook intercepts tool results and transforms them into a canonical structure before the model reasons over them. Expanding the system prompt with regional mappings relies on probabilistic model compliance and increases context burden, whereas the hook centralizes normalization deterministically.

Answer: A. Temporarily suppress the ambiguous payment terms category while refining its criteria and examples before re-enabling it.

Temporarily suppressing the noisy category targets the specific issue damaging reviewer trust without weakening accurate finding categories. Raising global confidence thresholds or adding broad conservative instructions reduces the visibility of accurate findings, worsening overall system reliability.

Answer: A. Expose the read-only policy, reason-code, and queue catalogs as MCP resources, while keeping customer-changing operations as tools.

MCP resources are appropriate for read-only catalogs that provide context about available data or policy options. This reduces exploratory tool calls while preserving tools for model-driven actions such as looking up orders, processing refunds, or escalating cases.

Answer: D. Add Task to coordinator allowedTools and invoke specialists through it, while keeping backend MCP tools scoped to appropriate agents.

In the Agent SDK, a coordinator invokes subagents through the Task tool, so allowedTools must include Task. Prompting the coordinator to mention specialist names is only natural-language guidance, not a real subagent invocation, and granting broad tool permissions breaks least privilege.