Free Practice Questions for Microsoft AI-103 Exam

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

Yes. Moderate text content is exactly the Content Safety testing workflow Microsoft documents for analyzing sample text and tuning harmful-content filtering.

Microsoft ' s current quickstart instructs users to open the Moderate text content panel, provide sample text, and select Run test . The service returns detected harm categories together with severity levels. The user can then open Configure filters , adjust which severity levels are allowed or prohibited for each category, and run the text again to verify the behavior. Microsoft Learn

That directly satisfies the requirement to optimize the content-filter configuration by testing sample questions.

The Safety metaprompt capability influences generative model behavior but does not provide the same moderation-threshold testing. Protected material detection evaluates a separate protected-content concern and likewise is not the harmful-content filter test surface.

Therefore, the answer printed in the supplied document ( B, No ) conflicts with current Microsoft Learn documentation. The verified answer is A, Yes .

Study Guide alignment: configure safety filters, guardrails, risk detection, content moderation, and safety evaluations for generative AI and agentic systems . Microsoft Learn

====================

Create an AnalyzeTextOptions instance and set its required text property to the string stored in comment. Microsoft ' s Python SDK reference defines text as a required string containing the text to analyze. Microsoft Learn

Then submit the request through:

client.analyze_text(request)

The resulting AnalyzeTextResult exposes categories_analysis. The code can iterate through those results, locate the item whose category is TextCategory.SELF_HARM, and return its severity.

Azure AI Content Safety currently analyzes the primary categories Hate, SelfHarm, Sexual, and Violence and returns severity information that can be used by the application to enforce publishing policy. Microsoft Learn

analyze_image is inappropriate because the input is textual. A nonstandard client_moderate_text method is not the current SDK operation. The request ' s categories field, when used, expects a list of category identifiers and not the comment itself.

The technically correct current Python pattern is therefore AnalyzeTextOptions(text=comment) followed by client.analyze_text(request).

Study Guide alignment: configure detection of safety issues and sensitive content in text-analysis solutions . Microsoft Learn

====================

Endpoint selection: assistants

Function declaration property: tools=[

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

The command is creating/configuring an assistant that has access to a custom function named get_current_time, so the REST resource shown in the exhibit is assistants .

For the function definition, current Azure OpenAI/Foundry function-calling syntax uses the tools collection. A function tool is represented by an item with " type " : " function " and a nested " function " object containing its name, description, JSON parameter schema, and required arguments.

Microsoft explicitly documents that the older functions and function_call parameters have been deprecated and that tools and tool_choice should be used instead. Microsoft Learn

Therefore, although the embedded exhibit ' s answer image shows functions=[, the currently verified Microsoft syntax is tools=[ .

content represents message content rather than an agent tool definition. tool_resources is used for resources required by certain hosted tools and is not where a custom function schema is declared.

The AI-103 Study Guide requires candidates to define tool schemas and integrate agent tools, including APIs and custom functions . Microsoft Learn

====================

The correct intervention point is tool call because the prohibited content must be inspected before Agent1 transmits the MCP request to the external server. Microsoft Foundry defines a tool call as “the action and data the agent proposes to send to a tool.” This includes the selected MCP operation and its arguments or payload. A guardrail configured at this stage evaluates the outbound content immediately before execution. When the Violence risk is detected and the response action is configured as Annotate and block , the tool invocation is not executed, preventing the restricted data from leaving the agent boundary.

The other intervention points operate at different stages. User input scans the original user prompt, but harmful content could subsequently be generated within the tool arguments. Tool response scans information returned by the MCP server, which occurs after the outbound content has already been transmitted. Output scans the final answer delivered to the user and therefore does not control agent-to-tool communication.

This aligns with the AI-103 Study Guide topics Configure safety filters, guardrails, risk detection, and content moderation and Govern agent behavior with oversight modes, constraints, and tool-access controls under responsible AI and agentic systems.

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

Few-shot learning , more precisely few-shot prompting, supplies a small number of representative input/output examples as part of the prompt. Those examples demonstrate the intended classification behavior before the model receives the new support ticket.

For example, the prompt might show one ticket classified as Billing, one as AccountAccess, and one as TechnicalIssue. The model can infer the expected labels, style, and output structure from the demonstrations and then apply the pattern to the incoming ticket.

The model ' s weights are not updated. The examples exist only in the prompt context for that invocation or conversation, so the approach satisfies both requirements: no retraining and no permanent knowledge storage.

Zero-shot prompting would supply only task instructions and no demonstrations. RAG retrieves external source information to ground model responses; it is not primarily a mechanism for showing examples of desired classification outputs. Chain-of-thought relates to reasoning behavior rather than labeled demonstration examples.

Few-shot prompting is therefore the direct method for increasing task accuracy by showing the model what correct results look like.

Study Guide alignment: Optimize generative AI systems through prompt engineering and adjust model behavior without retraining . Microsoft Learn

====================

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

The Safety metaprompt is not the Content Safety feature intended to measure harm-category severity and tune moderation thresholds against representative sample text.

A safety metaprompt provides additional behavioral instructions intended to guide a generative model toward safer responses. It can complement other safety controls, but it does not perform the specific text moderation test required to determine whether configured severity thresholds accept or reject sample prompts.

For threshold testing, Microsoft provides the Moderate text content experience. The user supplies sample text, selects Run test , and Content Safety returns detected categories and severity values. The Configure filters interface can then be used to change allowed or prohibited severity levels and retest the samples. Microsoft documents severity classifications including safe, low, medium, and high. Microsoft Learn

Therefore, the proposed Safety metaprompt solution does not meet the stated requirement.

This maps to the AI-103 objectives to configure safety filters, guardrails, risk detection, and content moderation , and to apply responsible-AI safety evaluations. Microsoft Learn

====================

A serverless API deployment exposes a model from the Microsoft Foundry model catalog as a managed inference endpoint without hosting the model on virtual-machine compute in the customer’s subscription. Consequently, it does not consume the subscription’s VM-family vCPU quota. Capacity is managed by the service and controlled through deployment-level token and request rate limits rather than customer-managed compute instances.

The generated serverless endpoint uses key authentication. Foundry provides a target URI and associated primary or secondary credentials that the application uses to authorize inference requests. Serverless deployments support the Azure AI Model Inference API, enabling real-time application access through a consistent API interface suitable for REST-based prediction requests.

A self-hosted container requires customer-managed infrastructure and therefore consumes the compute capacity on which it runs. A compute-backed standard deployment generally requires provisioned hosting resources and applicable quota. A batch deployment is designed for asynchronous, high-volume processing rather than interactive real-time inference.

The serverless option therefore satisfies all three requirements simultaneously: key-based authorization, online API inference, and no dependency on the subscription’s virtual-machine vCPU quota.

Study Guide alignment: Planning and managing Azure AI solutions — select model deployment options, deploy catalog models, configure endpoint authentication, and evaluate compute and quota requirements.

Set tool_choice to: required

Configure the tool to authenticate by: Using a distinct agent identity bound to the client application

Set tool_choice to required because the compliance workflow must deterministically include a tool-based retrieval step before the agent generates a response. Microsoft Foundry Agent Service guidance states that tool_choice provides the most deterministic control over tool use: auto lets the model decide, none prevents tool calls, and required forces the model to call one or more tools. This directly corrects the current nondeterministic behavior where the model decides whether to call tools.

For authentication, use a distinct agent identity bound to the client application . Microsoft Foundry creates a shared identity for unpublished or in-development agents, but publishing an agent automatically creates a dedicated agent identity blueprint and agent identity associated with the agent application resource. Published agents authenticate tool calls by using that unique agent identity, and RBAC permissions must be assigned to the new identity. This provides isolation from the broader shared project identity and supports independent audit trails for compliance workflows.

Storing API keys in prompts violates security guidance and prevents robust audit attribution. The shared project agent identity is easier for development, but it has a broader blast radius and does not meet the isolation requirement. Reference topics: Foundry Agent Service tool choice, tool authentication, published agent identities, RBAC, and auditability.

The correct model type is a large language model (LLM) . The scenario requires an agent that can reason over retrieved documentation, synthesize context-aware answers, and generate detailed natural language responses. Microsoft Foundry RAG guidance defines Retrieval Augmented Generation as a pattern that combines search with large language models so responses are grounded in organizational data, which directly matches the use of Azure AI Search for internal product documentation.

An LLM is also the correct fit for deep, multi-step reasoning across long contexts. Azure AI Search agentic retrieval guidance states that complex chat and agent scenarios use an LLM to break a user query into smaller focused subqueries for better coverage over indexed content. Microsoft also describes Azure AI Search as a way to ground agents and chatbots in proprietary enterprise data for accurate, context-aware responses.

A multimodal model is unnecessary because the requirements are text-focused, not image, audio, or video based. A key phrase extraction model performs narrow text analytics and cannot generate detailed answers. An SLM may reduce cost and latency, but the stated need for deep reasoning and long-context synthesis favors an LLM. Reference topics: Microsoft Foundry RAG, Azure AI Search grounding, agentic retrieval, and model selection for generative AI agents.