9 The enterprise reference architecture · CCAR-P

Most CCAR-P scenarios fit one picture: requests pass through a gateway, reach Claude or an agent runtime, and touch enterprise data only through governed tools. Learn where each control lives and you can place almost any answer option.

Figure 7. The enterprise reference architecture: four layers and four cross-cutting controls

Read it top down. Channels never call Claude directly; the gateway enforces identity, guardrails, routing, and caching (Chapters 3 and 6). Claude runs on the platform and region the constraints require (Chapter 2). Tools reach data only through the MCP gateway and registry, under the user's own authorization (Chapter 4). Observability, evaluation, governance, and human review apply to every layer (Chapters 5 and 6).

Where each exam answer lands

If the item is about… Look at layer

Who the request acts as, PII screening, injection screening 2. Gateway

1. Channels

web, mobile, chat, email, internal apps; never call Claude directly

2. Gateway

identity and authorization, guardrails, routing, caching, prompt versions

3. Claude and agent runtime

model tiers on the required platform and region; loops, turn and spend limits, subagents

4. Integration

tools reach data only through the MCP gateway and registry, under the user's own authorization

Tool scope, token handling, retrieval permissions, freshness 4. Integration Drift, regressions, cost spikes Cross-cutting: observability and evaluation Approvals, audit, compliance Cross-cutting: governance and human review

The enterprise reference architecture