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

Answer: A. Organize conclusions by evidentiary status, retaining source characterization and methodological context for each major claim in the final report.

Organizing conclusions by evidentiary status preserves uncertainty by making the strength of evidence visible to readers. Separating stronger conclusions from tentative ones prevents the report from flattening source quality into a single authoritative narrative.

Answer: D. Have the coordinator issue separate Task calls for independent research branches in one response, then aggregate their returned findings before synthesis.

Independent subagent work can be launched concurrently when the coordinator emits multiple tool calls in the same response. This preserves the coordinator as the aggregation point while reducing wall-clock time for branches that do not depend on each other.

Answer: D. Create separate fork_session branches from the completed analysis baseline, develop each framing independently, then compare outputs through the coordinator.

Forking from a shared baseline preserves the same verified starting context while isolating divergent exploration paths. This fits the need to compare independent approaches without allowing assumptions from one branch to contaminate the other.

Answer: C. Use Glob with targeted filename patterns, then Read only matching policy and test files before editing.

Using Glob is the appropriate technique when the selection criterion is a specific file path or naming pattern. It narrows the search space before reading files, which avoids loading unrelated repository content into context unnecessarily.

Answer: A. Run Claude Code with claude -p "Review the changed files for security regressions" so it prints output and exits.

The print flag is the documented way to run the CLI in non-interactive mode for automation pipelines. It processes the prompt, writes the response to standard output, and exits instead of opening an interactive session that halts the CI job.

Answer: D. Split the request into distinct industry and jurisdiction workstreams, pass shared scope definitions, investigate in parallel, then synthesize one report.

Splitting the request into distinct workstreams gives each subagent a focused slice of the prompt while preserving shared constraints. Parallel investigation improves coverage, and the final synthesis step resolves overlaps into a unified report rather than fragmented outputs.

Answer: D. Create a targeted test suite for expected behavior and edge cases, then iterate by feeding Claude the specific failing results.

Creating an executable test suite establishes an objective feedback loop for the model. Vague prompts like asking to be exhaustive lack measurable targets, whereas feeding exact failing test results directs the model to make targeted corrections.

Answer: D. Load the full file with Read, identify the intended refund block, then Write the complete corrected file.

Reading the full file provides necessary context when an edit operation fails due to duplicate code blocks. Writing the complete corrected file ensures the specific handler updates safely without risking unintended modifications to similar paths.

Answer: C. Have each subagent export structured state to fixed paths, then load a resume manifest into restarted coordinator prompts.

Exporting structured state to fixed paths preserves progress outside the volatile conversation window. Loading this resume manifest allows the coordinator to inject exact handoff details into new prompts, avoiding the token limits of session histories.

Answer: A. Modify upstream subagents to return compact structured records: key facts, citations, relevance scores, and only synthesis-relevant details.

Modifying upstream agents to return compact structured records solves context dilution by reducing token noise. Increasing the context limit fails because the synthesis agent still struggles to track relevant facts buried inside long narratives.

Answer: D. Add targeted examples showing correct extraction from multiple document layouts, including inline citations, appendix tables, and embedded methodology details.

Few-shot examples teach Claude how to map differently placed evidence into the same schema fields across varied layouts. Making these fields required is a risky anti-pattern because it pressures the model into fabricating values when the data is genuinely absent.

Answer: D. Create focused .claude/rules/ files with YAML frontmatter paths globs targeting generated clients, migrations, and frontend files.

Path-specific rule files are designed for conditional convention loading based on file paths. YAML frontmatter paths fields with glob patterns let Claude Code load only the relevant guidance for matching files, reducing irrelevant context and false positive review comments.

Answer: D. Use Read to load the full template, modify the intended section, then Write the complete corrected file back.

When an edit target is not unique, loading the file and rewriting the complete contents is the reliable fallback. As a practical cue, relying on broader text matching or scripting shell commands risks modifying the wrong occurrence and damaging file integrity.

Answer: A. Add a small set of labeled examples showing acceptable unit variants and genuinely ambiguous entries, including expected fields and reasoning.

Few-shot examples are highly effective when a model must distinguish acceptable variations from genuine data issues. Showing both positive and negative cases provides a reliable decision boundary, whereas merely expanding prose rules or increasing thresholds fails to fix core logic.

Answer: D. Replace broad caution language with concrete report and skip criteria for each review category, including representative true-positive and non-issue examples.

Broad caution language fails to define the actual decision boundary for the model. Providing concrete category-specific criteria with true-positive and non-issue examples operationalizes the review process, whereas relying on self-reported confidence scores leaves the judgments noisy.