AI-300 Sample Questions Answers

Azure Machine Learning ' s experiment tracking is built around two complementary concepts. First, experiments are named containers that group related runs. By calling mlflow.set_experiment with an experiment name at the start of your training code, all subsequent runs are grouped under that experiment name in the AML workspace, creating the centralized record required. Second, metrics are scalar values such as accuracy, loss, or AUC that represent model performance. Calling mlflow.log_metric with a metric name and value during training persists these values to the run ' s record in the experiment history. These values appear on the Azure ML Studio run detail page and can be compared across runs using the experiment comparison view. Without set_experiment, runs fall into a default experiment. Without log_metric, the run history has no performance data to display or compare.

Microsoft Learn Reference Topic: Track machine learning experiments with MLflow in Azure Machine Learning

The MLTable format in Azure Machine Learning Python SDK v2 is a structured abstraction over tabular data sources. It stores a YAML file alongside data files, describing how to read and transform the data. To materialize this into a Pandas DataFrame, you use the mltable library: first call mltable.load with the path to the MLTable folder to load the definition, then call to_pandas_dataframe() on the returned object. The path parameter should point to the folder containing the MLTable YAML file on the default datastore. MLTable abstracts the storage location and transformation steps, making the code storage-agnostic — the same code works whether data lives in Blob Storage, ADLS Gen2, or a local path. The SDK v2 approach with MLTable is the recommended pattern for governed, reusable data access in Azure Machine Learning.

Microsoft Learn Reference Topic: Create and use MLTable data assets in Azure Machine Learning Python SDK v2

The Content Safety evaluator in Microsoft Foundry is specifically designed to detect hate speech, violence, sexual content, and self-harm content in model outputs, making it the most direct evaluator for the requirement of preventing hateful responses. It uses Azure AI Content Safety service under the hood, which is trained to classify content across these harmful categories with high accuracy. Protected Material (option A) evaluates whether outputs contain copyrighted or licensed material — not hate speech. Groundedness (option B) measures factual accuracy against a source context — completely irrelevant to hate detection. Indirect Attacks (option C) evaluates whether the model was manipulated via prompt injection to produce harmful content — this is a robustness metric, not a direct output quality measure. Content Safety must be configured first because detecting hate is the primary safety concern explicitly identified in the requirement.

Microsoft Learn Reference Topic: Content safety evaluators in Microsoft Foundry – Detect harmful content in AI model outputs

Navigate to the Microsoft Foundry project in the Azure portal or Foundry portal and open the prompt flow for which you want to capture telemetry. Locate the Tracing toggle in the project or flow settings and enable it — this single action instructs the Foundry runtime to instrument every LLM call within the flow. Execute test runs of the prompt flow through the portal ' s test interface or via the CLI. Open the Traces view in Microsoft Foundry: each run appears as a trace with a tree of spans, where each span corresponds to one LLM call or tool invocation. Every span captures the exact input sent to the model, the model ' s output, token counts including prompt tokens and completion tokens, and wall-clock latency. Compare runs across prompt variants by examining individual traces side-by-side. This solution directly satisfies all four capture requirements.

Microsoft Learn Reference Topic: Enable and use tracing in Microsoft Foundry – Capturing LLM call telemetry for evaluation

During high traffic, the question is whether the endpoint is keeping up with demand. Requests per minute (B) tells you the actual request load on the endpoint, letting you correlate traffic spikes with degradation. Connections active (C) reveals whether the endpoint ' s connection pool is saturating — too many concurrent connections without adequate scaling causes queuing and timeouts. Request latency (E) is the gold-standard measure of user-perceived performance; rising latency under load is the clearest signal of degradation. Feature count (A) is a model-design attribute, not a runtime performance metric. Dataset size (D) is a training-time concern unrelated to endpoint performance. Azure Machine Learning online endpoints expose these metrics through Azure Monitor, and Microsoft recommends configuring alert rules on latency and request rate thresholds for all production endpoints.

Microsoft Learn Reference Topic: Monitor Azure Machine Learning online endpoints – Azure Monitor metrics for managed endpoints

Microsoft ' s RAG optimization guidance identifies two high-impact, low-cost improvements for retrieval quality that do not require changing the embedding model. First, tuning chunk size and overlap (option A): chunk size determines how much context each retrieved piece contains — too large and irrelevant content dilutes the signal; too small and answers may be split across chunks. Adjusting these parameters requires only re-indexing the documents with zero additional compute cost. Second, implementing a re-ranker (option B): a re-ranker is a cross-encoder model that takes the top-N retrieved chunks and re-scores them based on their specific relevance to the query, significantly improving precision by filtering out contextually irrelevant chunks. Re-rankers add modest compute cost but are far cheaper than changing the embedding model, which would require re-embedding the entire knowledge base. Increasing token limits (option C) and optimizing embedding vector length (option D) do not address retrieval accuracy without an embedding model change.

Microsoft Learn Reference Topic: Optimize RAG pipelines – Chunk size tuning and re-ranking in Azure AI Search and Azure Machine Learning

In Azure Machine Learning, a workspace is the top-level resource that acts as a centralized hub for every ML activity. It stores experiments, pipelines, datasets, models, environments, and compute targets all in one place. Before you can register assets or deploy endpoints, the workspace itself must exist and be shared across the team. Fabrikam ' s core challenge is inconsistent experiment tracking, ad-hoc versioning, and no standardized deployment path — all symptoms of the absence of a single, governed workspace. Option A (registering assets) is a subsequent action only possible after the workspace exists. Option C (online endpoint) is a deployment concern, not an asset-management foundation. Option D (Foundry project) is appropriate for generative AI workloads, not for the traditional ML pipeline standardization described here. The workspace is the prerequisite that makes every other governance action possible.

Microsoft Learn Reference Topic: Azure Machine Learning workspaces – Microsoft Learn: Manage Azure Machine Learning workspaces

MLflow is the industry-standard open-source platform for experiment tracking, and Azure Machine Learning has first-class native integration with it. When you use MLflow within an Azure ML job, parameters, metrics, and artifacts are automatically logged to the run history of the AML workspace, making every run reproducible and comparable. Option A (AML job output logs) only captures console output and lacks structured parameter and metric logging. Option C (Application Insights logs) is designed for application-level telemetry, not ML experiment metadata. Option D (Azure Monitor alerts) is a reactive notification tool, not a tracking system. MLflow ' s autologging capability means that for common frameworks such as scikit-learn, XGBoost, and PyTorch, parameters and metrics are captured without a single line of custom code, directly answering Fabrikam ' s requirement for consistent experiment tracking.

Microsoft Learn Reference Topic: Track ML experiments with MLflow – Azure Machine Learning MLflow integration

Imagine a hospital analytics firm with data scientists who kick off dozens of training jobs throughout the week. During peak hours, five jobs compete for the same GPU cluster and fail or queue for hours. On quiet nights, that cluster sits completely idle, burning money. Managed compute targets with autoscaling solve both problems: the cluster scales out automatically when multiple jobs arrive simultaneously and scales back to zero when idle. Option A (single shared cluster) is exactly the resource-contention problem Fabrikam already has. Option B (fixed-size cluster) wastes money during off-peak hours. Option C (dedicated per-experiment clusters) eliminates contention but is prohibitively expensive for a cost-conscious healthcare firm. Autoscaling managed compute is the cloud-native answer to variable workload demand.

Microsoft Learn Reference Topic: Azure Machine Learning compute targets – Configure autoscale for compute clusters