A retailer's makers are ready to build a product-description copilot because they cannot tell which AI features are already turned on in the tenant. Where should the architect send them before that build starts?
Select an answer to reveal the explanation.
Short Explanation
Picture a stockroom clerk who orders another case without checking the shelf. You can send the makers to the Power Platform AI hub to see which AI features are already on in the tenant. Checking first helps you avoid funding a fresh build for a feature that may already be available.
Full Explanation
The Power Platform AI hub is where you can discover and review the AI features already turned on in the tenant, giving the makers the inventory they currently lack. Sending them there before a product-description build helps you reuse or govern an existing feature rather than duplicate it. A new Copilot Studio agent that rebuilds product descriptions starts a duplicate build without showing what the tenant already enabled. A custom model project trained on last season’s copy is a training effort, but it leaves the team just as unaware of features already turned on. One maker’s private prompt file is inaccessible to the rest of the team and is not a catalog of tenant AI features. Exam caveat: a feature listed in the hub still has to meet the retailer’s own policy before anyone relies on it; visibility is not approval. Practical check: have the makers open the hub, record the product-description features already on, and compare that list with the proposed build before creating an agent. If a matching feature is already on, the work becomes configuring that feature rather than creating a second copilot. 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.