AI-900 Exam Dumps - Microsoft Azure AI Fundamentals

QnA Maker (now part of Azure AI Language Service – Custom Question Answering) enables bots to answer user queries by extracting questions and answers from structured sources like FAQs, webpages, and documents (e.g., Word, PDF). In this scenario, where data comes from a Microsoft Word troubleshooting guide and a FAQ webpage, QnA Maker automatically extracts knowledge and creates a searchable knowledge base.

Other options are incorrect:

A. Language Understanding (LUIS): Detects intents, not question-answer pairs.

B. Text Analytics: Extracts key phrases and sentiment but does not support conversational responses.

C. Azure Bot Service: Hosts bots, but it requires QnA Maker for knowledge sources.

To improve the quality and relevance of responses generated by a generative AI solution using GPT-3.5, the following three actions are emphasized in the Microsoft Learn: Azure OpenAI Service best practices and AI-900/AI-102 training materials:

(A) Add grounding data to prompts: Grounding ensures that the model’s output is based on factual, domain-specific information. By adding context or external knowledge sources, responses become more accurate and aligned with the organization’s data rather than relying on the model’s general training corpus.

(B) Provide additional examples to prompts: Also known as few-shot prompting, this method demonstrates desired response patterns by including examples in the prompt. This significantly improves output quality, consistency, and adherence to desired formats.

(E) Modify system messages: In Azure OpenAI chat completions, system messages define the model’s behavior, style, and tone. Adjusting system messages allows fine-tuning of the model’s response quality, ensuring it follows context or persona guidelines.

The remaining options are incorrect:

(C) Modify tokenization is a low-level text-processing technique not used to improve model response quality directly.

(D) Add training data to prompts is not possible at runtime since GPT-3.5 models are pre-trained; only prompt engineering can influence output behavior.

Therefore, based on Azure OpenAI and AI-900 guidance, the three best ways to enhance generative

Microsoft’s Responsible AI principles are the foundation for developing and deploying ethical and trustworthy AI systems. The six key principles are Fairness, Reliability and Safety, Privacy and Security, Inclusiveness, Transparency, and Accountability. Each principle guides specific practices for ensuring AI systems operate responsibly in real-world applications like automated insurance quoting systems.

Transparency – This principle ensures that the AI’s decisions can be understood and explained. Recording the decision-making process and enabling staff to trace how a quote was generated aligns with transparency. It allows stakeholders to interpret the reasoning behind model outputs, ensuring that the AI behaves predictably and ethically.

Privacy and Security – This principle focuses on protecting personal data and ensuring that sensitive information is handled responsibly. Limiting access to customer data only to authorized personnel maintains compliance with privacy laws (like GDPR) and safeguards against misuse. Microsoft emphasizes that AI systems should maintain strict control over data visibility and integrity.

Inclusiveness – This principle ensures that AI systems are accessible to all users, including people with disabilities. By supporting screen readers and assistive technologies, the system ensures equal access to information and services for every customer. Inclusiveness prevents discrimination and promotes accessibility, both of which are central to Microsoft’s Responsible AI strategy.

Thus, the correct mapping of principles is:

Decision process → Transparency

Personal information visibility → Privacy and Security

Accessibility via screen readers → Inclusiveness.

According to the Microsoft Azure AI Fundamentals (AI-900) study guide, the three main types of supervised and unsupervised machine learning models—classification, clustering, and regression—are used for distinct problem types depending on the structure of the data and the prediction goal.

Clustering is an unsupervised learning technique used when the goal is to group items with similar characteristics without predefined labels. In this scenario, “Assign categories to passengers based on demographic data” implies automatically grouping passengers based on patterns such as age, income, or travel frequency, without any prior labeling. This directly maps to clustering, which discovers hidden groupings (for example, segmenting customers into categories like business travelers or vacationers).

