Pass the Microsoft Microsoft Certified: Azure AI Fundamentals AI-901 Questions and answers with CertsForce

Tokens per minute, or TPM , is a throughput allocation for a model deployment. Assigning a higher TPM allocation increases the amount of token processing capacity available to the deployment, which affects the speed and scale at which the deployment can process requests.

It does not directly make responses longer, change region availability, or automatically add citations.

The completed code is:

poller = client.begin_analyze(

analyzer_id= " invoice " ,

input_url=url

)

result = poller.result()

Azure Content Understanding analysis uses a long-running operation pattern. The Python SDK returns a poller from begin_analyze(), and Microsoft documentation states that the SDK poller handles polling automatically when you call .result() .

Therefore, to retrieve the analysis results after processing completes, the correct option is:

result

The other options are incorrect because status checks operation state, wait waits without returning the final analysis object, and get_results is not the method shown for retrieving the begin_analyze() result in this code pattern.

The correct answer is endpoint of the model . After a vision-enabled GPT model is deployed in Microsoft Foundry, the deployment exposes an inference endpoint that applications can call programmatically. The application sends requests containing text and, when required, image content to the deployed model through the appropriate chat-completions API endpoint. Microsoft’s documentation explicitly states that to use vision-enabled models, you call the Chat Completion API against a supported model that has been deployed.

The Foundry playground is primarily an interactive environment for testing prompts, model behavior, and multimodal inputs during development. It is not the production interface that an external application uses to submit inference requests. An evaluation pipeline is used to assess model or application quality against defined metrics and datasets, while a training dataset is associated with model training or fine-tuning rather than serving inference traffic.

Microsoft Foundry provides the endpoint and required authentication information after deployment. Applications then invoke that endpoint using an SDK or REST API, passing text and image inputs as part of the request payload.

Statement 1: Evaluators in Microsoft Foundry replace the need for configuring token limits. = No

Evaluators are used to assess model or agent output quality, safety, and reliability. They do not replace model configuration settings such as token limits. Microsoft describes evaluators as tools that measure the quality, safety, and reliability of AI responses.

Statement 2: Evaluators in Microsoft Foundry can assess the quality and safety of responses generated by a generative AI model. = Yes

This is correct. Microsoft Foundry includes built-in evaluators for general quality metrics such as coherence and fluency, safety/security metrics, RAG metrics, and agent-specific metrics.

Statement 3: Evaluators in Microsoft Foundry can retrain a deployed generative AI model automatically when quality issues are detected. = No

Evaluators measure and report quality, safety, and reliability issues. They do not automatically retrain deployed generative AI models. Microsoft describes evaluation as measuring model or agent performance against test data, while monitoring can alert when outputs fail quality thresholds.

Statement 1: The Temperature parameter can be set before deploying a model. = No

temperature is an inference/request parameter used when calling or testing a deployed model. It controls randomness in generated responses. It is not a required setting for deploying the model itself.

Statement 2: During inference, the model name is used to route requests to a specific deployment. = No

In Azure OpenAI / Microsoft Foundry deployments, application requests are routed to a specific deployment name , even when the SDK parameter is called model. The underlying model name, such as gpt-4.1-mini, is not what routes the request to the deployment.

Statement 3: After a model is deployed, both code and testing tools can be used to interact with the model. = Yes

After deployment, you can test the model in Foundry playground/testing tools or call the deployment from application code by using the endpoint, deployment name, and authentication credentials.

Statement 1: Voice Live returns only transcribed text. = No

Voice Live is not limited to returning transcribed text. It is designed for real-time spoken conversational experiences and can include speech input, model reasoning, and spoken output.

Statement 2: Voice Live requires you to separately implement speech to text and text to speech services. = No

Voice Live combines the conversational voice pipeline, so you do not need to separately build independent speech-to-text and text-to-speech services for the same real-time voice experience.

Statement 3: Voice Live combines speech to text, reasoning, and text to speech into a single conversational experience. = Yes

This statement is correct. Voice Live is used for real-time conversational AI experiences where spoken input is processed, the model reasons over the request, and spoken output can be returned.

GPT and DALL-E are examples of generative AI model types/families.

GPT models generate natural language text, such as answers, summaries, emails, and conversations.

DALL-E models generate images from text descriptions.

Why the other options are incorrect:

A. transformer is a model architecture, not the best answer here as a generative model type/family.

B. computer vision is an AI workload area.

E. natural language processing is an AI workload area, not a specific generative AI model type.