AI-103 Practice Question 41: Hub Based vs Foundry Project
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 5 · question 1 of 10
A consulting firm's platform team is standing up Foundry for several client-facing delivery teams. Every team already has Azure Machine Learning prompt-flow pipelines it must keep running, and the platform team wants all of the teams' projects to share the same data connections and sit under one centrally governed spend and security boundary, rather than each team wiring up its own connections independently.
What should the platform team create?
Show answer and explanation
Answer:
A hub exists precisely to serve multiple projects at once: "a hub allows you to share configurations like data connections with all projects, and to centrally manage security settings and spend." Hub-based projects are also the path Microsoft still documents for prompt flow, managed compute, and Azure Machine Learning compatibility, all three of which this firm's teams already depend on. One hub with a hub-based project per team gives every team its own workspace while inheriting the hub's shared connections and governance.
- A is wrong because giving each team its own standalone project with independently configured connections is exactly what the firm wants to avoid; there's no shared connection set and no single place to govern spend or security across teams. - C is wrong on two counts: a Foundry (project-only) resource doesn't carry prompt flow or Azure Machine Learning workspace compatibility, and Foundry Agent Consumer only grants access to call agent endpoints; it doesn't organize separate teams' work or connections. - D is wrong because it drops Foundry's project layer for day-to-day work and only reattaches it for agent hosting, which throws away the shared connections, governance, and agent tooling the platform team is trying to set up in the first place.
Reference: Create a hub project (classic)