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

Answer: A. Extend the enum with unclear and other, plus a required detail field when other is selected.

Extending the schema with fallback categories handles ambiguous data without breaking validation rules. Forcing existing enum values creates inaccurate reporting, while using unrestricted strings destroys the reliable structure required by downstream systems.

Answer: A. Create a .claude/rules/migrations.md file with YAML paths matching all migration locations and keep the conventions there.

Using a .claude/rules file with YAML path matching correctly applies guidance dynamically based on file locations. Placing everything in the root CLAUDE.md would load irrelevant instructions for every CI run, increasing noise and defeating your targeted scoping goals.

Answer: B. Add a structured field capturing the triggering code pattern, then analyze dismissal rates by that field during prompt iterations.

Capturing the specific code construct that triggered a finding makes false-positive analysis actionable. Aggregating dismissals by this field pinpoints problematic patterns, whereas asking the model to self-report confidence just masks bad logic without providing measurable data.

Answer: A. Configure the skill with context: fork so verbose exploration runs separately and returns only a concise summary.

Configuring the skill with context fork runs the verbose exploration in an isolated sub-agent context. This prevents setup noise from filling the main conversation window, whereas simply instructing the prompt to ignore earlier notes fails to prevent token bloat.

Answer: C. Rewrite the MCP tool description to specify coverage, accepted queries, returned citation metadata, and when agents should prefer it.

Tool descriptions act as the primary routing signal for Claude, so expanding the description clarifies when to use it. Renaming the tool with buzzwords fails to convey actual constraints or output expectations, leaving the agents confused about its intended coverage.

Answer: B. Move narrowly scoped guidance into topic-specific files under .claude/rules/, leaving root CLAUDE.md with only universal CI review principles.

Splitting massive files into focused topic-specific rule files significantly improves maintainability and reduces context noise. Leaving only universal CI principles in the root CLAUDE.md prevents unrelated standards from blending together, whereas broad headings fail to stop bloat.

Answer: B. Add 2 to 4 representative input and ideal output examples showing concise obligations, evidence boundaries, and owner wording.

Few-shot examples are the strongest next step when detailed instructions alone fail to stabilize formatting and actionability. Representative input and output pairs clearly demonstrate exactly how ambiguous source text should be extracted, outperforming rigid word limits.

Answer: B. Create separate issue records after customer verification, investigate independent concerns using shared case facts, then synthesize one customer-facing resolution.

Creating separate issue records preserves boundaries between distinct concerns while utilizing shared verified facts. Synthesizing one unified response resolves the multiple issues cleanly, whereas forcing sequential replies or splitting tickets worsens the customer experience.

Answer: B. Classify missing-baseline failures separately, retry only format or placement errors, and add the baseline artifact before re-extracting.

Retries are useful when the model has the needed information but produced it in the wrong structure or format. When the evidence is absent from the provided context, the correct recovery is to supply the missing source material or classify the case as unresolved rather than asking the model to invent evidence.

Answer: A. Rewrite returns_helper MCP tool description to specify eligibility inputs, returned fields, examples, and boundaries with refund tools.

Tool descriptions are the primary signal Claude uses to decide when and how to call MCP tools. Making the tool's purpose, inputs, outputs, examples, and boundaries explicit directly improves model-driven tool selection without adding brittle orchestration.

Answer: D. Add a tool call interception hook that blocks process_refund above $150 and redirects the case to human escalation.

A tool call interception hook provides deterministic enforcement before the refund action reaches the backend system. This is the right approach when a business rule must be guaranteed rather than merely encouraged through instructions.

Answer: B. Begin with a brief fact-gathering pass, then let the coordinator create targeted follow-up subtasks as tool findings reveal the dispute type.

This matches an open-ended investigation where the correct next steps depend on what is discovered during the case. A lightweight initial pass establishes the facts, then the coordinator can adapt the plan and delegate only the investigations needed for the actual dispute pattern.

Answer: B. Configure the review helper as a skill with context: fork, returning only a concise summary to the main CI review.

Skills can run in an isolated sub-agent context when configured with context fork, which prevents verbose exploratory work from polluting the main conversation. Returning only a concise summary keeps the final review focused on actionable findings while preserving the reusable workflow.

Answer: D. Decompose the request into concern-specific tasks, run relevant subagents in parallel with shared context, then synthesize one integrated report.

A multi-concern request should be split into distinct work items so each concern receives focused investigation. Running independent concerns in parallel improves latency, while shared context and final synthesis preserve coherence across the report.

Answer: C. Use Glob with the known path patterns to enumerate candidate template files, then Read only the selected matches.

This approach uses the purpose-built file path matching tool before consuming file contents. It minimizes context usage by separating file discovery from content inspection, then reading only the files that are actually relevant.