AI-300 Exam Dumps - Microsoft Certified: Machine Learning Operations (MLOps) Engineer Questions and Answers

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.

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

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

Data Zone Standard deployment routes requests to multiple datacenters within a defined geographic zone such as the US data zone, providing lower latency by using zone-level load balancing while maintaining data within a broad compliance boundary. This makes it suitable for enterprise internal applications where multiple business units need low-latency access without strict single-region data residency requirements. Developer deployment (option A) is a low-quota, unguaranteed tier designed for prototype testing, not production workloads serving multiple business units. Data Zone Batch (option B) is designed for high-volume asynchronous batch processing, not interactive low-latency real-time requests. Global Batch (option D) is optimized for scheduled bulk inference across all global regions but adds latency and is inappropriate for synchronous interactive use cases.

Microsoft Learn Reference Topic: Foundation model deployment types in Microsoft Foundry – Data Zone Standard for low-latency internal use

GPT-4o is OpenAI ' s multimodal model that accepts both text and image inputs natively. The ' o ' in GPT-4o stands for ' omni, ' reflecting its ability to process multiple modalities in a single inference call. It is available in Microsoft Foundry for both inference and fine-tuning, and it supports vision inputs alongside text prompts, making it the correct choice for any fine-tuning scenario requiring multimodal input. Davinci-002 (option A) is a legacy text-completion model with no vision capabilities and limited fine-tuning support for modern chat formats. GPT-3.5-Turbo (option C) is a text-only chat model that does not accept image inputs. GPT-4 (option D) has a standard version that is text-only; the vision variant GPT-4V is distinct from GPT-4o and has more limited fine-tuning availability in Foundry. For multimodal text plus image fine-tuning, GPT-4o is the only correct choice.

Microsoft Learn Reference Topic: Azure OpenAI Service models available for fine-tuning – GPT-4o multimodal capabilities

The team cannot rely on live user traffic for evaluation because it would make results non-reproducible and could expose users to untested prompts. Synthetic data generation within Microsoft Foundry allows the team to produce diverse, representative input examples that simulate real user queries without any live traffic risk, giving a stable, consistent test set evaluated under identical conditions. Option B (content filters) and Option C (blocklists) are safety controls applied at inference time, not evaluation inputs. Option D (observability metrics) is a monitoring capability for production systems. With synthetic data, the team can construct edge cases, varied phrasings, and domain-specific scenarios that would take months to accumulate organically from real users, directly enabling the controlled evaluation the question requires without any dependency on live traffic.

Microsoft Learn Reference Topic: Evaluate generative AI apps with synthetic data – Microsoft Foundry prompt evaluation

Correct sequence:

Collect retrieval logs.

Run RAG evaluators.

Adjust chunking strategy.

Re-index documents.

The process should begin by collecting retrieval logs . Retrieval diagnostics provide the evidence needed to understand which queries were issued, which document chunks were returned, and whether relevant content is being surfaced. Without retrieval telemetry, optimization becomes speculative rather than measurable.

Next, run RAG evaluators . Microsoft Foundry provides retrieval-oriented evaluators that assess how relevant retrieved context is to a query. The Retrieval evaluator measures contextual relevance without requiring ground truth, while the Document Retrieval evaluator can calculate metrics such as Fidelity and NDCG when labeled retrieval ground truth exists. These measurements help establish the retrieval-quality baseline before modifications are made.

After identifying retrieval deficiencies, adjust the chunking strategy . Microsoft specifically recommends reviewing chunk size and chunking methodology when retrieval returns irrelevant or incomplete passages. Chunks that are too small can lose context, while oversized chunks can introduce irrelevant material and reduce retrieval precision.

Finally, re-index the documents so the revised chunking configuration is reflected in the searchable corpus. Changing temperature or regenerating the prompt template primarily affects generation behavior rather than correcting the underlying retrieval pipeline.

Study Guide Reference: Implement generative AI quality assurance and observability — RAG evaluation, retrieval telemetry, retrieval-quality metrics, chunk optimization, indexing, and grounded-response assessment.