Home › Certifications › Azure AI Fundamentals AI-901 › Building Chat Clients and Agents
48 multiple-choice questions and 20 flashcards on Building Chat Clients and Agents, about 19% of the Azure AI Fundamentals AI-901 bank. Every one carries a written rationale.
Building Chat Clients and Agents is one of 6 chapters in CoStudy's Azure AI Fundamentals (AI-901) bank, and it holds 48 of the bank's 250 multiple-choice questions — roughly 19% of the total. That proportion is not arbitrary: chapters follow the certifying body's published exam outline, and the number of questions in each is set by that domain's published weight, so the share of your practice time this chapter takes matches the share of the real exam it accounts for.
Studying by chapter is worth doing once you have a diagnostic score. A single overall percentage tells you whether you are close; it does not tell you which domain is dragging. Working a weak chapter in isolation, and re-testing it in isolation, is the fastest way to move a score that has stalled — and it is why the mock exams in CoStudy report by domain rather than as one number.
3 questions drawn from this chapter, with the full rationale shown — the controlling principle behind the right answer, and why each wrong option tempts and fails.
Embeddings are:
Answer: B — Numeric vectors for text so similar meanings sit close
B) Right answer - an embedding maps text into a vector so that semantically similar passages land near each other, which is what makes vector search and grounding work. A) Image compression is unrelated to meaning. C) Backups are copies of stored data. D) Compiled code is an executable artifact, not a similarity space.
The PRIMARY problem that retrieval-augmented generation addresses is that a model:
Answer: B — Does not know private or recent data
B) Correct — the gap RAG closes is knowledge the model was never trained on: internal documents and information newer than training. A) Structured output is a prompting matter. C) Models do follow system prompts. D) Multiple examples are routine.
Using a managed identity rather than an embedded key for SDK calls is preferred because it:
Answer: B — Removes secrets from the application
B) Correct — the value is eliminating a long-lived secret that could leak, with credentials handled by the platform instead. A) Authentication method does not change generation speed. C) Context size is a model property. D) Filtering applies regardless of the credential type.
4 cards from the 20 in this chapter.
What does the Foundry SDK give you that calling a raw REST endpoint does not?
Typed clients for the project endpoint, integrated authentication, and a consistent surface across chat, agents, tools, evaluation and the Foundry Tools capabilities — so you switch models or add an agent without rewriting request plumbing. The REST API remains available underneath for anything the SDK does not wrap.
Why is a chat model described as stateless, and what does that mean for the developer?
The model retains nothing between requests; it sees only the messages in the current call. The developer — or a managed conversation feature — must resend the relevant history each turn, which is what makes the conversation feel continuous and what consumes context window.
Azure Search in Foundry Tools?
Search as a service that builds an index from your content, optionally enriching it with AI skills during ingestion. • Supports full-text, vector, hybrid and semantic queries, and is the usual retrieval layer for grounding a generative model.
What role does a search index play in a RAG solution?
It holds your content split into passages, usually with embeddings, so a question can be matched by meaning as well as keywords. Azure Search in Foundry Tools is the usual home for it, connected to the project so an agent can query it as a grounding tool.
These are a sample. The full Building Chat Clients and Agents chapter runs 68 items with per-chapter progress tracking, on the web and in the iOS app.
Open Azure AI Fundamentals AI-901 in CoStudy →