Question 570
At Northpoint Hospitality, a guest services desk is improving reservation help during an agent routing evaluation (SF-T04-01). The administrator observes that Testing Center reports the correct response text but the wrong configured action executed. Any fix must ensure that guest profile fields are used only with permitted access. 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 Reservation__c acceptance test, the corrected test records expected action evaluation and response evaluation independently; the record is retained under Northpoint Hospitality's rollout (SF-T04-01). The chosen correction was to inspect expected versus actual action traces and investigate action selection; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “Escalation utterances route to the intended subagent in repeat tests; confirm this using a representative sandbox fixture” would check a different original case: The test suite passes replies but chooses the wrong subagent for escalation requests. The correction must ensure that escalations preserve only the needed guest context. Its mechanism is: Subagent evaluation measures routing independent of response wording. In the present case, testing Center reports the correct response text but the wrong configured action executed. The correction must ensure that guest profile fields are used only with permitted access; the more direct acceptance evidence is “The corrected test records expected action evaluation and response evaluation independently; confirm this with production-equivalent source conditions” because a passing final response does not prove the correct action path.
The proposed observation “An updated expectation reflects the approved action contract and test results become interpretable; confirm this and compare with approved baseline behavior” would check a different original case: A test fails because its expected action list references a removed legacy action. The correction must ensure that citizen information stays limited to the relevant case. Its mechanism is: Test results must be adjudicated when expected outcomes become obsolete. In the present case, testing Center reports the correct response text but the wrong configured action executed. The correction must ensure that guest profile fields are used only with permitted access; the more direct acceptance evidence is “The corrected test records expected action evaluation and response evaluation independently; confirm this with production-equivalent source conditions” because a passing final response does not prove the correct action path.
The proposed observation “The production prompt resolves all referenced automation resources successfully; confirm this and confirm the resulting trace” would check a different original case: A prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. Its mechanism is: Prompt templates can depend on metadata and automation beyond template text. In the present case, testing Center reports the correct response text but the wrong configured action executed. The correction must ensure that guest profile fields are used only with permitted access; the more direct acceptance evidence is “The corrected test records expected action evaluation and response evaluation independently; confirm this with production-equivalent source conditions” because a passing final response does not prove the correct action path.