A junior developer wants to quickly try out how a candidate model responds to different system messages and sample questions before writing any application code or committing to a deployment configuration. What Foundry capability lets them do this interactively, without building a custom application first?
Select an answer to reveal the explanation.
Short Explanation
You just want to poke at the model and see what it does, and the Foundry portal's chat playground is built for that. It lets you type system messages and sample questions directly in the browser without writing application code. Logs, automated evaluation, and fine-tuning are heavier or after-the-fact tools, not quick prompt testing.
Full Explanation
The correct answer is using the Foundry portal's chat playground to interactively test prompts. It is built exactly for this kind of quick, interactive exploration, letting a developer type system messages and sample questions directly in the browser and immediately see how a candidate model responds, with no application code required. Reviewing Azure Monitor logs for the deployment is incorrect because Azure Monitor logs report on the behavior and performance of a deployment that is already running in production; they are an after-the-fact observability tool, not a way to interactively test prompt ideas beforehand. Running the automated evaluation SDK against a labeled test set is incorrect because the evaluation SDK is designed to run automated, repeatable scoring across a labeled test set at scale, which is a heavier, more formal process than casually trying out a few prompts. Submitting a fine-tuning job with sample conversations is incorrect because fine-tuning retrains the model's weights on example conversations, a significant undertaking meant to change model behavior long-term, not a lightweight way to preview how an existing model already responds.