Free Microsoft AI-300 Practice Exam with Questions & Answers

Azure Machine Learning Studio explicitly distinguishes actions that merely interrupt execution from actions that reset notebook state and clear variables . Microsoft documents three relevant operations that reset notebook state: changing the kernel, switching compute, and resetting compute .

C. Reset the compute restarts the notebook execution environment. When another cell is subsequently executed, the compute environment starts again and the previous in-memory notebook state is no longer retained.

D. Change the current kernel causes the notebook to use a different kernel. Because variables, imported objects, and other runtime state belong to the active kernel process, changing the kernel resets that execution state.

E. Change the compute switches the notebook to another compute resource. Microsoft states that switching compute automatically connects the notebook to the selected compute and resets the notebook state and variables.

By contrast, B. Stop the current kernel only stops a currently running cell; executing another cell automatically restarts the kernel while the notebook-state behavior documented for this action does not constitute a reset. Likewise, A. navigating to another workspace section stops running cells but does not reset variables or notebook state.

Study Guide Reference: Implement machine learning model lifecycle and operations — Azure Machine Learning notebooks, compute instances, kernel management, execution environments, and interactive development.

Step 1: Create an Azure DevOps project

Step 2: Create a release pipeline

Sign in to your Azure DevOps organization and navigate to your project.

Go to Pipelines, and then select New pipeline.

Step 3: Install the Machine Learning extension for Azure Pipelines

You must install and configure the Azure CLI and ML extension.

Step 4: Create a service connection

How to set up your service connection

Select AzureMLWorkspace for the scope level, then fill in the following subsequent parameters.

Note: How to enable model triggering in a release pipeline

Go to your release pipeline and add a new artifact. Click on AzureML Model artifact then select the appropriate AzureML service connection and select from the available models in your workspace.

Enable the deployment trigger on your model artifact as shown here. Every time a new version of that model is registered, a release pipeline will be triggered.

All three requirements point to Git as the underlying mechanism, but each uses a different Git capability. For reviewing changes before production: a branch-based workflow where prompt changes are made on feature branches and merged to the main branch only after pull request approval enforces the review gate. For restoring previous versions: Git ' s commit history and tag system provide a precise, immutable record of every prompt state, and a git revert or checkout to a specific commit SHA restores any prior version instantly. For governance parity with application code: by storing prompts in the same Git repository as application code, all the same CI/CD, branch protection, code review, and audit trail policies apply automatically. The alternatives such as Blob Storage or embedded configuration files lack native review workflows, branch protection, and full audit history.

Microsoft Learn Reference Topic: Prompt management and versioning with Git integration in Microsoft Foundry

Data asset type: mltable

Scheme of the URL paths to storage locations: wasbs

The correct data asset type is mltable because the image collection is distributed across multiple storage locations . Microsoft identifies MLTable as the appropriate Azure Machine Learning data asset type when unstructured data such as images, text, or audio is spread across multiple storage locations. An MLTable definition can contain multiple file, folder, or pattern entries, allowing one logical data asset to reference image data residing in different storage accounts.

A uri_folder data asset is appropriate when the required unstructured files reside within a single folder path . It represents one folder location and therefore does not provide the same multi-path abstraction required by this scenario. uri_file represents only an individual file and is clearly unsuitable for a collection of images.

For the path scheme, Azure Machine Learning uses wasbs:// for Azure Blob Storage. Microsoft documents the canonical format as:

wasbs:// < container > @ < account > .blob.core.windows.net/ < path >

By comparison, abfss:// is used for Azure Data Lake Storage Gen2, while azureml:// identifies Azure Machine Learning datastore paths rather than direct Azure Blob Storage URLs.

Therefore, an MLTable containing multiple wasbs:// paths correctly represents image files distributed across the two Azure Blob Storage accounts.

Study Guide Reference: Design and implement an MLOps infrastructure — Azure Machine Learning data assets, MLTable, multi-location datasets, storage URI schemes, and Blob Storage integration.

This solution attempts to pass the dataset filename as a positional argument, bypassing the entire Azure Machine Learning input-binding mechanism. In Azure ML command jobs, data assets are not simple local file paths — they are managed references to data stored in Azure Storage that Azure ML resolves and mounts or downloads to the compute target at runtime. The script cannot directly reference dataset1.csv as a bare filename because there is no guarantee that file will be in the working directory of the compute target. Moreover, the script ' s argparse configuration uses --training_data as a named parameter, not a positional argument, so the command syntax does not match the expected interface. The correct approach uses the input binding placeholder syntax, which instructs Azure ML to resolve the registered data asset and provide its local path to the script at runtime.

Microsoft Learn Reference Topic: Work with data in Azure Machine Learning command jobs – Input binding syntax

UTF-8 is the universal encoding standard: it is backward-compatible with ASCII for standard Latin characters, supports every Unicode code point covering over 140,000 characters, and is the de facto standard for all modern APIs including Azure OpenAI. This matters for fine-tuning because training data often contains diverse characters from multiple languages, special punctuation, and domain-specific symbols. If they use ASCII encoding, any accented character or non-Latin script will be corrupted or lost entirely. UTF-16 adds a Byte Order Mark and can cause parsing issues with tools that expect standard JSONL. ISO-8859-1 covers Western European characters only and fails immediately with CJK or Arabic scripts. The Azure OpenAI fine-tuning documentation explicitly states that training files must be UTF-8 encoded, making it the only safe choice.

Microsoft Learn Reference Topic: Azure OpenAI fine-tuning – File format and encoding requirements

Because you want to reference all blobs in a container rather than a single file, the correct asset type is AssetTypes.URI_FOLDER. This type points to a directory-level URI, allowing Azure ML to traverse all files within it. For a publicly accessible Azure Blob Storage container, the URI follows the pattern https://storage_account.blob.core.windows.net/container_name/. You then create the Data object with the correct type, path, name, and version parameters, and register it in the workspace using ml_client.data.create_or_update. Do not use AssetTypes.URI_FILE, which references a single file. Do not use AssetTypes.MLTABLE unless you have an MLTable YAML descriptor. URI_FOLDER is the correct choice for referencing a collection of CSV blobs in an Azure Blob Storage container, allowing Azure ML to discover and process all files within the specified path.

Microsoft Learn Reference Topic: Create and manage data assets in Azure Machine Learning Python SDK v2 – URI_FOLDER