Monday, August 24, 2026

    Integration

    19% of the exam · 8 published objectives

    Domain 3 · Integration

    19%

    Weight as published in the exam guide. Your score report shows a percentage per domain and no domain has its own pass line — only the total scaled score decides the result.

    8 objectives, as published

    The guide lists these as bullets and assigns them no numbers. Nothing here numbers them either, and no score report will.

    • Evaluate tool/agent configuration for capability bloat
    • Analyze authentication and authorization requirements to identify security gaps
    • Evaluate accuracy-latency trade-offs and justify configuration decisions
    • Analyze observability challenges and select monitoring strategies at scale
    • Design a RAG pipeline with appropriate chunking and indexing strategies
    • Apply retrieval strategies matched to data shape and query pattern
    • Evaluate connection protocols and select the appropriate integration mechanism (MCP, API/CLI, agent-to-agent)
    • Evaluate progressive discovery vs. monolithic context strategy

    5 concepts — tap a card for the example, the right instinct and the trap

    Verified first-party sources for this domain

    18 pages, each fetched and observed to resolve on 2026-08-24.

    Objectives in this domain Anthropic does not document

    • RAG and retrieval architecture — no Anthropic guide exists
      How we know: Searched the whole platform.claude.com path manifest for /rag|retrieval/ on 2026-08-24: zero hits. The nearest page, Embeddings, is largely a third-party vendor table linking out to Voyage's own material.
      Read instead: The only first-party worked examples are the RAG recipes in the capabilities/ directory of the Claude Cookbooks repository. Citations and structured outputs cover the grounding half; chunking and indexing strategy is not documented by Anthropic at all.
      Objectives this leaves unsupported
      • Design a RAG pipeline with appropriate chunking and indexing strategies
      • Apply retrieval strategies matched to data shape and query pattern
    • Observability — one page, and it is on the Claude Code host
      How we know: Observability with OpenTelemetry, under the Agent SDK, is the only observability page in the corpus. There is no platform-level equivalent, and the exam asks about monitoring strategies at scale.
      Read instead: That page for the mechanism, plus the Usage & Cost and Analytics APIs for what is measurable about a deployment. Nothing first-party discusses observability design for a multi-agent system.
      Objectives this leaves unsupported
      • Analyze observability challenges and select monitoring strategies at scale
      • Monitor system performance using logging and observability tools

    Working the whole blueprint? The study guide carries the eligibility gate, the exam logistics and every concept card in one place.

    HomeNewsLearnIntelBuildAsk Koko