What should Universal Containers consider when deploying an Agentforce Service Agent with multiple topics and Agent Actions to production?

Question

Options

• ADeploy agent components without a test run in staging, relying on production data for reliable
• BEnsure all dependencies are included, Apex classes meet 75% test coverage, and configuration
• CDeploy flows or Apex after agents, topics, and Agent Actions to avoid deployment failures and

• A
  11% (5)
• B
  83% (39)
• C
  6% (3)

Explanation

When deploying Agentforce components to Salesforce production, proper deployment hygiene is critical. Option B is correct because Salesforce enforces that all dependent metadata components (flows, Apex classes, objects, permission sets, etc.) must be included in the deployment package - missing dependencies cause deployment failures. Additionally, Salesforce mandates a minimum of 75% code coverage for all Apex classes before any deployment to production can succeed. Option A is wrong because deploying without staging testing is a risky anti-pattern; issues should be caught in sandbox first. Option C is wrong because Apex classes and flows should be deployed BEFORE agents, topics, and Agent Actions, not after - the agent components depend on those underlying technical artifacts.

No community discussion yet for this question.