Free Microsoft AI-300 Practice Exam with Questions & Answers

Azure Machine Learning infrastructure can be described as Infrastructure as Code using ARM templates, Bicep, or Terraform. To make provisioning fully automated, two separate concerns must be addressed. First, the trigger: a CI/CD system like GitHub Actions or Azure DevOps Pipelines must detect changes to IaC template files in the repository, configured through a branch-push or pull-request trigger. Second, the execution: the CI/CD pipeline runs the provisioning commands such as az ml workspace create or bicep deploy non-interactively using a service principal or managed identity, eliminating the need for a human to run scripts manually. Together, these two mechanisms deliver the GitOps-style automation that modern MLOps practices require, ensuring every template change automatically results in a consistent, auditable infrastructure update.

Microsoft Learn Reference Topic: Automate Azure Machine Learning with GitHub Actions – CI/CD for ML infrastructure

MLflow training runs produce model artifacts — the serialized model files, conda environment, and MLmodel specification — stored in the run ' s outputs folder. These artifacts are transient run outputs but are not yet a versioned, named model that can be deployed. To make the model a first-class, versioned, deployable artifact, you must explicitly register it. Locating artifacts from the run (action A) is necessary because you need the run ' s artifact URI, typically in the form runs:/run_id/model, to register from. Registering in the AML workspace (action B) creates an entry in the model registry with a name and auto-incremented version, making the model discoverable, governable, and deployable across environments. Tagging the experiment (option C) does not version the model. Exporting to local storage (option D) removes the model from Azure ML ' s managed infrastructure, losing lineage and governance.

Microsoft Learn Reference Topic: Register MLflow models in the Azure Machine Learning model registry

Enabling tracing via the prompt flow SDK alone does not guarantee that all four required dimensions — inputs, outputs, token usage, and latencies — are captured and surfaced in the Microsoft Foundry portal ' s trace viewer in a way that allows manual comparison across runs. While the prompt flow SDK does support tracing configuration, the portal-based Tracing activation is the complete, supported path for this specific capture requirement. The correct and complete solution as confirmed by the next question in this series is to use the Tracing toggle directly in the Microsoft Foundry portal for the project, then execute test runs. This portal-side Tracing feature is purpose-built to instrument all four dimensions and store them in a queryable trace store accessible through the Foundry interface.

Microsoft Learn Reference Topic: Enable tracing for prompt flows in Microsoft Foundry portal – Capturing run telemetry

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

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

A system requesting predictions synchronously during customer interactions needs sub-second responses, while a system submitting files with millions of records can tolerate minutes of processing time. For real-time synchronous serving, a Managed Online Endpoint provisions a persistent always-on container behind an HTTPS REST endpoint that returns predictions within milliseconds. For large-batch asynchronous scoring, a Batch Endpoint accepts a data asset input, distributes scoring across a compute cluster, and writes results back to storage. Online endpoints support auto-scaling based on request volume and traffic splitting. Batch endpoints are invoked on-demand or on a schedule, automatically provisioning and de-provisioning compute, keeping costs low for intermittent large jobs. Each deployment type is purpose-built for its usage pattern and should not be swapped.

Microsoft Learn Reference Topic: Deploy and score models with managed online endpoints and batch endpoints – Azure Machine Learning

According to Microsoft ' s Azure Machine Learning SDK v2 documentation on command jobs, input arguments in the command string must exactly match the argument names defined in the Python script ' s argparse configuration. The script reads an argument named training_data with an underscore, but the proposed command passes --trainingdata without the underscore. Python ' s argparse treats these as completely different argument names, so the script would receive None for its --training_data argument, causing a runtime error. The placeholder syntax for referencing the input in the command string is correct, which is a point in this solution ' s favor. However, the argument name mismatch alone is sufficient to make this solution fail. The corrected command would use --training_data exactly matching the argument name defined in the script.

Microsoft Learn Reference Topic: Configure command job inputs and outputs – Azure Machine Learning SDK v2 reference

Microsoft ' s Azure AI Foundry documentation defines built-in roles scoped to the resource hierarchy. The Azure AI Administrator role grants permissions to manage the Azure AI Hub resource itself — including network settings, shared connections, quota, and governance configuration — which is appropriate for platform engineers who configure resource-level settings. The Azure AI Developer role grants permissions to create, update, and manage project-level assets such as deployments, prompt flows, fine-tuning jobs, and evaluations, without access to resource-level configuration. This precisely matches the developer requirement and enforces least privilege. Disabling Entra ID authentication (option B) violates security policy and removes the identity-based access control that makes RBAC possible. Sharing a single API key (option D) violates the least-privilege principle — all users would have identical, undifferentiated access with no audit trail.

Microsoft Learn Reference Topic: Manage access to Azure AI Foundry – Built-in roles: Azure AI Administrator and Azure AI Developer

Microsoft ' s Azure Machine Learning documentation on registries describes them as organization-level repositories that sit above individual workspaces. When you publish an asset such as a model, environment, or component to an Azure ML registry, it becomes accessible to any workspace in any subscription within the same Azure tenant, all without physical duplication. The registry maintains a single source of truth with full version history. Option A (Git integration) synchronizes code, not compiled ML artifacts. Option B (pipeline component) packages a reusable pipeline step but does not solve cross-workspace sharing. Option C (shared environment) addresses runtime dependencies, not the full range of ML assets. The registry is the purpose-built solution for centralized governance, version control, and cross-workspace asset sharing — the Microsoft-recommended pattern for mature MLOps organizations.

Microsoft Learn Reference Topic: Share assets across workspaces with Azure Machine Learning registries

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