Microsoft Microsoft Azure AI Fundamentals (Updated Version) AI-901 Exam Dumps: Updated Questions & Answers (September 2026)

In Microsoft Foundry Agent Service, tool_choice controls whether and how an agent uses tools during a run.

Statement 1: Yes

Setting tool_choice to auto lets the agent/model decide whether to call a tool. This statement is true.

Statement 2: No

Setting tool_choice to none does not mean the model decides whether to call a tool. It means the model will not call a tool. This statement is false.

Statement 3: Yes

Setting tool_choice to required means the agent must call one or more tools during the run. This statement is true.

Microsoft documentation describes the tool_choice values as follows: auto allows the model to decide whether to call tools, none prevents tool calls, and required forces one or more tool calls.

For vision-enabled Azure OpenAI / Microsoft Foundry model requests, image input can be provided by using an image URL or base64-encoded image data. Microsoft’s Azure OpenAI REST API reference states that the image content part URL field can contain either a URL of the image or the base64 encoded image data . It also states that the Responses API input_image.image_url value can be a fully qualified URL or a base64 encoded image in a data URL .

To ensure a vision-enabled model produces a relevant and useful response, the prompt should include a clear description of the task . For example, you should tell the model what to do with the image, such as describe it, identify objects, compare images, extract visible text, or answer a specific question about the visual content.

The other options are incorrect:

B. a dataset ID for the image is not needed in the prompt.

C. the version number of the model is deployment/configuration information, not prompt content.

D. the deployment name of the model is used in the API call to route the request, not inside the prompt.

The Model catalog is used for comparing and deploying a wide range of models for generative AI development in Microsoft Foundry.

Microsoft documentation states that the model catalog in Foundry portal is the hub for discovering and using a wide range of models to build generative AI applications . It also includes many models across providers such as Azure OpenAI, Mistral, Meta, Cohere, NVIDIA, and Hugging Face.

The Microsoft Learn module for Foundry models also states that the model catalog is used to explore and filter models , compare models using benchmark metrics , and deploy a model to an endpoint .

When calling a Foundry agent programmatically by using the Microsoft Foundry SDK, the application needs the agent’s configuration values, including the agent ID . The Foundry playground provides a Code view that shows sample application code and environment variables needed to call the agent.

The other options are incorrect:

A. copy the tool name used by the agent identifies a tool, not the agent.

B. copy the model family name identifies the model family, not the agent instance.

C. copy the project name identifies the project, not the specific agent ID.

Statement 1: Human-in-the-loop practices provide accountability for AI-generated decisions. = Yes

Microsoft responsible AI guidance recommends keeping a human in the loop, maintaining human oversight, and ensuring humans have a role in decisions based on model output.

Statement 2: Deploying an AI system to a production environment eliminates the need for ongoing monitoring. = No

Microsoft guidance states that after deployment, an AI-powered product or feature requires ongoing monitoring and improvement .

Statement 3: Disclosing the team that designed and deployed an AI system provides accountability for the system’s output. = Yes

Accountability in responsible AI means people and organizations remain responsible for AI systems and their effects. Identifying the people or team responsible for designing and deploying the system supports accountability and governance.

The Model catalog is used for comparing and deploying a wide range of models for generative AI development.

Microsoft states that the model catalog in Foundry portal is the hub for discovering and using a wide range of models to build generative AI applications. Microsoft training also states that the model catalog is used to compare models by benchmark metrics and deploy models to endpoints.

When using the OpenAI Responses API and a vision-enabled model, you can include an image in a request by providing the image as a base64-encoded image data .

Azure OpenAI / Microsoft Foundry vision requests support image input as an input_image item. The image can be provided by URL or as base64-encoded image data in the request. Microsoft documentation for Azure OpenAI batch examples also lists Base64 encoded image and Image URL as supported input patterns for Responses API requests.

The other options are incorrect:

a CSV file attachment is not an image input format for vision analysis.

an MP4 video stream is video content, not an image format.

a shared access signature (SAS) token is only an access token for a protected resource; it is not the image data itself.

The correct answer is API endpoint . After a generative AI model is deployed in Microsoft Foundry, the deployment exposes an inference endpoint through which external applications can submit requests and receive generated responses. Microsoft Foundry documentation describes deployed models as being accessible programmatically through an endpoint and associated credentials. Applications invoke the relevant REST API or SDK against this endpoint and specify the deployed model as required by the API.

An embedding vector is a numerical representation of semantic information used for similarity search, retrieval, and grounding; it is not the network interface through which a deployed model is invoked. A training dataset contains data used to train or fine-tune a model and is not called when performing inference. A URL parameter can be part of an API request, but it does not represent the deployed model ' s callable interface.

This directly aligns with the AI-901 objective to deploy a model and interact with it in the Foundry portal and to create lightweight applications that invoke deployed generative AI models through supported APIs and SDKs.