The AgentForce Security and Deterministic Logic Guide specifies that sensitive actions must be gated through conditional filters linked to verification variables, not through natural language. It states: "For any process requiring secure, deterministic access, create a custom variable (e.g., IsCustomerVerified) that stores the verification status as a Boolean. Apply a filter expression to all protected actions (e.g., IsCustomerVerified
= true). This ensures the LLM cannot bypass or alter access logic."
This configuration ensures security and determinism because the execution of sensitive actions is programmatically enforced, not dependent on the LLM's understanding.
Option A is incorrect because natural language-based checks are non-deterministic.
Option B relies solely on topic instructions, which can be ignored or misinterpreted by the LLM.
Therefore, Option C is the only solution that provides deterministic, system-enforced access control.
References (AgentForce Documents / Study Guide):
AgentForce Security Configuration Guide: "Using Conditional Filters for Deterministic Access" AgentForce Implementation Handbook: "Verification Variables and Secure Action Flow" AgentForce Study Guide: "Protecting Sensitive Data in AI Workflows"