Question 700
At Quayside Commerce, an omnichannel retail help desk is improving return-policy queries before expanding the internal rollout (SF-M03-02). The administrator observes that a service agent delegates a case to a specialized billing agent without the required case identifier. Any fix must ensure that published policy must match the country of the customer. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that a service agent delegates a case to a specialized billing agent without the required case identifier. Define approved handoff inputs and evidence needed by the recipient agent for Quayside Commerce's return-policy queries workflow (SF-M03-02) while respecting that published policy must match the country of the customer. Its outcome is not established merely by changing instructions: In a controlled Case acceptance test, the receiving specialist obtains only the intended case context and returns a traceable outcome; the record is retained under Quayside Commerce's rollout (SF-M03-02). The underlying reason is that Multi-agent coordination depends on explicit context and controlled responsibility transfer. In this return-policy queries scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Use separate specialized agents with controlled task delegation when the isolation benefit justifies complexity; implement it with least-privilege execution” addresses a separate source case: A support and finance workflow has distinct permissions and responsibilities that one broad agent cannot govern safely. The correction must ensure that student records never cross program authorization boundaries. Its underlying reason is: Multi-agent design can separate responsibilities but increases orchestration complexity. This question instead describes a service agent delegates a case to a specialized billing agent without the required case identifier. The correction must ensure that published policy must match the country of the customer. The original answer “Define approved handoff inputs and evidence needed by the recipient agent; implement it with a controlled rollback path” targets that failure because multi-agent coordination depends on explicit context and controlled responsibility transfer.
The action “Keep a single appropriately scoped agent when multi-agent orchestration adds no control or scale benefit; implement it before the next environment promotion” addresses a separate source case: A basic FAQ workflow has one data source and no specialized actions yet architects propose six coordinating agents. The correction must ensure that supplier prices are never shown outside entitled teams. Its underlying reason is: Multiple agents should be chosen for a business or control need, not novelty. This question instead describes a service agent delegates a case to a specialized billing agent without the required case identifier. The correction must ensure that published policy must match the country of the customer. The original answer “Define approved handoff inputs and evidence needed by the recipient agent; implement it with a controlled rollback path” targets that failure because multi-agent coordination depends on explicit context and controlled responsibility transfer.
The action “Require authenticated agent identities and enforce recipient-side authorization for delegated tasks; implement it with a controlled rollback path” addresses a separate source case: A specialist agent trusts a delegated instruction to reveal private data outside its permitted audience. The correction must ensure that citizen information stays limited to the relevant case. Its underlying reason is: Cross-agent messages are requests, not blanket grants of authority. This question instead describes a service agent delegates a case to a specialized billing agent without the required case identifier. The correction must ensure that published policy must match the country of the customer. The original answer “Define approved handoff inputs and evidence needed by the recipient agent; implement it with a controlled rollback path” targets that failure because multi-agent coordination depends on explicit context and controlled responsibility transfer.