A hospital wants a SharePoint agent that answers nursing policy questions. The draft connection lets the agent read every site in the tenant, including finance and executive sites the nurses do not use. What should the architect change?
Select an answer to reveal the explanation.
Short Explanation
The ward manual belongs on the ward shelf, not in every office in the building. You ground the nursing policy agent only on the approved nursing sites. A connection to every site in the tenant lets a policy question reach finance and executive files the nurses do not use.
Full Explanation
A SharePoint agent should be grounded on the sites that hold the content for its job, and no wider. Nursing policy lives on the approved nursing sites, so that is the grounding boundary, and finance and executive sites stay out of the agent's reach. Leaving the tenant-wide connection in place so a nurse can ask about finance files widens a clinical agent into records it was not built to answer. Copying policies onto a site anyone can open, and turning permissions off, trades a too-wide connection for an uncontrolled copy, and the agent no longer follows SharePoint access at all. Moving the agent to a public website and asking nurses to paste each policy leaves SharePoint, puts a second copy in the chat, and still does not establish the nursing sites as the source. Exam caveat: narrowing the sites is separate from whether a nurse's own account could open another library. The agent should not inherit the whole tenant just because one person can. Operational check: ask a nursing policy question and confirm the citation is from an approved nursing site, then confirm a finance file is not available to the agent.