County IT must design Azure infrastructure for a Foundry project that hosts a permitting chatbot and shared models. What should that design emphasize?

County IT designing Azure infrastructure for a Foundry project that hosts a permitting chatbot and shared models should emphasize an Azure resource layout covering apps, shared model deployments, identity, and networking. Foundry projects sit in an Azure estate; municipal readiness means planning those boundaries, shared model consumption, authentication, and network controls—not planning dedicated model deployments, which don't address the chatbot app and shared model deployment layout.

An Azure resource layout for the Foundry project covering apps, dedicated model deployments, identity, and networking fails the requirement because it focuses on dedicated model capacity rather than the Foundry project’s app, shared model deployment, identity, and networking layout for a permitting chatbot. An Azure resource layout for the Foundry project covering apps, shared model evaluations, identity, and networking misses the mark because it addresses evaluating models rather than the full Foundry project layout for apps, shared model deployments, identity, and networking. An Azure resource layout for the Foundry project covering apps, shared model training, identity, and networking is only model training; it omits the shared model deployments needed to host the permitting chatbot.

Exam caveat: shared models still need access control so departments consume them appropriately without cross-contaminating secrets. Operational check: inventory Foundry project resources, confirm model deployments are reachable via intended identity and network paths, and document how the permitting app authenticates to those deployments.