A consultant is deploying Copilot's next-best-action recommendations for a sales team at a healthcare equipment distributor. Compliance requires that any recommendation a seller acts on be traceable to information already stored in the organization's Dataverse records, not to content Copilot may have retrieved from the public web. Which configuration should the consultant apply?
Select an answer to reveal the explanation.
Short Explanation
Picture Copilot as a research assistant who can either pull answers strictly from your own filing cabinet or also wander out and grab whatever it finds on the open internet. In a regulated setting, compliance needs every answer to point back to something already in that filing cabinet, so the fix is to tell the assistant to stop wandering outside and only use what is already on file. Turning on web search would send the assistant further from that requirement, not closer. Making sellers manually paste in outside research doesn't change what the assistant itself is grounded in, it just bolts extra effort onto an unsolved problem. And shutting the whole recommendation feature off throws away something useful to avoid a much smaller, fixable configuration issue. The real move is narrower than any of those: point the grounding at the organization's own data and leave the web out of it.
Full Explanation
The correct answer is C. The compliance requirement is that every recommendation must trace back to information the organization already holds in Dataverse, so grounding must be limited to first-party data sources and web content grounding must be turned off for this feature. That configuration satisfies the traceability requirement while preserving the value of AI-generated recommendations. Option A is incorrect because it does the opposite of what compliance requires, deliberately pulling in ungoverned web content that cannot be traced to internal records. Option B is incorrect because it adds a manual research step without actually restricting where Copilot's own grounding pulls from, so the underlying traceability gap is not closed and sellers gain extra work for no compliance benefit. Option D is incorrect because it eliminates a useful capability entirely when a narrower, supported configuration change achieves the same compliance outcome without losing the feature. The consultant's job is to match the tool's grounding settings to the regulatory constraint, not to add manual workarounds or remove the capability outright.