Stormwater management needs a parks FAQ agent grounded only on approved SharePoint content. Which create-an-agent approach fits?

Stormwater management should create an agent grounded on the approved SharePoint FAQ content for the parks workload. Grounding on approved knowledge sources is the correct create-an-agent approach when answers must reflect vetted municipal FAQ material rather than using that FAQ content as an action, which runs tasks or calls data instead of grounding answers in vetted knowledge. SharePoint-approved content gives the parks FAQ agent a controlled corpus that communications and operations already own.

Creating an agent using the approved SharePoint FAQ content as an action for the parks workload fails because an action executes tasks or calls systems rather than grounding conversational answers in the vetted FAQ corpus. Creating an agent fine-tuned on the approved SharePoint FAQ content for the parks workload fails because fine-tuning customizes a model’s weights rather than grounding a created agent on a SharePoint knowledge source for vetted answers. Creating an agent triggered by the approved SharePoint FAQ updates to rewrite parks records fails because a record-rewriting automation is not a grounded FAQ answering agent and abandons the governed Microsoft 365 agent knowledge path.

Exam caveat: AB-900 Domain 3 covers creating agents and grounding them on knowledge sources such as approved SharePoint content. Grounding is not optional flavor—it is how agents stay tied to municipal truth. Do not confuse 'create an agent' with being triggered by approved SharePoint FAQ updates to rewrite parks records, which automates record writes rather than grounding FAQ answers in the vetted SharePoint corpus.

Operational check: Confirm the parks FAQ site or library is the approved source, create the agent with that SharePoint grounding, avoid a fine-tuning job on the FAQ content as fine-tuning customizes the model rather than grounding answers, test representative stormwater/parks questions against expected FAQ answers, and set an owner to update grounding when the FAQ pages change.