Microsoft AI-103 Practice Test Questions Answers

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

TextAnalyticsClient.recognize_entities invokes Azure Language ' s pretrained Named Entity Recognition (NER) capability. NER identifies recognized concepts in unstructured text and assigns supported categories such as Person, Organization, Location, DateTime, Quantity, and related entity classes.

No training dataset or custom model is required, which directly satisfies the question.

recognize_pii_entities is designed for personally identifiable and sensitive information. Although there is some overlap in certain entity classes, its purpose is privacy detection and redaction rather than general NER.

NamedEntityRecognitionSkill is an Azure AI Search enrichment skill. It would be appropriate if the text were being processed as part of an AI Search indexing pipeline, but the question states that the application already uses TextAnalyticsClient, so adding Search would unnecessarily increase complexity.

Custom Entity Recognition is required when an organization needs domain-specific entities not adequately covered by pretrained categories. It requires labeling training data and training a custom Language model, directly contradicting the requirement to avoid training.

The correct method is therefore A, recognize_entities .

Study Guide alignment: Implement text analysis solutions → extract entities, topics, summaries, and structured information using Foundry Tools .

Configure hybrid search , which executes full-text and vector queries within the same Azure AI Search request. The full-text component searches the product-name and product-code fields through the lexical index, providing the precision required for exact or near-exact identifiers. Microsoft specifically identifies product codes and other specialized terms as scenarios that frequently perform better with keyword search.

The vector component compares the embedding of the user’s natural-language query with the embeddings stored for product descriptions. This retrieves semantically similar products even when the query and indexed description do not share the same literal words. Azure AI Search runs the full-text and vector searches in parallel and combines their result sets by using Reciprocal Rank Fusion, returning one unified ranking to the Foundry agent.

Keyword-only search would preserve exact matching but perform poorly for conceptual or paraphrased descriptions. Vector-only search supports semantic similarity but can miss precise product codes and rare identifiers. Semantic search alone reranks text-search results using language understanding; it does not replace the vector query required to use the existing embedding field.

Study Guide alignment: configure semantic, hybrid, and vector search for grounding, choose an appropriate retrieval method, and connect retrieval pipelines to agent tools .

Use image type detection to distinguish drawings from ordinary photographic content. Azure Vision’s ImageType visual feature returns information including lineDrawingType, which indicates whether the submitted image is a line drawing, and clipArtType, which estimates whether it is clip art. The application can use these pretrained results to implement the required photograph-versus-drawing categorization without collecting labeled images or training a custom classifier.

Use image descriptions to generate the caption. Azure Vision Image Analysis provides the Caption visual feature, which generates a concise, one-sentence description of the overall image. Dense Captions can additionally describe individual regions, but the standard Caption feature directly satisfies the stated requirement.

Object detection identifies and locates individual objects by using bounding boxes; it does not determine whether the entire image is a photograph or drawing. Content tags produce descriptive keywords rather than a natural-language caption. Azure Custom Vision classification could be trained for the image-type distinction, but it would require image collection, labeling, training, evaluation, and deployment, increasing development effort unnecessarily.

Study Guide alignment: configure applications to produce captions and implement solutions that identify visual characteristics within images .

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

The first statement is No because automatic Responsible AI checks applied to a fine-tuning dataset are separate from the runtime content-filter threshold. Changing the runtime filter from high to low does not correct unsafe or disallowed training examples that cause the fine-tuning safety evaluation to fail.

The second statement is Yes . A medium severity threshold evaluates or flags a broader set of content than a high-only threshold. Consequently, Run1 can legitimately report a larger defect rate—12%—while Run2 reports only 4%.

The third statement is also Yes . Protected-material evaluation is a separate evaluation dimension from the standard harmful-content severity categories. Because both runs use the same dataset and protected-material evaluator, an identical 6% result is consistent even though the harmful-content threshold changes.

The key distinction is between runtime harmful-content thresholds , protected-material detection , and automatic RAI checks for training/fine-tuning data . They are related responsible-AI controls but operate independently.

The AI-103 Study Guide covers safety filters, risk detection, safety evaluations, and responsible-AI instrumentation as separate operational controls. Microsoft Learn

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

Azure Custom Vision uses a supervised machine-learning workflow. The first requirement is to create a Custom Vision project , where you select the project type and domain. Because the application must detect business-specific component faults, the model requires organization-specific labeled training images rather than relying solely on a general pretrained image-analysis capability.

Next, upload and tag representative images . For object detection, tagging includes drawing bounding regions around the faulty components or defect regions and associating those regions with appropriate tags. Training quality depends strongly on having sufficiently varied examples representing lighting, orientation, component position, normal conditions, and defect types.

Finally, train the object detection model . Custom Vision uses the annotated regions to create a model capable of returning both the predicted tag and the bounding box for each detected fault. “Train the classifier model” is inappropriate because classification assigns a category to the overall image and does not provide object locations. “Initialize the training dataset” is not a separate required Custom Vision portal/API lifecycle step.

The AI-103 Study Guide maps this scenario to implement solutions that identify objects, components, or regions within images or video . Microsoft Learn

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