Explanation:

The correct answer is "An embedding."
In the context of large language models (LLMs) such as GPT-3, GPT-3.5, or GPT-4, an embedding refers to a multi-dimensional numeric vector representation assigned to each word, token, or phrase. According to the Microsoft Azure AI Fundamentals (AI-900) study guide and Microsoft Learn documentation for Azure OpenAI embeddings, embeddings are used to represent textual or semantic meaning in a numerical form that a machine learning model can process mathematically.
Each embedding captures the semantic relationships between words. Words or tokens with similar meanings (for example, "car" and "automobile") are represented by vectors that are close together in the multi- dimensional space, while unrelated words (like "tree" and "laptop") are farther apart. This vector representation enables the model to understand context, similarity, and relationships between different pieces of text.
Embeddings are fundamental in tasks such as:
* Semantic search: Finding documents or sentences with similar meaning.
* Clustering: Grouping related concepts together.
* Recommendation systems: Suggesting similar content based on text meaning.
* Contextual understanding: Helping generative models produce coherent and context-aware text.
Option review:
* Attention: A mechanism used within transformers to focus on relevant parts of input sequences but not a representation of words.
* A completion: Refers to the generated text output from a model, not the internal representation.
* A transformer: The architecture that powers models like GPT, not the vector representation of tokens.
Therefore, the correct term for a multi-dimensional vector assigned to each word or token in a large language model (LLM) is An embedding, which represents how meaning is numerically encoded and compared within language models.

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation:

This question tests the understanding of features and labels in machine learning, a core concept covered in the Microsoft Azure AI Fundamentals (AI-900) syllabus under "Describe fundamental principles of machine learning on Azure." In supervised machine learning, data is divided into features (inputs) and labels (outputs).
* Features are the independent variables - measurable properties or characteristics used by the model to make predictions.
* Labels are the dependent variables - the target outcome the model is trained to predict.
From the provided dataset, the goal of the Azure Machine Learning model is to predict product quality (Pass or Fail). Therefore:
* Mass (kg) is a feature - Yes"Mass (kg)" represents an input variable used by the model to learn patterns that influence product quality. It helps the algorithm understand how variations in mass might correlate with passing or failing the quality test. Thus, it is correctly classified as a feature.
* Quality Test is a label - YesThe "Quality Test" column indicates the outcome of the manufacturing process, marked as either Pass or Fail. This is the target the model tries to predict during training. In Azure ML terminology, this column is the label, as it represents the dependent variable.
* Temperature (C) is a label - No"Temperature (C)" is an input that helps the model determine quality outcomes, not the outcome itself. It influences the quality result but is not the value being predicted.
Therefore, temperature is another feature, not a label.
In conclusion, per Microsoft Learn and AI-900 study materials, features are measurable inputs (like mass and temperature), while the label is the target output (like the quality test result).

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation:

In Microsoft's Responsible AI framework, the Reliability and Safety principle ensures that AI systems perform consistently, safely, and as intended across diverse conditions - even when faced with incomplete, unusual, or unexpected data. Correctly handling unusual or missing values in a dataset directly demonstrates this principle, as it helps prevent faulty predictions, biased results, or unsafe system behaviors.
According to the Microsoft Learn Responsible AI module (from the AI-900 and AI-102 study paths), a reliable AI model should maintain its performance when encountering data anomalies. This includes validating inputs, managing missing or extreme values, and testing models to ensure they behave as expected in real-world scenarios. Such practices make AI systems robust and trustworthy, which aligns exactly with the Reliability and Safety principle.
The other Responsible AI principles address different concerns:
* Inclusiveness: Ensures AI empowers and serves all users equitably.
* Privacy and Security: Focuses on safeguarding personal data and preventing unauthorized access.
* Transparency: Ensures that AI decisions are understandable and explainable to users.
While all principles are essential, managing data integrity and system stability-including how a model responds to missing or anomalous values-is primarily a matter of reliability and safety. It ensures the AI behaves predictably and minimizes risks of errors or unintended harm.
Therefore, the correct completion of the sentence is:
"Correctly handling unusual or missing values is an example of the application of the Reliability and Safety principle for Responsible AI."

