Universal Containers has multiple Salesforce orgs, each with a unique customer service agent where a verification agent must pass customer identity data to downstream agents handling account modificat

Question

Options

• AImplement a custom object to temporarily store verification status and have each agent query it
• BStore customer identity information in conversation variables created by the first agent and have
• CUse the Agent API to start the downstream agent's session and pass the verified customer ID as

• A
  23% (6)
• B
  12% (3)
• C
  65% (17)

Explanation

The AgentForce Inter-Agent Communication and Security Configuration Guide specifies that when sensitive identity data (like a verified customer ID) must be shared between agents, the correct approach is to use the Agent API to initiate the downstream agent's session. The verified data should be passed as a read-only context variable, ensuring persistence across sessions while preventing modification by the large language model (LLM). This setup maintains data integrity and security compliance by isolating sensitive variables from the LLM's reasoning layer. Context variables passed via the Agent API are immutable during runtime, ensuring they cannot be altered or exposed in agent-generated responses.

No community discussion yet for this question.