Question 400
At Keystone Telecom, a technical contact center is improving network fault support after a customer-reported regression (SF-A29-03). The administrator observes that a custom mobile application needs server-driven interaction with an already configured Agentforce agent. 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, an authenticated application request receives a valid agent response and session mapping; the record is retained under Keystone Telecom's rollout (SF-A29-03). The chosen correction was to use the supported Agent API integration rather than screen-scraping an agent UI; 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, a custom mobile application needs server-driven interaction with an already configured Agentforce agent. The correction must ensure that production changes remain gated by approval; the more direct acceptance evidence is “An authenticated application request receives a valid agent response and session mapping; confirm this using a least-privilege test identity” because agent API enables programmatic agent interaction from external applications.
The proposed observation “A client token cannot retrieve unrelated tenant context or perform forbidden actions; confirm this using a representative sandbox fixture” would check a different original case: An application uses a wide integration credential to call agents for multiple unrelated tenants. The correction must ensure that production changes remain gated by approval. Its mechanism is: API connectivity does not override CRM or agent execution authorization. In the present case, a custom mobile application needs server-driven interaction with an already configured Agentforce agent. The correction must ensure that production changes remain gated by approval; the more direct acceptance evidence is “An authenticated application request receives a valid agent response and session mapping; confirm this using a least-privilege test identity” because agent API enables programmatic agent interaction from external applications.
The proposed observation “An end user opens the authorized support entry point and sees the intended agent behavior; confirm this and confirm the resulting trace” would check a different original case: A service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that financial identifiers are masked outside authorized roles. Its mechanism is: An agent definition does not automatically establish its channel delivery. In the present case, a custom mobile application needs server-driven interaction with an already configured Agentforce agent. The correction must ensure that production changes remain gated by approval; the more direct acceptance evidence is “An authenticated application request receives a valid agent response and session mapping; confirm this using a least-privilege test identity” because agent API enables programmatic agent interaction from external applications.