A 311 supervisor compares Copilot answers grounded only in city SharePoint knowledge-base articles with answers that also pull web data. What should the supervisor recognize?
Select an answer to reveal the explanation.
Short Explanation
City KB articles are the in-house playbook; the web is the wider world. Mixing those two context sources can change what Copilot says—so the 311 desk should know which well it's drawing from.
Full Explanation
Work files such as city SharePoint knowledge-base articles and web data are distinct Copilot context sources. A 311 supervisor should recognize that grounding only on approved municipal KB content can produce different answers than grounding that also pulls web information—because the underlying evidence set changed. That distinction matters for resident-facing accuracy: internal procedure wording may differ from generic web guidance.
Web data always overwriting and deleting SharePoint articles fails because using web grounding does not destroy the city's KB repository. Identical wording always fails because different sources can yield different phrasing, emphasis, or outdated external advice. Requiring the web to be fully disabled forever before SharePoint grounding works fails because organizational work-file grounding is not contingent on permanently turning off web context; the sources are separable concepts even when both are available in some experiences.
Exam caveat: Different sources change answers is not automatic endorsement of web grounding for 311. Many municipal desks prefer approved KB-only answers for consistency and liability. Know which mode policy allows.
Operational check: Document whether 311 Copilot responses must be KB-grounded only, compare sample answers with and without web context, and require staff to cite the SharePoint article ID or title when giving residents procedural guidance.