Home / artificial-intelligence-machine-learning / Operationalizing Machine Learning and Generative AI Solutions (AI-300) / Cheat Sheet
Operationalizing Machine Learning and Generative AI Solutions (AI-300)

AI-300 Cheat Sheet

AI-300 Tests Shipping and Running Models Safely — Not Building Them from Scratch

AI-300 is the MLOps and GenAIOps exam that followed DP-100. Think like the engineer who owns workspaces, endpoints, Foundry deployments and evaluation gates, not the data scientist tuning one notebook.

Check Your Readiness →
Among the harder certs
Avg: Not published by Microsoft
Pass: 750 / 1000
Most candidates understand Operationalizing Machine Learning and Generative AI Solutions (AI-300) concepts — and still fail. This exam tests how you apply knowledge under pressure.

AI-300 Domain Map (study guide updated October 15, 2026)

Scenarios set a constraint such as no stored secrets, EU-only processing, zero-downtime release or rising token spend, then ask for the feature or sequence that meets it with least risk and effort. 700/1000 to pass in 120 minutes; Microsoft does not publish the question count.

  1. 01
    MLOps infrastructure (15–20%) — workspace resources, compute choice, identity-based datastores, registries, Bicep/CLI with GitHub OIDC, managed VNet
  2. 02
    ML model lifecycle (25–30%) — MLflow tracking, sweep jobs, MLflow models, online vs. batch endpoints, safe rollout, monitoring signals and retraining
  3. 03
    GenAIOps infrastructure (20–25%) — Foundry resources and projects, keyless access, global/data zone/regional scope, PTUs vs. standard, prompt versioning
  4. 04
    GenAI quality and observability (10–15%) — groundedness, relevance and safety evaluators, column mapping, tracing, token metrics, continuous evaluation
  5. 05
    Optimizing GenAI systems (10–15%) — chunking, thresholds, hybrid search and semantic ranker, embeddings, SFT vs. DPO, distillation

Wrong instinct vs correct approach

A green deployment must see real requests for a week while no customer receives its responses
✕ Wrong instinct

Split 10% of live traffic to green

✓ Correct approach

Mirror a percentage of traffic to green: mirrored responses are discarded, so callers only ever get blue's answers. When ready, shift the traffic split gradually and keep blue until the rollout is proven, since it is the fast rollback path.

Millions of rows must be scored overnight with no latency requirement and minimal cost
✕ Wrong instinct

Deploy to a managed online endpoint and loop over rows

✓ Correct approach

Use a batch endpoint, which scores asynchronously on compute clusters that scale to zero between jobs. Tune mini_batch_size and instance count for throughput. Online endpoints keep instances running and suit low-latency, per-request scoring.

GitHub Actions deploys workspaces; no client secrets may exist in GitHub and only main may deploy
✕ Wrong instinct

Store a service principal ID and secret as repository secrets

✓ Correct approach

Add an OIDC federated credential to a Microsoft Entra identity with the subject scoped to the main branch or a protected environment. GitHub exchanges its token for an Entra token, so there is nothing to store or rotate.

A bank's internal assistant has steady high daytime volume, EU-only processing and needs predictable monthly cost
✕ Wrong instinct

Use a global standard pay-per-token deployment

✓ Correct approach

Choose a data zone provisioned throughput deployment in the EU. PTUs give reserved capacity, predictable latency and spend for steady load; overflow returns 429 unless spillover is set. Bursty, low traffic would fit standard deployments better.

Searches for part numbers miss the right document even though vector search works for descriptive questions
✕ Wrong instinct

Switch to a larger embedding model

✓ Correct approach

Exact identifiers match best on keyword BM25 retrieval, so enable hybrid search merged by reciprocal rank fusion, optionally with the semantic ranker. The ranker only reorders results already retrieved, and a new embedding model forces re-embedding the corpus.

Know these cold

  • ▸ Compute instance = one user's dev VM; cluster or serverless compute for scheduled training
  • ▸ Set compute cluster minimum nodes to 0 so idle clusters cost nothing
  • ▸ Registries share versioned models, environments and components across workspaces and regions
  • ▸ MLflow-format models deploy without a scoring script or custom environment
  • ▸ Archiving a model version hides it but endpoints keep serving it
  • ▸ Performance monitoring needs ground-truth labels; drift signals compare production to a reference dataset
  • ▸ Managed compute deployments bill for VM time while they exist, even when idle
  • ▸ Pin model versions when outputs must stay stable; test upgrades through evaluation before release
  • ▸ Prompts belong in Git with evaluation gates; change one element per prompt variant
  • ▸ Traces pinpoint the slow step in one request; metrics show trends and drive alerts

Can you answer these without checking your notes?

In this scenario: "A green deployment must see real requests for a week while no customer receives its responses" — what should you do first?
Mirror a percentage of traffic to green: mirrored responses are discarded, so callers only ever get blue's answers. When ready, shift the traffic split gradually and keep blue until the rollout is proven, since it is the fast rollback path.
In this scenario: "Millions of rows must be scored overnight with no latency requirement and minimal cost" — what should you do first?
Use a batch endpoint, which scores asynchronously on compute clusters that scale to zero between jobs. Tune mini_batch_size and instance count for throughput. Online endpoints keep instances running and suit low-latency, per-request scoring.
In this scenario: "GitHub Actions deploys workspaces; no client secrets may exist in GitHub and only main may deploy" — what should you do first?
Add an OIDC federated credential to a Microsoft Entra identity with the subject scoped to the main branch or a protected environment. GitHub exchanges its token for an Entra token, so there is nothing to store or rotate.

Common Exam Mistakes — What candidates get wrong

Pairing Bayesian sampling with an early termination policy in a sweep job

Azure Machine Learning sweeps support grid, random and Bayesian sampling, but early termination (Bandit, median stopping, truncation) cannot be combined with Bayesian. To cut tuning cost with early stopping, switch to random sampling.

Giving a workspace role but no storage data role for identity-based access

Identity-based datastores check the data plane, so the user or compute identity also needs Storage Blob Data Reader or Contributor on the storage account. AzureML Data Scientist on the workspace alone still fails to read the data.

Choosing a global deployment when inference must stay in the EU

Global deployments may process requests in any Azure region. A data zone deployment keeps processing inside a geography such as the EU or US, and a regional deployment pins it to one region. Residency wording rules global out.

Using relevance or fluency to catch hallucinated answers

Groundedness scores whether claims are supported by the retrieved context and needs the context column mapped. Relevance only checks the answer addresses the query; coherence and fluency judge structure and language. AI-assisted evaluators also consume judge-model tokens.

Fine-tuning a model to keep up with frequently changing facts

Facts that change every few weeks belong in a retrieval index, which also supports citations. Supervised fine-tuning shapes format, tone and behaviour; DPO needs preferred-versus-rejected pairs. Fine-tuned deployments are billed hourly while deployed, used or not.

Resources to help you pass Azure MLOps & GenAIOps AI-300 on your first attempt

AI-300 rewards production-grade MLOps and GenAIOps choices. See which deployment calls you would get wrong.