Multi-Agent Orchestration5% of the exam
When to use a multi-agent architecture
When one agent should become several and when it shouldn't: the reliability and control benefits of narrow specialist agents, the supervisor or orchestrator front door, Greeter, Operator and Orchestrator patterns, the four orchestration archetypes (SOMA, MOMA, Salesforce-led and MuleSoft-led multi-vendor), and what Agentforce Multi-Agent Orchestration supports today.
Given a scenario, determine whether a Multi Agent architecture is appropriate for scalability and control.
~7 min read · 8 practice questions ·
What the exam expects
- Decide whether a requirement needs one agent or several, using reliability, scale and control as the test.
- Cite the benefits Salesforce gives for multi-agent architecture, and the lighter-weight alternatives to consider first.
- Describe the supervisor (orchestrator) agent as a single front door, and tell the Greeter, Operator and Orchestrator patterns apart.
- Choose an orchestration archetype: Single Org, Multiple Agents (SOMA); Multi Org, Multiple Agents (MOMA); multi-vendor A2A led by Salesforce or by MuleSoft.
- Key terms: monolithic agent (one agent covering every domain); supervisor / orchestrator agent (the front door that routes or delegates to specialist agents); specialist agent (a narrowly scoped agent for one domain); connected subagent (a complete, separate agent that an orchestrator uses like a subagent, formerly topic); orchestration archetype (the system-level blueprint for how a fleet of agents collaborates).
Key facts
Default design
- Detail
- Start with a single agent for common use cases
Reliability principle
- Detail
- Limit any one agent's scope of concerns
Lighter alternatives
- Detail
- Ensemble of prompts; grounding through actions
Orchestrator pattern
- Detail
- Stays first point of contact; aggregates specialist responses
MOMA
- Detail
- Supervisor delegates to another org's agent via A2A
Handoff vs supervisor mode
- Detail
- Handoff (default): subagent answers directly; supervisor: orchestrator synthesizes
Feature scope today
- Detail
- One org; no cross-org or non-Agentforce agents; one delegation level
Timeouts
- Detail
- Orchestrator 120 seconds; connected subagent 30 seconds
- When should you start with a single agent?
- Why does splitting a large agent improve reliability?
- Which archetype fits when planning starts in a third-party application outside Salesforce?
- When is supervisor mode better than handoff mode?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Agentforce Specialist pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Agentforce Specialist guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams