Last Attempt AI-300 Questions

GitHub Actions is the appropriate automation tool because the deployment process originates from pull requests and requires CI/CD automation, traceability, and an approval gate. Azure Machine Learning integrates directly with GitHub Actions for automated machine learning workflows, including infrastructure and asset deployment. Workflows can be triggered by repository events such as pull requests, merges, or pushes, providing an auditable record of who initiated the change, which commit was deployed, and whether the workflow succeeded.

Critically, GitHub environments can enforce required reviewers before a deployment job executes. Microsoft documents that when an environment requires approval, a job cannot access the environment ' s protected secrets until one of the required reviewers approves the deployment. This directly satisfies the requirement that deployment must require approval before running.

Azure Machine Learning pipelines orchestrate ML workflow steps such as preprocessing, training, evaluation, and registration, but they are not primarily the repository-level pull-request approval mechanism. MLflow provides experiment tracking and model lifecycle functionality, not CI orchestration. Azure Monitor provides telemetry and alerting rather than source-driven deployment automation.

Therefore, GitHub Actions provides the required combination of pull-request integration, automation, auditability, and protected deployment approval.

Study Guide Reference: Design and implement an MLOps infrastructure — CI/CD, GitHub Actions, pull-request automation, deployment approvals, protected environments, and Azure Machine Learning integration.

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

When evaluating a fine-tuned model against the base model using the same evaluation dataset, the interpretation of each metric requires careful analysis. A statement that the fine-tuned model improves on the target task is True if and only if the target metric such as task-specific accuracy, F1 score, or ROUGE score shows a statistically meaningful improvement. A statement about regression on a complementary metric is True if the fine-tuned model ' s score on that metric is meaningfully lower than the base model ' s. In Microsoft Foundry ' s evaluation framework, both pre-fine-tuning and post-fine-tuning results are stored against the same experiment, enabling direct side-by-side comparison. The core principle is that improvement on the primary task is not sufficient if fine-tuning causes degradation on safety or coherence — this is called catastrophic forgetting, and the evaluation dataset is designed to detect it.

Microsoft Learn Reference Topic: Evaluate fine-tuned models in Microsoft Foundry – Compare base and fine-tuned model metrics

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