Claude Certified Architect – Foundations: Exam Prep Guide

About This Guide

This guide is compiled from a detailed Q&A thread analyzing exam-style questions for the Claude Certified Architect – Foundations certification. It breaks down multi-agent architectures, context management, tool design, and batch processing principles, focusing heavily on architectural tradeoffs and best practices over raw prompt engineering.

How the Exam Works

The Claude Architect Foundations exam tests your ability to design resilient, production-ready AI systems. It consists of scenario-based multiple-choice questions focusing on Domain 1: Agentic Architecture, Domain 4: API & Orchestration, and Domain 5: Context Management. The exam prioritizes structural, deterministic solutions (like schema design and tool boundaries) over probabilistic approaches (like prompt instructions).

Scenarios Covered

This guide covers core architectural scenarios you are likely to encounter, including:

• Agentic Architectures: Subagent spawning, parallelism, and workflow decomposition.
• Context Management: Mitigating "lost in the middle" effects, context bloat, and preserving provenance through summarization.
• Tool & Schema Design: Enforcing business rules, standardizing outputs, and designing machine-readable identifiers for tool chaining.
• Batch Processing & State: Resuming crashed sessions, optimizing SLA buffers, and handling partial batch failures.

---

Questions & Answers

Q1: Handling Semantic Errors in Extraction Totals

Scenario: Schema Design & Self-Correction

Question:
An automated invoice extraction pipeline occasionally outputs structured JSON where the extracted line items do not add up to the total amount extracted from the invoice. What is the best architectural approach to handle this semantic error?

Options:

• A) Add a calculated_total field alongside the stated_total field, compare them, and flag mismatches for human review.
• B) Automatically adjust the line item values so they mathematically sum to the stated total.
• C) Introduce a secondary LLM step to reconcile the math errors.
• D) Add more few-shot examples of correct math to the prompt.

✅ Correct Answer: A — Extract calculated_total and flag discrepancies

Why this is correct:
JSON schemas prevent syntax errors but not semantic errors (like bad math). The most robust self-correction pattern is extracting both what the document explicitly states (stated_total) and what the model calculates from the line items (calculated_total). If they don't match, the record is flagged for human review. This improves reliability without fabricating data.

Why the others are weaker:

• B) Adjusting line items invents values not supported by the document, corrupting data integrity.
• C) Adds unnecessary architectural overhead when explicit deterministic validation is available.
• D) Few-shot examples cannot guarantee deterministic consistency for arithmetic.

💡 Exam Takeaway:
Design self-correction flows by extracting both a stated value and a calculated value, routing mismatches to human review rather than silently "fixing" source document errors.

---

Q2: Scaling Prompt Refinement vs. Batch Processing

Scenario: Batch Processing & Cost Optimization