Microsoft AI-300 Practice Exam Questions & Answers

Azure Private Endpoints are network interfaces that connect your Azure ML workspace to your Virtual Network using a private IP address from the VNet's address space. Once a private endpoint is created and DNS is configured, all traffic to the workspace --- including the Studio UI, REST API, and SDK calls --- travels entirely over Microsoft's private backbone rather than the public internet. The workspace's public endpoint can then be completely disabled. Azure Firewall (option A) filters traffic at the network layer but still requires the workspace to have a public IP. Network Security Groups (option C) control traffic within VNets but cannot block the public endpoint of a PaaS service. Service endpoints (option D) keep traffic on the Azure backbone but the workspace still has a public-facing address. Private endpoints are the only option that fully removes the public network presence.

Microsoft Learn Reference Topic: Configure a private endpoint for Azure Machine Learning workspace

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

To continue logging metrics and artifacts when moving from local execution to Azure Machine Learning compute instance execution, you need to: (1) Authenticate to the workspace - Use MLflowClient or configure workspace authentication in the notebook so it connects to workspace1. (2) Enable MLflow autologging - Configure MLflow autologging on the compute instance so that metrics and artifacts are automatically logged to your workspace. This ensures seamless continuation of the logging behavior across environments.

Before using a custom component in an Azure Machine Learning Studio designer pipeline, you must first register the custom component. This involves creating a component definition with the YAML schema that specifies the component's inputs, outputs, code, and environment. Once registered, the custom component becomes available for use in the designer and can be added to pipelines.

Azure Machine Learning's model registry supports three lifecycle states: Active (the default, fully usable state), Archived (not deployable but still accessible for review), and Deleted (permanently removed). Archiving is precisely designed for this scenario: it ensures that operations teams cannot accidentally select the old version for a new deployment, while compliance officers can still inspect it, compare its metrics to newer versions, and reactivate it quickly if a rollback is needed. Deleting (option B) would permanently remove the version, making compliance review and rollback impossible and violating both requirements. Unregistering (option D) is not a standard Azure ML operation; deletion is the removal action. Archiving the training dataset (option A) is unrelated to the model version's deployability. Archiving creates a soft-block on deployment while preserving the full artifact history.

Microsoft Learn Reference Topic: Manage model versions in the Azure Machine Learning registry -- Archive and lifecycle management

The correct solution is a GitHub Actions workflow that executes Microsoft Foundry evaluations as part of the CI process. Microsoft provides an AI agent evaluation GitHub Action specifically for incorporating Foundry agent evaluations into CI/CD workflows. The action can invoke the agent against an evaluation dataset, execute configured evaluators---including safety evaluators---and publish evaluation results before a change reaches production.

For pull-request gating, the workflow can be configured to run whenever relevant application files change. Evaluation commands can also enforce explicit thresholds and return a non-zero exit code when those thresholds are not satisfied. Microsoft documents evaluation gating through options such as --fail-on pass-rate=<threshold> or --fail-on any-failure; a non-zero result causes the CI job to fail, preventing unsafe changes from being promoted.

A blocklist or content filter provides runtime content protection but does not automate pull-request evaluation. A retrieval chunking strategy affects RAG retrieval quality, not CI safety gates.

Therefore, the required mechanism is GitHub Actions integrated with Foundry evaluation runs and safety thresholds.

Study Guide Reference: Implement generative AI quality assurance and observability --- automated evaluations, CI/CD quality gates, safety evaluators, GitHub Actions, and pre-production validation.