Microsoft AI-900 Online Access

According to the Microsoft Azure AI Fundamentals (AI-900) official study guide and Microsoft Learn module “Identify features of Natural Language Processing (NLP) workloads and services,” the Azure Cognitive Service for Language – Question Answering capability is designed to allow applications to respond to user questions using information from a prebuilt or custom knowledge base. It relies on Natural Language Processing (NLP) to match user queries to the most relevant answers but does not directly execute queries against databases or infer user intent.

“You can use Language Service’s question answering to query an Azure SQL database.” → NOThe Question Answering feature does not connect directly to or query structured databases such as Azure SQL. Instead, it retrieves answers from unstructured or semi-structured content (FAQs, manuals, documents). Querying SQL databases would require traditional database access, not a cognitive service.

“You should use Language Service’s question answering when you want a knowledge base to provide the same answer to different users who submit similar questions.” → YESThis statement is correct and aligns exactly with Microsoft’s official documentation. Question Answering enables organizations to create a knowledge base that can automatically answer repeated or similar customer queries using natural language understanding. For instance, two users asking “How do I reset my password?” and “Can you help me change my password?” would receive the same predefined response.

“Language Service’s question answering can determine the intent of a user utterance.” → NODetermining user intent is handled by Language Understanding (LUIS) or Conversational Language Understanding, not by Question Answering. While both belong to the Language Service, Question Answering focuses on retrieving relevant answers, whereas LUIS focuses on intent detection and entity extraction.

According to the Microsoft Azure AI Fundamentals (AI-900) official study materials and Microsoft Learn module “Describe features of common AI workloads,” an anomaly detection workload is designed to identify data points or patterns that deviate significantly from what is expected or normal. These anomalies often indicate irregularities, faults, or potential issues that require attention.

In this scenario, the AI system monitors temperature data from a large machine. Normally, the machine operates within a predictable temperature range. When the AI detects sudden or unexpected temperature spikes or drops — behavior that does not match the historical pattern — it flags these occurrences as anomalies. This type of workload is fundamental in predictive maintenance and industrial monitoring, where it helps detect equipment failures, safety hazards, or energy inefficiencies before they escalate.

Microsoft’s AI-900 curriculum emphasizes that anomaly detection workloads are often used in:

Industrial IoT systems (detecting abnormal sensor readings or machine behavior)

Finance (fraud detection or unusual transaction monitoring)

Cybersecurity (detecting irregular network traffic or access patterns)

Operations (identifying abnormal variations in production data)

The Azure service used for this purpose is Azure Anomaly Detector, part of Azure Cognitive Services, which uses advanced statistical and machine learning models to automatically detect outliers in time-series data such as temperature, pressure, or transaction logs.

By comparison:

Computer vision handles image or video analysis.

Knowledge mining extracts insights from large document collections.

Natural Language Processing (NLP) interprets human language.

Thus, based on the official Microsoft AI-900 study guide and Microsoft Learn, the correct and verified answer is An anomaly detection workload, since detecting unusual temperature fluctuations precisely fits this AI workload type.

Model Explain Ability.

Most businesses run on trust and being able to open the ML “black box” helps build transparency and trust. In heavily regulated industries like healthcare and banking, it is critical to comply with regulations and best practices. One key aspect of this is understanding the relationship between input variables (features) and model output. Knowing both the magnitude and direction of the impact each feature (feature importance) has on the predicted value helps better understand and explain the model. With model explain ability, we enable you to understand feature importance as part of automated ML runs.

The correct answer is B. Randomly split the data into rows for training and rows for evaluation.

According to the Microsoft Azure AI Fundamentals (AI-900) official study guide and the Microsoft Learn module “Describe fundamental principles of machine learning on Azure”, the process of developing a machine learning model involves dividing the available dataset into two or more parts—commonly training data and evaluation (or testing) data. The goal is to ensure that the model can learn patterns from one subset of the data (training set) and then be objectively tested on unseen data (evaluation set) to measure how well it generalizes to new situations.

The training dataset contains both features (the measurable inputs) and labels (the target outputs). The model learns from the patterns and relationships between these features and labels. The evaluation dataset also contains features and labels, but it is kept separate during the training phase. Once the model has been trained, it is tested on this unseen evaluation data to calculate metrics like accuracy, precision, recall, or F1 score.

Microsoft emphasizes that the data split should be random and based on rows, not columns. Each row represents a complete observation (for example, one customer record, one transaction, or one image). Randomly splitting ensures that both subsets represent the same distribution of data, avoiding bias. Splitting by columns would separate features themselves, which would make the model training invalid.

The AI-900 materials often illustrate this using Azure Machine Learning’s data preparation workflow, where data is randomly divided (commonly 70% for training and 30% for testing). This ensures the model learns from diverse examples and is fairly evaluated.

Therefore, the verified and correct approach, as per Microsoft’s official guidance, is B. Randomly split the data into rows for training and rows for evaluation.