A hospital's Power Platform AI hub lists a clinical-note copilot that the privacy office has not approved, and makers can already see it. What is the design issue?
Select an answer to reveal the explanation.
Short Explanation
If the menu still offers a dish the kitchen was told not to serve, you change the menu. You govern what the AI hub exposes so makers are not offered a copilot the privacy office has not approved. Another agent does not take that listing down.
Full Explanation
The AI hub is a governance surface for which AI features people can see and use. A clinical-note copilot that the privacy office has not approved should not stay on offer, so the design issue is what the hub exposes, not a new build beside it. A second clinical-note agent outside the hub leaves the unapproved copilot in front of makers and adds another path onto the same notes. A longer instruction telling the copilot to be careful does not remove it from the hub, and a longer prompt is not a privacy approval. A training run on last year's discharge summaries uses the unapproved copilot as a model project and does nothing to stop makers from opening it today. Exam caveat: hiding a feature in the hub is not a substitute for deleting data it already processed, and the privacy office still has to decide whether a later, reviewed version may be turned on. Operational check: after the hub change, sign in as a maker and confirm the unapproved clinical-note copilot is no longer offered, while approved features remain visible. Ask the privacy office to confirm that same copilot stays off until they approve it. Naming note: the exam outline calls this the AI hub, while the Power Platform admin center currently labels the same admin controls the Copilot hub.