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

Answer: A. Temporarily omit the noisy category from the active prompt, keep accurate categories enabled, and rebuild it with examples, definitions, and precision/recall evals.

Temporarily removing the noisy category immediately restores trust in the automated pipeline while keeping the accurate signals active. Rebuilding the prompt with positive and negative examples alongside precision metrics addresses the underlying classification failure directly.

Answer: D. Send an immediate tool_result for that tool_use_id with is_error true and the concrete validation failures.

Returning a tool result with the error flag set provides the exact validation failures needed for correction. Specific feedback is far more effective than generic prompt tweaks or random temperature retries.

Answer: B. Resume the saved session ID with the fork option for each attempt, and checkpoint files before edits.

Forking a saved session creates separate histories from the same baseline without altering the original. Since a session is not a filesystem snapshot, checkpointing files ensures safe reversion for overlapping edits.

Answer: C. Use Grep for refund and escalation identifiers, then Read only matching files and follow imports from those entry points.

Using Grep to search for identifiers and then reading only the matching files builds understanding incrementally. This prevents context bloat better than reading entire directories or pasting raw search outputs.

Answer: B. Add 2-4 tagged examples showing similar ambiguous requests, the selected response path, and concise reasoning against plausible alternatives.

Tagged few-shot examples teach the model the exact decision boundary for ambiguous requests. Explicit reasoning alongside these examples resolves judgment calls better than long written checklists.

Answer: B. Run each requested Task tool call, send matching tool_result blocks, and keep calling the Messages API until stop_reason is end_turn.

The agent loop must execute requested tools and return their results before continuing. A tool use request is not a final answer, so the coordinator stops prematurely if the loop lacks result handling.

Answer: B. Add per-field confidence, ambiguity, contradiction, and evidence-excerpt fields to the JSON schema, then queue flagged records before clean records.

Defining explicit application-level signals for ambiguity and contradiction catches the specific failure modes that a successful stop reason cannot detect. On the exam, remember that model generation metadata like stop reason or logprobs is never a safe substitute for validating structured extraction logic.

Answer: D. Separate review and test-generation steps, expose only role-specific tools to each step, and force the review step's reporting tool with tool_choice.

Separating the steps and restricting tool access ensures the review phase only sees its specific reporting tool, preventing irrelevant actions. For the exam, remember that setting tool_choice to a specific named tool is the safest way to force structured output.

Answer: A. Enter plan mode, have Claude inspect the affected areas, and review the proposed plan before choosing execution mode.

Plan mode directly separates codebase exploration from actual edits, allowing Claude to propose an approach without risking unintended changes. For large migrations, starting in bypass permissions or accept edits risks immediate regressions before the maintainers even approve a design.

Answer: C. Submit accumulated requests every 4 hours, using custom_id to correlate each case outcome.

A thirty-hour service level agreement paired with a twenty-four-hour maximum batch window leaves only six hours for safe accumulation. Submitting every four hours keeps the worst-case timeline within the strict audit limit while providing a crucial two-hour safety buffer.

Answer: C. Create a Markdown rule file under .claude/rules/ with YAML frontmatter using paths glob patterns for the test file names.

Using path-specific rule files applies instructions only to matching files. This targets conventions precisely, whereas root or user-level files apply globally and load unnecessary context for production files.

Answer: A. Have the subagent retry transient command failures locally, then return attempts, partial findings, and unresolved errors in its final result.

A subagent should retry transient failures locally and summarize partial findings in its final result. This isolates messy command logs from the parent context while preserving useful details for planning.

Answer: B. Add REVIEW.md guidance that uses prior findings during re-reviews and reports only new or still-unresolved issues.

Configuring review guidance ensures the system uses prior findings during re-reviews. This prevents duplicate comments by shaping behavior directly, rather than relying on manual cleanup by maintainers.

Answer: C. Use batch for initial analysis or tool requests, then execute returned client tools and continue each case in later Messages requests.

Batch processing is asynchronous and cannot execute client tools directly. The batch should perform initial analysis, then your application handles the tools and continues in standard requests.

Answer: D. Run the SDK-driven agent loop so each MCP tool invocation is dispatched, results are returned, and processing continues until a final response.

The agent runtime must dispatch tool requests and return observations until the model finishes. Claude cannot execute backend operations itself, so a missing runtime loop causes the session to halt prematurely.