A developer needs a small app that chats with a deployed model. What do they use?
Why B is the answer
The Foundry SDK
The Foundry SDK lets a developer build a lightweight chat client that calls a deployed model.
In detail
- The Foundry SDK lets code call a deployed model.
- Use a managed identity in Azure rather than a stored key where you can.
Use case
An illustrative scenario, not a real incident.
A developer builds a small chat app with the Foundry SDK, which calls the deployed model from code.
See it in different ways
flowchart LR A["Deploy a model in Foundry"] --> B["Get the endpoint"] B --> C["Your app calls it with the SDK"] C --> D["Show the response"]
sequenceDiagram participant D as Developer participant F as Foundry participant A as App D->>F: Choose a model in the catalog D->>F: Deploy it D->>F: Test it in the playground A->>F: Call the endpoint
sequenceDiagram participant P0 as App participant P1 as Foundry SDK participant P2 as Deployed model P0->>P1: Send the prompt P1->>P2: Call the endpoint P2-->>P0: Reply
Key point: Apps call deployed models through the SDK.
Why the other options are wrong
- A. The model catalog page in the portal
- A catalog page cannot be called from an app.
- C. An Azure Policy definition
- A policy governs resources, and does not call a model.
- D. The Azure pricing calculator
- A calculator estimates cost.