Testing, Deployment, and Maintenance10% of the exam
Deploying agents from sandbox to production
Moving a tested agent to production with a change set or with Salesforce CLI and source control: which metadata types carry the agent, why every dependency must travel with it, and the post-deployment steps (agent user, permissions, activation) on a go-live checklist.
Identify the considerations for deploying an agent from sandbox to production.
~8 min read · 6 practice questions ·
What the exam expects
- Choose between a change set and Salesforce CLI with source control for moving an agent.
- Name the metadata components that carry an agent and add every dependency (flows, Apex, objects, permission sets) to the deployment.
- Complete the move: inbound change set validation and deployment, or CLI retrieve and deploy.
- Plan post-deployment steps: agent user, permissions and activation.
- Build a go-live checklist that keeps testing in the sandbox.
- Key terms: change set (Setup tool that sends metadata from one connected org to another); Salesforce CLI (command-line tool that retrieves and deploys metadata between orgs and a local project); GenAiPlugin / GenAiFunction (metadata for an agent's subagents, formerly topics, and its actions); agent user (the user record a Service agent runs as); interdependent components (everything an action needs to run in the target org).
Key facts
Change set agent components
- Detail
- GenAI Function Definition, GenAI Plugin Definition, Bot
Dependencies
- Detail
- Add flows, Apex classes, custom objects and permission sets the actions use
Completing a change set
- Detail
- Open the inbound change set in the target, then validate and deploy
Committed agent metadata (v67 and earlier)
- Detail
- AiAuthoringBundle, Bot and BotVersion; not editable
v68 agent metadata
- Detail
- AiAgentDefinition and AiAgentDefinitionVersion; Bot only for Einstein Bots
CLI path
- Detail
- Retrieve from sandbox to a DX project, deploy to production
After CLI deploy
- Detail
- Assign the agent user; keep source and target agent versions matching
Activation
- Detail
- One active version per agent; needs Manage AI Agents plus agent-type permissions
Sources for this section (5)
- Agentforce Deployment with Change Sethelp.salesforce.com (opens in a new tab)
- Define Agent Metadata (v67 and Earlier)developer.salesforce.com (opens in a new tab)
- Agentforce Metadata Types (v68 and Later)developer.salesforce.com (opens in a new tab)
- Move an Agent to a New Orgdeveloper.salesforce.com (opens in a new tab)
- Activate or Deactivate Your Agenthelp.salesforce.com (opens in a new tab)
- Which three component types carry an agent in a change set?
- Why might an agent arrive in production with no subagents or actions?
- When should a team use Salesforce CLI instead of change sets?
- What must you do before a CLI-deployed agent can run in the target org?
- Why must testing stay in the sandbox on a go-live checklist?
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 (6 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams