Question 61
Choose 1
What should Universal Containers consider when deploying an Agentforce Service Agent with multiple topics and Agent Actions to production?
Correct answer:
B. Ensure all dependencies are included, Apex classes meet 75% test coverage, and configuration settings are aligned with production. Plan for version management and post-deployment activation.
Explanation
Deploying an Agentforce Service Agent into production—especially with multiple topics and custom Agent Actions—is a complex deployment. Here’s why Option B is correct:
✅ Key considerations when deploying Agentforce Service Agents:
Dependencies and References:
Agents, topics, and Agent Actions often reference:
. Flows
. Apex classes
. Prompt templates
. Search indexes
. Custom metadata
All referenced components must be deployed together or the agent will fail to execute in production.
Apex Test Coverage:
Salesforce requires a minimum of 75% test coverage for all Apex classes and triggers in production.
This is especially critical if your custom Agent Actions call Apex.
Environment Parity:
Ensure that settings and connected services (e.g. Data Cloud, Copilot indexes) in the sandbox/staging are mirrored in production.
Version Management:
You may need to manage different versions of:
. Prompt templates
. Agent configurations
. Flows
Deploying new versions without proper version management could break existing functionality.
Post-deployment Activation:
After deployment, Agentforce Agents are inactive by default in production.
You must manually activate the agent and test in production.
Hence, Option B is the correct and complete answer for real-world deployments.
Why the other options are incorrect:
Option A (Deploy without a test run in staging):
This is risky and not a best practice.
Testing in a sandbox or staging environment is critical to avoid production issues.
Option C (Deploy flows or Apex after agents):
That’s backwards.
Agent Actions depend on:
. Flows
. Apex classes
Those dependencies must be deployed first before the Agent can function.
Deploying agents before their supporting components would result in errors.
Therefore, Universal Containers should:
B. Ensure all dependencies are included, Apex classes meet 75% test coverage, and configuration settings are aligned with production. Plan for version management and post-deployment activation.
🔗 Reference
Salesforce Help — Deploy Copilot Components to Production
Salesforce Developer Docs — Agentforce Deployment Best Practices
Salesforce Blog — Avoid Deployment Pitfalls for Einstein Copilot
Deploying an Agentforce Service Agent into production—especially with multiple topics and custom Agent Actions—is a complex deployment. Here’s why Option B is correct:
✅ Key considerations when deploying Agentforce Service Agents:
Dependencies and References:
Agents, topics, and Agent Actions often reference:
. Flows
. Apex classes
. Prompt templates
. Search indexes
. Custom metadata
All referenced components must be deployed together or the agent will fail to execute in production.
Apex Test Coverage:
Salesforce requires a minimum of 75% test coverage for all Apex classes and triggers in production.
This is especially critical if your custom Agent Actions call Apex.
Environment Parity:
Ensure that settings and connected services (e.g. Data Cloud, Copilot indexes) in the sandbox/staging are mirrored in production.
Version Management:
You may need to manage different versions of:
. Prompt templates
. Agent configurations
. Flows
Deploying new versions without proper version management could break existing functionality.
Post-deployment Activation:
After deployment, Agentforce Agents are inactive by default in production.
You must manually activate the agent and test in production.
Hence, Option B is the correct and complete answer for real-world deployments.
Why the other options are incorrect:
Option A (Deploy without a test run in staging):
This is risky and not a best practice.
Testing in a sandbox or staging environment is critical to avoid production issues.
Option C (Deploy flows or Apex after agents):
That’s backwards.
Agent Actions depend on:
. Flows
. Apex classes
Those dependencies must be deployed first before the Agent can function.
Deploying agents before their supporting components would result in errors.
Therefore, Universal Containers should:
B. Ensure all dependencies are included, Apex classes meet 75% test coverage, and configuration settings are aligned with production. Plan for version management and post-deployment activation.
🔗 Reference
Salesforce Help — Deploy Copilot Components to Production
Salesforce Developer Docs — Agentforce Deployment Best Practices
Salesforce Blog — Avoid Deployment Pitfalls for Einstein Copilot
