Question 980
At Alpine Hospitality, a concierge service organization is improving guest escalation during a controlled sandbox pilot (SF-A31-02). The administrator observes that an application uses a wide integration credential to call agents for multiple unrelated tenants. Any fix must ensure that escalations preserve only the needed guest context. 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 Case acceptance test, a client token cannot retrieve unrelated tenant context or perform forbidden actions; the record is retained under Alpine Hospitality's rollout (SF-A31-02). The chosen correction was to scope API access and underlying agent permissions to the intended application and tenant; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “A second turn refers to the prior conversation context and supported action outcome; confirm this and confirm the resulting trace” would check a different original case: An external partner requires conversational follow-ups but the design offers only a one-shot Flow endpoint. The correction must ensure that escalations preserve only the needed guest context. Its mechanism is: Agent API supports conversation patterns that differ from single transaction automation endpoints. In the present case, an application uses a wide integration credential to call agents for multiple unrelated tenants. The correction must ensure that escalations preserve only the needed guest context; the more direct acceptance evidence is “A client token cannot retrieve unrelated tenant context or perform forbidden actions; confirm this using a least-privilege test identity” because aPI connectivity does not override CRM or agent execution authorization.
The proposed observation “An authenticated application request receives a valid agent response and session mapping; confirm this and retain a reproducible test record” would check a different original case: A custom mobile application needs server-driven interaction with an already configured Agentforce agent. The correction must ensure that policy terms come from the current approved revision. Its mechanism is: Agent API enables programmatic agent interaction from external applications. In the present case, an application uses a wide integration credential to call agents for multiple unrelated tenants. The correction must ensure that escalations preserve only the needed guest context; the more direct acceptance evidence is “A client token cannot retrieve unrelated tenant context or perform forbidden actions; confirm this using a least-privilege test identity” because aPI connectivity does not override CRM or agent execution authorization.
The proposed observation “The helper is accessible only to authorized employees through approved internal channels; confirm this and confirm the resulting trace” would check a different original case: An internal procurement helper is configured as a public service agent with customer-facing entry points. The correction must ensure that citizen information stays limited to the relevant case. Its mechanism is: Agent type selection should follow user audience and operational purpose. In the present case, an application uses a wide integration credential to call agents for multiple unrelated tenants. The correction must ensure that escalations preserve only the needed guest context; the more direct acceptance evidence is “A client token cannot retrieve unrelated tenant context or perform forbidden actions; confirm this using a least-privilege test identity” because aPI connectivity does not override CRM or agent execution authorization.