AI-900 Practice Question: Describe features of generative AI workloads on Azure
What is 'Azure OpenAI's Assistants API' and what capabilities does it add?
⚠ Common exam trap
Test-takers frequently confuse the Assistants API with a simple completion API (Option D) or assume it requires human oversight (Option A), missing the key differentiator of statefulness and tool integration.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A stateful API enabling AI assistants with persistent threads, tool use, and file handling
The Assistants API is a stateful API that manages persistent threads, supports tool use (e.g., code interpreter, file search), and handles file attachments, enabling multi-turn, context-aware AI assistants. This goes beyond simple completions by maintaining conversation state and integrating external tools, which is a core generative AI workload capability on Azure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
An API for hiring human assistants to review and approve AI model outputs
Why it's wrong here
This option confuses human-in-the-loop workflows with an API that automates AI agent behavior. The Assistants API does not hire, schedule, or involve human reviewers to approve model outputs; it uses language models and tools to act autonomously on behalf of the user. Human review and approval workflows are typically implemented as separate governance processes, for example using Azure AI Content Safety or custom review systems built around model outputs. Therefore, this description incorrectly frames the Assistants API as a workforce-management service rather than as a stateful AI orchestration API.
- ✓
A stateful API enabling AI assistants with persistent threads, tool use, and file handling
Why this is correct
The Assistants API is a stateful application programming interface specifically designed to enable AI assistants that maintain persistent conversation state. It provides persistent thread objects that store the full message history across turns, built-in tool use such as the Code Interpreter and File Search, and the ability to attach and reference files during a conversation. This design allows developers to craft sophisticated multi-turn agents that can perform complex tasks—like retrieving relevant documents, executing code, and calling custom functions—without requiring the client to resend all prior context. This option accurately captures the fundamentally stateful, tool-enabled nature of the service.
- ✗
An API for building traditional rule-based chatbots without language model capabilities
Why it's wrong here
Traditional rule-based chatbots rely on hard-coded decision trees, keyword matching, and pattern-matching rules, with no language model generating responses; they cannot handle unanticipated phrasing or complex reasoning. The Assistants API is fundamentally different: it is powered by large language models that understand natural language and generate contextual, generative replies. Moreover, the Assistants API adds stateful threads, tool invocation, and file handling capabilities that a purely rule-based system completely lacks, so this option describes a legacy technique rather than the API in question.
- ✗
A simplified interface for generating single-turn completions without conversation history
Why it's wrong here
The base Chat Completions API (or legacy Completions API) is a stateless endpoint that takes a list of messages and returns a single model response, with no built-in mechanism for maintaining conversation history or state across turns. The Assistants API, by contrast, is purpose-built for multi-turn agents: it introduces persistent threads that automatically store and manage message history, and it orchestrated tool calls and file access as part of the run loop. Thus describing it as 'a simplified interface for single-turn completions' directly mischaracterizes its architecture and intended use.
Go deeper
Related to this question
Learn chapter
Machine Learning Core Concepts
Key term
Generative AI
Generative AI is a type of artificial intelligence that creates new content—like text, images, or code—by learning patterns from existing data.
Key term
Azure OpenAI Service
Azure OpenAI Service is a cloud platform from Microsoft that lets developers use powerful artificial intelligence models, like GPT-4, to build applications that can understand and generate human-like text, code, images, and more.
About these practice questions
Courseiva writes every AI-900 question from scratch — 985 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AI-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI-900 exam.