Question 750
At Redfern Aviation, a supplier operations group is improving spare-part quotations during cross-channel acceptance testing (SF-A02-01). The administrator observes that an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. Any fix must ensure that supplier prices are never shown outside entitled teams. Which observable result would best demonstrate that the correction actually worked?
Explanation
Correct Answer
This is the direct acceptance signal for the reported failure: In a controlled Quote acceptance test, script validation and preview show predictable routing and available variables; the record is retained under Redfern Aviation's rollout (SF-A02-01). The chosen correction was to assign identity, variables, routing, and subagent instructions to their appropriate script blocks; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “A sample utterance enters the specified router and reaches the expected subagent; confirm this and retain a reproducible test record” would check a different original case: A new Agentforce agent has global instructions but no defined route for incoming requests. The correction must ensure that student records never cross program authorization boundaries. Its mechanism is: Agent Script expresses global configuration and runtime entry routing together. In the present case, an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that supplier prices are never shown outside entitled teams; the more direct acceptance evidence is “Script validation and preview show predictable routing and available variables; confirm this while testing the unauthorized case” because agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities.
The proposed observation “The first session turn correctly sees a false flag and later turns see the updated value; confirm this and confirm the resulting trace” would check a different original case: An agent checks whether a compensation was issued but its mutable flag has no reliable initial state. The correction must ensure that sensitive product claims must cite approved knowledge. Its mechanism is: Mutable Agent Script variables hold state that deterministic conditions can use. In the present case, an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that supplier prices are never shown outside entitled teams; the more direct acceptance evidence is “Script validation and preview show predictable routing and available variables; confirm this while testing the unauthorized case” because agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities.
The proposed observation “A test email follows the expected intake and response handling without a live-chat assumption; confirm this using a least-privilege test identity” would check a different original case: A team assumes an asynchronous support email flow has the same state and latency as an interactive web chat. The correction must ensure that billing adjustments require verified eligibility. Its mechanism is: Channel context changes how an agent receives messages and maintains interaction. In the present case, an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that supplier prices are never shown outside entitled teams; the more direct acceptance evidence is “Script validation and preview show predictable routing and available variables; confirm this while testing the unauthorized case” because agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities.