Pass the Microsoft Azure AI Engineer Associate AI-103 Questions and answers with ExamsMirror

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

Azure Vision Image Analysis provides a pretrained image-tagging capability that generates descriptive tags for visual content. The service can identify concepts such as objects, scenes, activities, and other image characteristics and return confidence values for the generated tags.

Because this is a pretrained capability, no custom training dataset, labeling process, training iteration, or prediction-resource deployment is required. That directly satisfies the requirement to minimize development effort.

Image Analysis also supports localized output for supported features and languages, allowing an application to request results appropriate for users who prefer English, French, or Spanish. The application therefore avoids implementing a separate tag-generation model followed by an additional translation workflow.

Azure Custom Vision image classification is intended for business-specific categories and would require labeled training images. Content Safety classifies harmful or inappropriate content rather than producing general-purpose descriptive image tags. Custom Translator can translate text but cannot inspect an image and determine which tags describe it.

The AI-103 Study Guide includes multimodal image analysis and extracting visual characteristics as part of the computer-vision skill domain. Microsoft Learn

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

The correct answer is A. Set the input_fidelity parameter to high . The scenario requires the generated image to preserve the identity and visual characteristics of the user-supplied product photo. In Azure OpenAI image editing and generation workflows, input_fidelity controls how strongly the model attempts to match the style and features of the input image. Microsoft’s documentation states that this parameter lets you make subtle edits without changing unrelated areas, and that high input fidelity preserves input-image features more accurately than standard mode.

Including a prompt and input image is necessary for image-guided generation, but it does not by itself maximize preservation of the product’s appearance. The explicit preservation control is input_fidelity, and the requirement specifically asks to maintain product identity and visual characteristics. A groundedness detection filter applies to validating generated text against source data, not preserving visual features in image generation. Lowering temperature may reduce randomness in text generation, but it is not the image-control parameter used to retain product-specific visual details. Reference topics: Azure OpenAI image generation, image edit API, input images, input_fidelity, image-to-image generation, and visual identity preservation.

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

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

Select AI quality (AI assisted) metrics for groundedness and relevance. Groundedness evaluates whether the generated answer is supported by the retrieved RAG context, while relevance evaluates whether the answer appropriately addresses the user’s query. These evaluations use an AI judge model to assess meaning and contextual alignment rather than relying only on exact token matches. Microsoft Foundry categorizes groundedness and relevance as quality evaluators and requires a compatible judge-model deployment for AI-assisted evaluation.

Select risk and safety metrics to evaluate harmful-content categories. These evaluators detect and score content involving violence, sexual material, self-harm, and hate or unfairness. They provide the safety dimension required alongside the RAG quality measurements.

AI quality NLP metrics include mathematically calculated measures such as F1, BLEU, GLEU, ROUGE, and METEOR. These primarily compare token or n-gram overlap with reference answers and do not provide the requested groundedness and content-harm assessments. A fluency evaluator measures language readability, while a similarity evaluator compares a response with ground truth; neither is a complete evaluation category covering the requirements.

Study Guide alignment: evaluate generative AI solutions by using quality, groundedness, relevance, risk, and safety metrics .

Extract the text: Azure Vision in Foundry Tools

Identify well-known locations: Azure Language in Foundry Tools

Azure Vision in Foundry Tools is the appropriate service for extracting text from road signs. Its pretrained Optical Character Recognition capability detects printed or handwritten text in images and returns recognized words, lines, and their coordinates. Microsoft specifically identifies street signs as an applicable OCR scenario. Because the OCR model is already trained, it avoids the data labeling and custom-model training that would increase development effort.

After OCR produces the text, Azure Language in Foundry Tools can analyze it through entity linking . Entity linking recognizes and disambiguates well-known entities and connects them to entries in a recognized knowledge base. This is suitable for determining that text on a sign represents a known geographic location rather than merely returning an unclassified text string. Named entity recognition can also classify extracted entities under categories such as Location, but entity linking provides the stronger interpretation implied by “well-known locations.”

Azure Document Intelligence is optimized for structured and text-heavy business documents, while Azure AI Search provides indexing and retrieval rather than primary OCR and linguistic analysis.

Study Guide alignment: implement OCR-based ingestion and use Foundry Tools to extract entities from text .

Foundry Control Plane obtains agent observability information from the Application Insights resource connected to the Foundry project that hosts the agent. When the telemetry is available, Control Plane uses it to calculate run counts and error rates, report usage metrics such as token consumption and cost, and display execution traces. Microsoft’s guidance explicitly directs administrators to configure Application Insights when these values are absent.

Application Insights must be connected to the project, and the agent or application must emit the applicable OpenTelemetry data. Traces are stored in Application Insights and surfaced through both the Foundry portal and Azure Monitor. Microsoft’s tracing procedure requires connecting an Application Insights resource to the Foundry project before trace records can be displayed.

A Log Analytics workspace can provide the underlying storage for a workspace-based Application Insights resource, but assigning a workspace alone does not configure the project’s agent telemetry connection. Restarting Agent1 does not add instrumentation or a telemetry destination. Creating a new agent version also does not resolve the missing observability configuration.

Study Guide alignment: Integrate monitoring into deployed agents and set up observability by implementing tracing, token analytics, safety signals, latency analysis, and error investigation.

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.

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

Spatial Analysis is the appropriate capability because the requirement is to analyze a video stream and determine how many people are present in a defined physical space.

Spatial Analysis provides pretrained person-detection and spatial-event functionality that can monitor occupancy, presence, and movement without requiring the developer to build a custom person-detection model. The application can use those detections to determine whether more than one person appears within the monitored area and generate an appropriate violation event.

Custom Vision object detection could theoretically be trained to detect people, but doing so would require data collection, labeling, model training, deployment, and additional application logic. That conflicts with the requirement to minimize development effort.

Speech-to-text analyzes microphone audio and cannot determine how many people are visually present. Azure AI Video Indexer derives insights from video but is not the specialized real-time physical-space monitoring solution represented by this scenario.

The AI-103 Study Guide includes implementing solutions that identify objects, components, or regions within images or video and building video understanding workflows, making Spatial Analysis the appropriate pretrained service choice. Microsoft Learn

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

The correct answer is A. Speech recognition requests will fall back to the most recent base model for the same locale . Microsoft’s custom speech model lifecycle guidance states that when a model expires, it is no longer available for transcription. For the custom endpoint route, speech recognition requests fall back to the most recent base model for the same locale. The documentation also warns that recognition results might still be returned, but the transcription may no longer reflect the domain-specific adaptation of the custom model.

This distinguishes real-time custom endpoint behavior from batch transcription behavior. Batch transcription requests that specify an expired model fail with a 4xx error, but that is not the route described in this question. The agent is using a custom endpoint for real-time recognition, so fallback to the latest base model is the expected behavior. The model is not automatically deleted merely because it expires, and it does not continue to use the expired custom model indefinitely. The operational recommendation is to update the endpoint’s model before expiration by redeploying the endpoint with a newer custom model. Reference topics: Azure Speech custom speech model lifecycle, custom endpoints, model expiration, real-time speech recognition, and endpoint redeployment.