Pass the Microsoft Microsoft Certified: Machine Learning Operations (MLOps) Engineer AI-300 Questions and answers with CertsForce

No. Deleting an existing Azure Machine Learning kernel is neither required nor appropriate before adding another Jupyter kernel. Azure Machine Learning compute instances are explicitly designed to support multiple kernels simultaneously . Microsoft states that notebooks automatically discover the Jupyter kernels installed on the connected compute instance, allowing users to switch between them from the kernel selector.

To add a kernel, the supported process is to create a new Conda environment, activate it, install pip and ipykernel, and then register that environment by using python -m ipykernel install --user. Existing kernels do not need to be removed.

More importantly, Microsoft warns against deleting Conda environments or Jupyter kernels that you did not create , because doing so can damage Jupyter or JupyterLab functionality on the Azure Machine Learning compute instance. This makes removal of a built-in AzureML kernel particularly inappropriate as a prerequisite for creating another kernel.

The correct approach is therefore to leave the existing kernel intact and create a separate environment/kernel for the new workload.

Study Guide Reference: Design and implement an MLOps infrastructure — Azure Machine Learning notebook environments, kernel management, compute instances, and dependency isolation.

===============

To ensure runtime dependencies are consistent and reusable, first create a conda.yaml or requirements.txt file that lists all Python packages and system libraries required by your training code — this file is the single source of truth for your runtime. Next, create an Environment object using the Azure ML Python SDK v2 with a name and reference to the conda.yaml file, specifying the base Docker image. Then register the Environment by calling ml_client.environments.create_or_update, which publishes it to the workspace registry with an auto-incremented version. Finally, reference the registered environment by name and version in all pipeline job steps. Azure ML will build or retrieve the cached Docker image and use it as the execution container. This approach means updating dependencies only requires modifying the conda.yaml and registering a new version — training code remains unchanged.

Microsoft Learn Reference Topic: Create and manage Azure Machine Learning environments – Reusable curated environments

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

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

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 first action should be to evaluate the model output . Fabrikam already has evaluation data containing manually defined expected responses, and the technical requirements explicitly state that the organization must use its existing evaluation datasets based on real data with input-output pairs . Microsoft Foundry supports evaluating a model against an existing curated dataset to establish measurable baseline performance before optimization. Evaluation results can identify weaknesses in accuracy, relevance, groundedness, safety, or other quality dimensions and provide objective evidence for subsequent changes.

This sequencing is critical because Fabrikam also requires that advanced fine-tuning be applied only when prompt engineering is insufficient . Therefore, immediately fine-tuning the model would bypass the required baseline evaluation and optimization process. Fine-tuning should be driven by demonstrated performance gaps, not applied automatically.

Deploying directly to production is also inappropriate because leadership requires low operational risk and gradual rollout. Production traffic should not be used as the first evaluation mechanism when curated evaluation data already exists. Synthetic interaction data is useful when evaluation coverage is insufficient, but Microsoft specifically positions synthetic generation as an option when an adequate test dataset is unavailable. Fabrikam already has suitable evaluation data.

Study Guide Reference: Optimize generative AI systems and model performance — evaluate model performance, benchmark against curated datasets, iterate on prompts, and apply advanced fine-tuning when justified.