Explanation: Only visible for TestSimulate members. You can sign-up / login (it's free).

Explanation:
Yes, Yes, and No.
According to the Microsoft Azure AI Fundamentals (AI-900) official study materials and the Microsoft Learn module "Identify features of natural language processing (NLP) workloads on Azure", the Azure Translator service is a cloud-based AI service within Azure Cognitive Services that provides real-time text translation across multiple languages.
* "You can use the Translator service to translate text between languages." - Yes.This is the core function of the Translator service. It takes text as input in one language and returns it in another using advanced neural machine translation models. This aligns with the AI-900 learning objective: "Describe the capabilities of Azure Cognitive Services for language", which specifically names Azure Translator as the service used to perform automatic text translation. The service supports over 100 languages and dialects, offering both single-sentence and document-level translations.
* "You can use the Translator service to detect the language of a given text." - Yes.This statement is also true. The Translator service automatically detects the source language if it is not specified in the request. This feature is documented in the Azure Translator API, where the system identifies the input language before performing translation. The AI-900 exam content emphasizes this as one of the Translator service's built-in capabilities-language detection for untagged text.
* "You can use the Translator service to transcribe audible speech into text." - No.This is not a function of Translator. Transcription (converting speech to text) is a speech AI workload, handled by the Azure Speech Service, not Translator. The Speech-to-Text capability in Azure Cognitive Services processes spoken audio input and returns the text transcription. The Translator service only works with text input, not direct audio.
Therefore, based on official AI-900 guidance, the verified configuration is:
# Yes - for text translation
# Yes - for language detection
# No - for speech transcription.
This aligns precisely with the AI-900 learning outcomes describing Text Translation and Language Detection as Translator capabilities, and Speech Transcription as part of the separate Speech service.

Explanation:

According to the Microsoft Azure AI Fundamentals (AI-900) official study materials, object detection is a type of computer vision workload that not only identifies objects within an image but also determines their location by drawing bounding boxes around them. This functionality is clearly described in the Microsoft Learn module "Identify features of computer vision workloads." In this scenario, the AI system analyzes an image to find a vehicle and then returns a bounding box showing where that vehicle is located within the image frame. That ability - to detect, classify, and localize multiple objects - perfectly defines object detection.
Microsoft's study content contrasts object detection with other computer vision workloads as follows:
* Image classification: Determines what object or scene is present in an image as a whole but does not locate it (e.g., "this is a car").
* Object detection: Identifies what objects are present and where they are, usually returning coordinates for bounding boxes (e.g., "car detected at position X, Y").
* Optical Character Recognition (OCR): Extracts text content from images or scanned documents.
* Facial detection: Specifically locates human faces within an image or video feed, often as part of face recognition systems.
In Azure, object detection capabilities are available through services such as Azure Computer Vision, Custom Vision, and Azure Cognitive Services for Vision, which can be trained to detect vehicles, products, or other objects in various image datasets.
Therefore, based on the AI-900 study guide and Microsoft Learn materials, the verified and correct answer is Object detection, as it accurately describes the process of returning a bounding box indicating an object's position in an image.

Explanation:

According to the Microsoft Azure AI Fundamentals (AI-900) official study guide and the Microsoft Learn module "Identify features of common machine learning types", the standard workflow for creating and deploying a machine learning model - especially within Azure Machine Learning Designer - follows a structured sequence of steps to ensure that the model is trained effectively and evaluated correctly.
Here's the detailed breakdown of the correct order:
* Import and prepare a dataset:This is always the first step in the machine learning lifecycle. The dataset is imported into Azure Machine Learning and cleaned or preprocessed. Preparation might include handling missing values, normalizing data, removing outliers, and encoding categorical variables. This ensures the dataset is ready for modeling.
* Split the data randomly into training data and validation data:The dataset is then divided into two parts
- the training set and the validation (or testing) set. Typically, around 70-80% of the data is used for training and 20-30% for validation. This step ensures that the model can be evaluated on unseen data later, preventing overfitting.
* Train the model:During this stage, the machine learning algorithm learns patterns from the training data. Azure Machine Learning Designer provides multiple algorithms (classification, regression, clustering, etc.) that can be applied using "Train Model" components.
* Evaluate the model against the validation dataset:Finally, the trained model's performance is tested using the validation dataset. Evaluation metrics such as accuracy, precision, recall, or RMSE (depending on the model type) are calculated to assess how well the model generalizes to new data.
The incorrect option - "Evaluate the model against the original dataset" - is not used in proper ML workflows, because evaluating on the same data used for training would give misleadingly high accuracy due to overfitting.