AI-300 Dumps with Practice Exam Questions Answers

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

Different query types require fundamentally different retrieval algorithms. For queries that include exact policy identifiers, keyword or BM25 search is the correct choice because BM25 scores documents based on term frequency and inverse document frequency — an exact match on a specific policy identifier such as POL-2024-HR-042 scores very highly regardless of semantic context. This is the right approach when semantic similarity is low but exact term matching is critical. For natural-language questions where keywords may not be an exact match, semantic or vector search is the correct choice because vector embeddings capture meaning rather than exact tokens, finding relevant documents even when the user ' s vocabulary differs from the document ' s terminology. Azure AI Search supports both modes through its hybrid search capability, and the correct configuration maps each query type to its optimal retrieval algorithm.

Microsoft Learn Reference Topic: Configure hybrid search in Azure AI Search – BM25 keyword search vs. semantic vector search

UTF-8 is the universal encoding standard: it is backward-compatible with ASCII for standard Latin characters, supports every Unicode code point covering over 140,000 characters, and is the de facto standard for all modern APIs including Azure OpenAI. This matters for fine-tuning because training data often contains diverse characters from multiple languages, special punctuation, and domain-specific symbols. If they use ASCII encoding, any accented character or non-Latin script will be corrupted or lost entirely. UTF-16 adds a Byte Order Mark and can cause parsing issues with tools that expect standard JSONL. ISO-8859-1 covers Western European characters only and fails immediately with CJK or Arabic scripts. The Azure OpenAI fine-tuning documentation explicitly states that training files must be UTF-8 encoded, making it the only safe choice.

Microsoft Learn Reference Topic: Azure OpenAI fine-tuning – File format and encoding requirements

Microsoft ' s observability guidance for Azure AI Foundry applications describes a three-stage activation sequence. First, enable Tracing in the Microsoft Foundry project settings before deployment — Tracing instruments the application ' s LLM calls with OpenTelemetry-compatible spans that capture timing data for each step in the flow. Second, deploy the application to a production endpoint so that real traffic flows through the instrumented code path — without actual production traffic, there is no latency data to observe. Third, configure Azure Monitor and Application Insights to receive, aggregate, and visualize the telemetry emitted by Tracing. Azure Monitor ' s metrics explorer and Application Insights ' performance views display p50, p95, and p99 latency distributions over time, enabling the team to identify latency regressions and set alert thresholds. This sequence — instrument, deploy, visualize — is the canonical Microsoft path to production AI performance observability.

Microsoft Learn Reference Topic: Monitor generative AI applications with Azure Monitor and Microsoft Foundry Tracing

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