Question 490
At Keystone Telecom, a technical contact center is improving network fault support as a new data source is onboarded (SF-A24-02). The administrator observes that an agent would close a high-severity case directly without the required human approval. Any fix must ensure that production changes remain gated by approval. 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 Incident__c acceptance test, a high-severity case remains open until required approval is recorded; the record is retained under Keystone Telecom's rollout (SF-A24-02). The chosen correction was to require an approved authorization and confirmation step before the privileged action; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “A user without field access cannot obtain the protected value through the agent; confirm this using a least-privilege test identity” would check a different original case: A template returns a confidential account field in a customer-facing response. The correction must ensure that policy terms come from the current approved revision. Its mechanism is: Field-level security still governs agent grounding and action results. In the present case, an agent would close a high-severity case directly without the required human approval. The correction must ensure that production changes remain gated by approval; the more direct acceptance evidence is “A high-severity case remains open until required approval is recorded; confirm this and retain a reproducible test record” because sensitive agent operations need deterministic approval gates beyond conversational requests.
The proposed observation “A cross-account record access test fails under the agent's runtime security context; confirm this using a representative sandbox fixture” would check a different original case: A service agent action runs with a privileged user context that grants excessive record visibility. The correction must ensure that plant access boundaries are not weakened by chatbot replies. Its mechanism is: The user identity executing an action determines which permissions can apply. In the present case, an agent would close a high-severity case directly without the required human approval. The correction must ensure that production changes remain gated by approval; the more direct acceptance evidence is “A high-severity case remains open until required approval is recorded; confirm this and retain a reproducible test record” because sensitive agent operations need deterministic approval gates beyond conversational requests.
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 agent would close a high-severity case directly without the required human approval. The correction must ensure that production changes remain gated by approval; the more direct acceptance evidence is “A high-severity case remains open until required approval is recorded; confirm this and retain a reproducible test record” because sensitive agent operations need deterministic approval gates beyond conversational requests.