The key concept here is low-priority (spot) VMs, which are available at a significant discount because Azure can reclaim them at any time. Azure Machine Learning compute clusters are the only target in the list that directly supports low-priority VM nodes as a cost-saving configuration. You set the minimum and maximum node counts and specify that new nodes should be provisioned as low-priority. Azure Container Instances (ACI) does not support low-priority pricing. Local deployment runs on the developer ' s machine with no Azure billing model. Azure Kubernetes Service (AKS) does support spot node pools but requires significantly more infrastructure management and is not the primary mechanism for low-priority compute in Azure Machine Learning. The exam tests whether you know that AML compute clusters are the managed way to leverage low-priority discounts inside Azure Machine Learning.
Microsoft Learn Reference Topic: Create and manage Azure Machine Learning compute clusters - Low- priority VMs

Explanation:
For tracking changes across contributors, Git integration is the answer: by connecting the Microsoft Foundry project to a Git repository, every prompt file change is tracked as a commit with author attribution, timestamp, and diff view, and pull requests enforce review before changes reach production. The Git history provides the complete audit trail and rollback capability needed for traceability. For allowing applications to consume updated prompts without requiring redeployment, Microsoft Foundry ' s prompt management feature allows prompts to be stored and versioned as named artifacts in the project. Applications reference prompts by name and load the latest approved version at inference time, rather than having prompt text hard-coded in the application deployment artifact. This decoupling means updating a prompt is a content operation - not a code deployment - so applications automatically pick up the new prompt without any redeployment.
Microsoft Learn Reference Topic: Prompt management in Microsoft Azure AI Foundry - Git integration and dynamic prompt versioning

Define the evaluation dataset with input prompts and expected outputs covering both quality and safety scenarios. Configure built-in evaluators such as Coherence, Fluency, Groundedness, and Content Safety alongside custom Python evaluator functions for domain-specific safety checks. Create a GitHub Actions workflow that triggers on pull requests or merges to the main branch, calling the Azure AI evaluation SDK to run the evaluation job automatically. Add a quality gate by parsing the evaluation results and using a conditional step to fail the workflow when thresholds are not met. Configure GitHub branch protection rules to require the evaluation workflow to pass, preventing merging or deploying code that fails the quality gate.
Enabling application tracing (option A) and monitoring latency (option C) are runtime monitoring tools, not release gates. Reviewing results manually after deployment (option B) directly contradicts the requirement to eliminate manual evaluation.
Microsoft Learn Reference Topic: Automate AI evaluation in CI/CD with GitHub Actions - Microsoft Foundry evaluation integration

Explanation:
Microsoft ' s documentation on Azure Machine Learning model monitoring describes a layered alerting architecture. At the base layer, Azure ML model monitors compute drift, prediction, and data quality metrics on a scheduled basis and publish results as Azure Monitor metrics. To notify stakeholders, you create an Azure Monitor alert rule that watches these metrics and fires an action group when a threshold is breached.
Action groups support email, SMS, push notifications, and webhook calls. To initiate automated retraining, the webhook call in the action group targets an Azure ML pipeline ' s REST endpoint, triggering a retraining run. Alternatively, Azure Event Grid subscriptions on AML workspace events can route model-quality events to Azure Functions that start pipelines. The separation of monitoring, alerting, notification, and remediation is intentional, allowing each component to be updated independently.
Microsoft Learn Reference Topic: Set up model monitoring for data and model quality - Azure Machine Learning model monitoring

Explanation:
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