A Retrieval Augmented Generation evaluator is required because Agent1 will retrieve product-sheet content and use it as grounding context when generating answers. Foundry RAG evaluators assess both retrieval quality and the quality of the final grounded response. This directly supports Contoso's requirement that answers based on the product sheets be relevant, complete, and accurate.
The appropriate evaluation suite can include groundedness , which determines whether the answer is supported by the retrieved product information without fabrication; relevance , which evaluates whether the answer accurately and completely addresses the customer's question; and response completeness , which measures whether critical expected information is missing. Retrieval evaluators can additionally determine whether the indexing and search pipeline returned context chunks relevant to the query.
A coherence evaluator assesses readability and logical organization but does not establish that claims are supported by storage1. A custom guardrail controls or blocks behavior rather than measuring RAG quality.
Fine-tuning changes model behavior and does not evaluate whether retrieved documentation was selected and used correctly.
The AI-103 Study Guide includes evaluating models and applications for fabrications, relevance, quality, and safety , as well as monitoring grounding quality and retrieval relevance.

Explanation:

Call client.videos.create() to submit the prompt and start a video-generation job against the model deployment. Video generation is asynchronous: the initial response represents a job and contains properties such as its unique ID and current status rather than immediately returning the completed video. Microsoft's official Python example creates the job by using client.videos.create(model=..., prompt=...).
The application must then poll the job. After waiting between requests, client.videos.retrieve(video.id) obtains the latest state of that specific job. Polling continues until the status becomes completed, failed, or cancelled.
list would enumerate jobs rather than refresh the selected job, while download_content is used only after successful completion to retrieve the generated video file.
To comply with Contoso's prohibition on API keys, the client should use a Microsoft Entra bearer-token provider. The OpenAI Python client accepts this provider through its api_key constructor parameter even though no static API key is used.
Study Guide alignment: design and implement video-generation solutions and integrate generative workflows through Foundry SDKs.

The most appropriate type of deployment is a serverless API deployment (also referred to as a standard deployment or Models-as-a-Service / MaaS).
Key-Based Authentication: Serverless API deployments natively provision an endpoint URL alongside primary and secondary API keys to secure your client applications.
Real-Time REST API Access: When the model is successfully deployed, it exposes a scalable, real-time HTTP/REST endpoint matching the standardized Azure AI Model Inference API.
No Virtual Machine vCPU Quota Consumption: Unlike managed compute deployments-which provision dedicated virtual machines in your subscription and require VM vCPU quota- serverless API deployments are completely hosted and managed by Microsoft. They operate on a pay-as-you-go, token-based billing structure and do not consume any VM vCPU quota from your Azure subscription.
Reference:
https://learn.microsoft.com/en-us/azure/foundry/concepts/deployments-overview

Explanation:
" tool_choice " : " required "
The correct completion is " tool_choice " : " required " . In Microsoft Foundry Agent Service, tool_choice controls whether the model can answer directly or must invoke a tool during a run. The official Foundry tool guidance states that tool_choice provides deterministic control over tool calling: auto allows the model to decide whether to call tools, none prevents tool use, and required forces the model to call one or more tools.
This directly addresses the issue where the ticket-triage agent sometimes responds without invoking a required tool.
The completed payload should therefore add the tool_choice property beside assistant_id, with the value " required " . The value " auto " is incorrect because it preserves the current nondeterministic behavior. The values " tools " and " type " do not force execution-time tool invocation in this payload; they are used for tool definitions or typed objects in other contexts. response_format controls output formatting, not tool execution.
Reference topics: Microsoft Foundry Agent Service, tool calling reliability, run payload configuration, tool_choice, agent execution, and deterministic tool invocation.