Coral Cloud Resorts (CCR) wants to configure its agent so that booking actions are only available when a customer's membership tier is "Premium" or "Elite". This business rule must be enforced…

Question

Options

• ASet up custom validation rules on the underlying booking objects to prevent non-eligible
• BConfigure topic instructions that clearly state booking actions should only be used for Premium or
• CCreate a context variable mapped to the customer's membership tier field, then add a conditional

• A
  17% (5)
• B
  10% (3)
• C
  73% (22)

Explanation

The requirement is that booking actions must be enforced 'deterministically' - meaning the rule must be guaranteed by system logic, not interpreted by the LLM. Using a context variable mapped to the customer's membership tier field provides a concrete, system-set value (e.g., 'Premium' or 'Elite'). A conditional action instruction or flow conditional then evaluates that variable and only exposes or executes the booking action when the tier matches. This is fully deterministic because it is enforced by code/configuration logic, not language model inference. Option A (validation rules on booking objects) fires after a booking action is attempted and submitted - it prevents saving but does not prevent the agent from attempting the action. It also does not proactively gate access. Option B (topic instructions) relies on the LLM to read and follow natural language rules, which is inherently probabilistic and can be inconsistently applied - explicitly ruled out by the 'deterministically' requirement.

No community discussion yet for this question.