Universal Containers (UC) is expanding its Agentforce for Service capabilities to include case management. For security purposes, UC wants the agent to verify a customer's identity before providing…

Question

Options

• AUse keywords such as "Always" and "Never" to write clear logic in Topic Instructions to verify user
• BCreate a variable to store the verification status, set it as output from a "Verify Identity" action,
• CStore the verification status in a custom variable and set a global instruction that the agent should

• A
  5% (3)
• B
  85% (50)
• C
  10% (6)

Explanation

For deterministic, gated behavior, the correct approach is to use a programmatic flow: a dedicated 'Verify Identity' action sets the result into a structured variable, and downstream actions check that variable's value before proceeding. This makes identity verification a hard conditional gate, not a soft instruction. Option A (keywords like 'Always'/'Never' in topic instructions) relies on the LLM following natural language guidance, which is probabilistic - not deterministic. Option C (a global instruction with a custom variable) is similarly LLM-interpreted and cannot guarantee the gate is enforced in all cases.

No community discussion yet for this question.