Salesforce Decode
Salesforcedecode
Back to questions
AgentforceArchitect (Hardest)governancecenter-of-excellencemulti-bustandards

Govern agent sprawl across business units in a large enterprise

Real World Scenario

Six business units independently built 14 Agentforce agents with duplicate actions, inconsistent branding, and conflicting refund policies.

Expected Answer

• Establish an Agentforce CoE owning standards for topics, actions, prompts, and security baselines • Create a shared action library with certified invocable Flows and Apex services • Implement agent registry catalog documenting owner, scope, connected systems, and risk tier • Define review gates for new agents: security, legal, brand, and operational readiness • Consolidate duplicate agents where journeys overlap; differentiate by data scope not policy • Centralize analytics definitions so leadership sees enterprise-wide metrics • Fund platform team to maintain shared components—do not leave reuse as voluntary

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Establish an Agentforce CoE owning standards for topics, actions, prompts, and security baselines Also consider: Create a shared action library with certified invocable Flows and Apex services In practice: Implement agent registry catalog documenting owner, scope, connected systems, and risk tier Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Agent sprawl mirrors SaaS sprawl—cheap to start, expensive to unwind. A CoE is not bureaucracy; it is how you prevent 14 refund actions with different limits. Shared libraries with federated ownership scale better than mandates alone.