Home / Claude Certified Architect – Foundations / Objective 1.5

Domain 1: Agentic Architecture & Orchestration · 27% of the exam · Full exam outline

1.5 Apply Agent SDK hooks for tool call interception and data normalization

What this objective covers

Hook patterns (e.g., PostToolUse) that intercept tool results for transformation before the model processes them. Hook patterns that intercept outgoing tool calls to enforce compliance rules (e.g., blocking refunds above a threshold). The distinction between using hooks for deterministic guarantees versus relying on prompt instructions for probabilistic compliance. Implementing PostToolUse hooks to normalize heterogeneous data formats (Unix timestamps, ISO 8601, numeric status codes) from different MCP tools before the agent processes them. Implementing tool call interception hooks that block policy-violating actions (e.g., refunds exceeding $500) and redirect to alternative workflows (e.g., human escalation). Choosing hooks over prompt-based enforcement when business rules require guaranteed compliance.

Practice questions

Question 1easy

To cut latency, a developer changes a PreToolUse policy hook so it returns {"async": true} and finishes its check in the background. What does this do to the policy?

Included in Master: master every domain.See plans
Question 2easy

A stage-lighting assistant issues a tool call with these hook input fields:

{
  "tool_name": "mcp__stage__dim",
  "tool_input": {"zone": "balcony", "level": 35},
  "session_id": "lighting-72"
}

For a PreToolUse hook, which value does the SDK test against the registered matcher?

Included in Master: master every domain.See plans