A developer has finished prototyping a chat experience in the Microsoft Foundry portal and now needs to embed the same deployed model inside a C# web service so that inference requests are issued programmatically at runtime. Which Foundry surface is designed for this?
- AThe Foundry SDK, which exposes client libraries so an application can authenticate to and call the deployed model from its own code. Correct
- BThe Foundry portal, which is a browser-based workspace for building and testing projects interactively rather than for embedding calls in application code.
- CAzure Content Understanding, which extracts fields from documents and media rather than providing programmatic access to a deployed chat model.
- DThe model catalogue, which lists available models to browse and deploy but does not itself issue runtime inference requests from application code.
Why A is correct: The Foundry SDK provides client libraries for languages such as C# and Python, letting application code authenticate and send inference requests to a deployed model at runtime, which is exactly what embedding the model in a web service requires.
Why B is wrong: The portal is tempting because that is where the prototyping happened, but it is an interactive browser workspace for building and testing, not a mechanism for issuing calls from within a compiled application.
Why C is wrong: Azure Content Understanding is an information-extraction capability for documents, images, audio, and video, so it does not give an application programmatic access to a deployed conversational model.
Why D is wrong: The model catalogue helps you find and deploy a model, but it is a discovery surface, not the runtime client an application uses to call the model once deployed.