Microsoft AI-103 Exam Dumps - Actual Questions Answers

The correct role is Cognitive Services OpenAl User . The application is using DefaultAzureCredential, so az login only proves the developer’s Microsoft Entra identity and enables token acquisition. It does not by itself grant authorization to the model deployment. Azure OpenAI and Microsoft Foundry separate authentication from authorization; Microsoft Entra ID provides token-based authentication, while Azure RBAC controls whether the signed-in principal can perform data-plane actions such as model inference. Microsoft’s Foundry guidance states that Microsoft Entra ID supports granular RBAC and that data-plane operations include runtime usage such as chat completions and embedding generation.

For Azure OpenAI resources, the Cognitive Services OpenAI User role specifically allows users to make inference API calls with Microsoft Entra ID against deployed models, while preventing higher-privilege actions such as creating deployments, copying keys, fine-tuning, or managing the resource.

The other roles are not least privilege. Contributor grants broad management-plane permissions. Cognitive Services User is broader and less specific than the Azure OpenAI inference role. Cognitive Services Data Reader is read-oriented and does not provide the required model inference data action. Reference topics: Microsoft Foundry authentication and authorization, Azure RBAC, Microsoft Entra ID keyless authentication, Azure OpenAI v1 API, and least-privilege model inference.

Access up-to-date information from public websites: Grounding with Bing Search

Perform calculations during conversations: Code interpreter

Retrieve information from documents uploaded directly to the agent: File search

The correct tool for public, current web information is Grounding with Bing Search . Microsoft Foundry Agent Service identifies Grounding with Bing Search as the built-in tool that enables an agent to access and return information from the internet, which fits the requirement for up-to-date public website data. ( learn.microsoft.com )

For calculations during conversations, use Code interpreter . Microsoft’s Foundry guidance states that Code Interpreter enables an agent to run Python code in a sandboxed execution environment and solve data analysis and math tasks iteratively. This is the correct fit for financial analysts who need calculations, analysis, and potentially chart generation during the conversation.

For documents uploaded directly to the agent, use File search . Microsoft describes File Search as the tool that enables Foundry agents to search through documents, retrieve relevant information, and augment model responses with knowledge from uploaded files such as PDFs, Word documents, and proprietary content.

Computer use is for interacting with graphical applications, not calculation or document retrieval. Microsoft Fabric is for enterprise data and analytics integration, not direct uploaded document retrieval. Reference topics: Foundry Agent Service tools, Code Interpreter, File Search, and Grounding with Bing Search.

The correct answer is D. Set the output_content_format=ContentFormat.MARKDOWN value . Azure Document Intelligence Layout API can return extracted document content in Markdown format, preserving semantic structure such as headings, paragraphs, sections, tables, and other layout elements. Microsoft’s Document Intelligence layout guidance shows the Python SDK pattern for analyzing a document with the prebuilt-layout model and setting output_content_format=ContentFormat.MARKDOWN in the begin_analyze_document call. The Markdown output is returned in the top-level content section of the analysis result.

This minimizes development effort because the service produces structure-preserving Markdown directly, rather than requiring custom post-processing to reconstruct sections and table formatting from raw OCR spans. Microsoft’s Markdown output documentation states that specifying Markdown output produces semantically structured content that maintains paragraphs, headings, tables, and other document elements in their proper hierarchy.

Option A only changes validation behavior and does not generate Markdown. Option B requests figures, not structured Markdown. Option C uses an incorrect parameter name; the documented SDK setting is output_content_format, not content. Reference topics: Azure Document Intelligence Layout API, Markdown output, PDF analysis, table extraction, and Foundry Tools document processing.