Why is "Deploy flows, Apex, and all agent-related items using either change sets or the Salesforce CLI/Metadata API" the correct answer?
When deploying an Agentforce Agent with multiple topics and Agent Actions that use flows and Apex, a complete deployment solution is required. Change sets and the Salesforce CLI/Metadata API support the deployment of flows, Apex code, and agent-related metadata.
Key Considerations for Agentforce Deployments:
Supports Deployment of All Required Components
Agentforce Agents include flows, Apex classes, topics, and agent actions.
Change sets and Salesforce CLI/Metadata API allow deployment of all these components together, ensuring a smooth transition to production.
Agentforce Metadata Can Be Deployed Using Standard Tools
Change Sets: Allows admins to move configurations, custom objects, and metadata between Salesforce environments.
Salesforce CLI/Metadata API: Enables scripted deployments, automating the transfer of Agentforce configurations.
Ensures a Complete Migration Without Manual Configuration
Deploying all components together reduces the risk of misconfiguration.
Automating deployments using the Metadata API ensures consistency across environments.
Why Not the Other Options?
❌ A. Deploy the flows and Apex using normal deployment tools and manually create the agent-related items in production.
Incorrect because manually creating agent-related items in production introduces risk and inconsistency.
This approach is error-prone and time-consuming, especially for large Agentforce deployments.
❌ B. Use only change sets because the Salesforce CLI does not currently support the deployment of agent-related metadata.
Incorrect because Salesforce CLI and Metadata API fully support Agentforce deployments.
Change sets are useful but limited in large-scale, automated deployments.
Agentforce Specialist References
Salesforce AI Specialist Material confirms that Agentforce metadata (flows, actions, and topics) can be deployed using Change Sets or the Metadata API.
