AI-201 · Question #220
Universal Containers needs to restrict access to refund processing actions so only customers with Active account status can initiate refunds. How should an Agentforce Specialist apply the restriction
The correct answer is B. Create a context variable for the account status field and apply a conditional filter AccountStatus. The word 'deterministically' is the key signal here - it means the restriction must be enforced by logic, not by LLM interpretation. Context variables with conditional filters are evaluated programmatically: if AccountStatus ≠ Active, the action is simply not available to the age
Question
Universal Containers needs to restrict access to refund processing actions so only customers with Active account status can initiate refunds. How should an Agentforce Specialist apply the restriction deterministically?
Options
- ACreate a Flex Prompt Template that has instructions to check for account status.
- BCreate a context variable for the account status field and apply a conditional filter AccountStatus
- CInclude step-by-step instructions at the topic level and action level explaining the rules and
How the community answered
(34 responses)- A9% (3)
- B71% (24)
- C21% (7)
Explanation
The word 'deterministically' is the key signal here - it means the restriction must be enforced by logic, not by LLM interpretation. Context variables with conditional filters are evaluated programmatically: if AccountStatus ≠ Active, the action is simply not available to the agent. This is a hard, rule-based gate. Using a Flex Prompt Template with instructions (A) or adding step-by-step instructions at the topic/action level (C) both rely on the LLM to interpret and follow the rule - which is non-deterministic and can be bypassed or misread. For security-critical business rules like refund eligibility, always use conditional logic, not prompt instructions.
Topics
Community Discussion
No community discussion yet for this question.