Regression is a supervised learning method used to predict continuous numerical values. The scenario “Predict the amount of consumed fuel based on flight distance” is a classic regression problem because the output (fuel consumption) is a continuous variable dependent on another continuous variable (distance). Regression models, such as linear regression, are trained to estimate numeric outputs.

Classification is also a supervised learning approach, but it predicts discrete categories or outcomes. The scenario “Predict whether a passenger will miss their flight based on demographic data” involves a binary decision (missed or not missed), which is typical of classification tasks. These models learn from labeled examples to assign new instances to specific categories.

In summary, Clustering groups similar passengers, Regression predicts continuous numerical outcomes, and Classification determines categorical outcomes. This alignment precisely matches the definitions in Microsoft’s AI-900 learning objectives under “Describe common machine learning types and scenarios.”

When building a K-means clustering model, all features (variables) used in the model must be numeric in nature. According to the Microsoft Azure AI Fundamentals (AI-900) study materials and standard machine learning theory, K-means clustering is an unsupervised learning algorithm that groups data points into clusters based on their similarity — specifically by minimizing the Euclidean distance between data points and their assigned cluster centroids.

Because the K-means algorithm depends on distance calculations, it requires numeric data types. The Euclidean distance (or similar measures) can only be computed between numerical values. Therefore, all categorical or text data must first be converted into numeric form through feature engineering techniques such as one-hot encoding, label encoding, or embedding vectors, depending on the nature of the data.

Here’s how K-means works in summary:

The algorithm initializes a predefined number of centroids (K).

Each data point is assigned to the nearest centroid based on numeric distance.

The centroids are recalculated as the mean of the points in each cluster.

The process repeats until convergence.

If non-numeric data (e.g., text or Boolean) were provided, the model would not be able to calculate distances accurately, leading to computational errors.

Other options are incorrect:

Boolean and integer types can represent numeric values but are considered special cases; the algorithm requires general numeric representation (e.g., continuous values).

Text cannot be processed directly without conversion.

Thus, according to Azure Machine Learning and AI-900 official concepts, all features in a K-means clustering model must be numeric to ensure valid mathematical operations and clustering accuracy.

According to Microsoft’s Responsible AI Principles, Transparency means that AI systems should clearly communicate how they operate, including data sources, limitations, and decision-making processes. Stating the source of data used to train a model helps users understand where the model’s knowledge comes from, enabling informed trust and accountability.

Transparency ensures that organizations disclose relevant details about data collection and model design, especially for compliance, fairness, and reproducibility.

Other options are incorrect:

A. Fairness: Focuses on avoiding bias and ensuring equitable outcomes.

C. Reliability and safety: Ensures AI performs consistently and safely.

D. Privacy and security: Protects user data and maintains confidentiality.

Thus, the principle illustrated by disclosing training data sources is Transparency.

According to the Microsoft Learn documentation for Azure AI Document Intelligence (formerly Form Recognizer) and the AI-900 official study materials, the prebuilt receipt model in Azure AI Document Intelligence supports analyzing image and PDF files up to a maximum size of 10 MB per document.

Azure AI Document Intelligence is a cloud-based service that applies advanced optical character recognition (OCR) and machine learning to extract structured information from documents such as receipts, invoices, identity cards, and business forms. The prebuilt receipt model is specifically designed to extract key data fields from retail receipts—such as merchant name, transaction date, items purchased, subtotal, tax, and total—without requiring users to build or train a custom model.

As per Microsoft’s service limits, the input file for the prebuilt models (including receipts, invoices, business cards, and identity documents) must:

Not exceed 10 MB in file size.

Not exceed 17 x 17 inches (43 x 43 cm) in physical dimensions.

Be in a supported image or document format such as JPG, PNG, BMP, TIFF, or PDF.

Let’s examine why other options are incorrect:

A. 5 MB → Too small; the service allows up to 10 MB.

C. 50 MB and D. 100 MB → Exceed the official maximum file size supported by Azure AI Document Intelligence.

Therefore, when using the prebuilt receipt model, you must ensure that the input file is 10 MB or smaller to be successfully processed by the service.