Home / AI-901 / Objective 2.1

Domain 2: Implement AI solutions by using Microsoft Foundry · 57% of the exam · Full exam outline

2.1 Implement generative AI apps and agents by using Foundry

What this objective covers · 19% of the exam

Create effective system and user prompts for generative AI models; Deploy a model and interact with it in the Foundry portal; Create a lightweight chat client application by using the Foundry SDK; Create and test a single-agent solution in the Foundry portal; Create a lightweight client application for an agent

Practice questions

Question 1easy

A clinic puts a deployed chat model behind its booking website. Whatever a patient types, every reply must stay friendly and must decline to give medical advice. Where should the developers place these rules?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Standing rules for tone and limits belong in the system prompt: the model answers every user prompt while obeying that guidance, so the rules hold whatever patients type.

TPM governs throughput on the deployment; it cannot express rules about tone or forbidden topics.

Tempting because history is resent with each prompt, but its job is to keep earlier questions and answers in context; it records what was said rather than defining how the model must behave.

Temperature trades predictability for creativity; raising it makes replies less controlled, not rule-bound.

Question 2easy

A compliance reviewer asks which setting on a Foundry model deployment decides where and how its inference requests are processed. Which deployment parameter should the team point to?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Temperature is a runtime generation parameter for creativity; it says nothing about processing location.

TPM is also a deployment parameter, which is why it tempts, but it sets how much token traffic the deployment can handle, not where processing happens.

Deployment types such as standard, global batch or regional provisioned throughput determine where and how inference runs, tied to throughput and data-processing needs.

System instructions shape the model's behavior and role; they do not configure the deployment's infrastructure.