A retail analytics group is setting up Azure AI Foundry so that three separate app teams (recommendations, chat support, and content moderation) can each deploy and manage their own models, while all three share the same virtual network, private endpoints, and Azure OpenAI connections that the central platform team already configured once. Which construct should the platform team create a single time, with each app team then attaching its own workspace to it?
Select an answer to reveal the explanation.
Short Explanation
Think of it like an office building versus individual offices. The building has the shared stuff nobody wants to set up three times: the network wiring, the security desk, the connections to outside services. Each team then gets its own office inside that building where they do their actual work, deploy their models, and keep their files separate from the other teams. Setting things up so each team gets its own separate building defeats the purpose of sharing anything, since now you are paying for three networks and three sets of connections instead of one. Cramming everyone into a single office also does not work, because then nobody has separation and one team's changes can bump into another team's work. The setup that actually matches what the platform team wants is a single shared foundation with individual team spaces built on top of it, so the expensive shared plumbing gets built once and each team still gets room to operate independently.
Full Explanation
The correct answer is B. A Foundry hub is the top-level container that holds shared infrastructure such as networking, private endpoints, and resource connections, while each app team's project sits underneath the hub as its own workspace for models, data, and deployments. This matches the scenario exactly: one shared setup, multiple isolated team workspaces. Option A is incorrect because a project is the team-level workspace itself, not a container designed to host multiple unrelated teams with separate governance needs; cramming three teams into one project removes the isolation they need. Option C is incorrect because abandoning Foundry for standalone resource groups throws away the central platform team's shared networking and connections, forcing each team to duplicate setup and increasing both cost and administrative overhead. Option D is incorrect because creating a separate hub per team recreates the shared network and connections three times over, which is precisely the duplicated effort the platform team was trying to avoid by configuring things once. The hub-and-project model is what lets centralized governance and per-team autonomy coexist.