Microsoft AI-300 Practice Test Questions Answers

Microsoft ' s Azure AI Foundry documentation defines built-in roles scoped to the resource hierarchy. The Azure AI Administrator role grants permissions to manage the Azure AI Hub resource itself — including network settings, shared connections, quota, and governance configuration — which is appropriate for platform engineers who configure resource-level settings. The Azure AI Developer role grants permissions to create, update, and manage project-level assets such as deployments, prompt flows, fine-tuning jobs, and evaluations, without access to resource-level configuration. This precisely matches the developer requirement and enforces least privilege. Disabling Entra ID authentication (option B) violates security policy and removes the identity-based access control that makes RBAC possible. Sharing a single API key (option D) violates the least-privilege principle — all users would have identical, undifferentiated access with no audit trail.

Microsoft Learn Reference Topic: Manage access to Azure AI Foundry – Built-in roles: Azure AI Administrator and Azure AI Developer

The key concept here is low-priority (spot) VMs, which are available at a significant discount because Azure can reclaim them at any time. Azure Machine Learning compute clusters are the only target in the list that directly supports low-priority VM nodes as a cost-saving configuration. You set the minimum and maximum node counts and specify that new nodes should be provisioned as low-priority. Azure Container Instances (ACI) does not support low-priority pricing. Local deployment runs on the developer ' s machine with no Azure billing model. Azure Kubernetes Service (AKS) does support spot node pools but requires significantly more infrastructure management and is not the primary mechanism for low-priority compute in Azure Machine Learning. The exam tests whether you know that AML compute clusters are the managed way to leverage low-priority discounts inside Azure Machine Learning.

Microsoft Learn Reference Topic: Create and manage Azure Machine Learning compute clusters – Low-priority VMs

According to Microsoft ' s Azure Machine Learning documentation on managed online endpoints, a single endpoint can host multiple named deployments simultaneously, and you can control what percentage of incoming traffic each deployment receives. This traffic-splitting capability is the foundation of blue/green and canary deployment strategies. When you route 10% of traffic to a new deployment and 90% to the existing one, you can monitor error rates, latency, and output quality of the new version under real production load without risking the majority of users. Microsoft explicitly recommends this pattern for safe rollouts. Option A (batch endpoint) is inappropriate for real-time serving. Option C (replacing the endpoint) is high-risk with no validation window. Option D (routing all traffic to the new deployment) provides zero protection if the new version has issues.

Microsoft Learn Reference Topic: Safe rollout of machine learning models – Traffic splitting on managed online endpoints

Speed of recovery is the central requirement. Rolling back traffic to the previous deployment is the fastest possible action: because the previous deployment still exists on the same endpoint, you simply update the traffic weights — setting the old deployment to 100% and the new deployment to 0% — using a single Azure ML CLI command or SDK call that completes in seconds without reprovisioning any compute. Deleting and redeploying (option B) requires tearing down the endpoint, waiting for deprovisioning, recreating it, re-deploying the model, and waiting for containers to start — potentially 10 to 30 minutes. Changing authentication type (option C) does not affect application errors caused by a bad model. Increasing compute size (option D) does not fix model logic errors. The entire reason Azure ML supports multiple concurrent deployments with traffic splitting is precisely to enable this instant rollback pattern.

Microsoft Learn Reference Topic: Roll back deployments on managed online endpoints – Azure Machine Learning safe deployment practices

Git commits on the main branch provide the immutable, ordered history that auditors need: every change is timestamped, attributed to a specific developer, and reversible via git revert — this is the audit trail and rollback mechanism required by the first requirement. Git branches allow developers to create and test multiple prompt variants in complete isolation from the production prompt on the main branch, addressing the second requirement. A developer on an experiment branch can run full evaluations without touching the production prompt. When a variant is approved, it is merged via pull request. You cannot use branches alone for audit history because branches can be deleted, and you cannot use main-branch commits alone for parallel variant comparison without disrupting the history. Git ' s branch-and-merge model provides both capabilities simultaneously.

Microsoft Learn Reference Topic: Version control for AI prompts – Git branch strategies for prompt management in Microsoft Foundry