cert
cert-1
cert-2

Pass Microsoft AI-300 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
AI-300 Exam - Verified By Experts
AI-300 Premium File

AI-300 Premium File

$69.99
$76.99
  • Premium File 213 Questions & Answers. Last Update: Nov 12, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 45 downloads in the last 7 days
block-screenshots
Microsoft AI-300 Practice Test 34

Question 330

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A GenAI application releases its Foundry project and calls a model name before that model deployment is created, causing intermittent first-run errors. The deployment must retain governed identities, endpoint contracts and auditable release history. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization.
  2. Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.
  3. Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.
  4. Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.

Explanation

Correct Answer

D:

Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. This is the most relevant evidence for foundry bicep rollout omits model deployment dependencies. Infrastructure-as-code can provision the platform consistently only when dependencies and deployment readiness are managed explicitly. The matching controlled remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.

Incorrect Answers

A:

Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. This would investigate foundry project links to wrong deployed model resource rather than the documented foundry bicep rollout omits model deployment dependencies issue. The relevant investigation is: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.

B:

Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. This would investigate foundry private endpoint dns resolves to public ip rather than the documented foundry bicep rollout omits model deployment dependencies issue. The relevant investigation is: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.

C:

Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. This would investigate prompt variant comparison measures fluency not task success rather than the documented foundry bicep rollout omits model deployment dependencies issue. The relevant investigation is: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.

Question 331

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A tool-enabled finance agent passes harmful-text screening but executes instructions inside a hostile retrieved web page because its safety suite contains no prompt-injection or tool-misuse cases. The workflow must produce measurable quality, safety and performance evidence. What measured outcome validates the solution while preserving the stated constraints?

  1. Unsupported claims fail the release gate even when the answers are grammatically smooth.
  2. An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.
  3. An induced tool timeout is attributable to the exact trace span and remediation can target the failing service.
  4. Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.

Explanation

Correct Answer

B:

An adversarial document cannot cause unapproved transactions while authorized research questions still succeed. Harmful-content detection alone does not test whether an agent obeys malicious instructions inserted into lower-trust retrieved material. a direct corrective action is to add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.

Incorrect Answers

A:

Unsupported claims fail the release gate even when the answers are grammatically smooth. That addresses a different configuration issue rather than the main requirement. Verify instead: An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.

C:

An induced tool timeout is attributable to the exact trace span and remediation can target the failing service. That addresses a different configuration issue rather than the main requirement. Verify instead: An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.

D:

Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields. That addresses a different configuration issue rather than the main requirement. Verify instead: An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.

Question 332

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A public-facing GenAI service is cleared for launch after English safety checks, but hostile user requests in supported non-English languages bypass the tested safety evaluator. The workflow must produce measurable quality, safety and performance evidence. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
  2. Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.
  3. Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
  4. Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.

Explanation

Correct Answer

A:

Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content. This targets harmful content probe set excludes multilingual input. Safety evaluation quality depends on representative inputs; English-only coverage cannot establish protection for a multilingual product. Verify the failure through: Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. Validate success with: Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A….

Incorrect Answers

B:

Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric. This could address relevance evaluator uses wrong intended user query, but it does not solve the specified harmful content probe set excludes multilingual input failure. The matching remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

C:

Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand. This could address genai throughput report mixes responses and tokens, but it does not solve the specified harmful content probe set excludes multilingual input failure. The matching remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

D:

Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run. This could address genai evaluation dataset lacks expected answer column mapping, but it does not solve the specified harmful content probe set excludes multilingual input failure. The matching remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

Question 333

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A retrieval assistant generates fluent answers citing unrelated documents, yet the release dashboard declares success based solely on readability. The workflow must produce measurable quality, safety and performance evidence. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.
  2. Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments.
  3. Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence.
  4. Inspect evaluation dataset field names, input-output column mapping, evaluator requirements, row samples and failed scoring logs.

Explanation

Correct Answer

B:

Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments. This is the most relevant evidence for groundedness metric conflated with response fluency. Readability and factual support are distinct dimensions of GenAI output quality; polished prose is not evidence that retrieved sources justify a claim. The matching controlled remediation is: Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.

Incorrect Answers

A:

Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. This would investigate debug traces leak secrets and retrieved personal records rather than the documented groundedness metric conflated with response fluency issue. The relevant investigation is: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments.

C:

Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. This would investigate harmful content probe set excludes multilingual input rather than the documented groundedness metric conflated with response fluency issue. The relevant investigation is: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments.

D:

Inspect evaluation dataset field names, input-output column mapping, evaluator requirements, row samples and failed scoring logs. This would investigate genai evaluation dataset lacks expected answer column mapping rather than the documented groundedness metric conflated with response fluency issue. The relevant investigation is: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments.

Question 334

While preparing a secure Foundry model or agent release, the following condition occurs: A web front end that only calls an approved LLM deployment is assigned Foundry resource management privileges, allowing it to modify deployments and project settings. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which investigation best verifies the cause before changing production configuration?

  1. Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.
  2. Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.
  3. Inspect the prompt template, target JSON schema, model output examples, parser exceptions and current evaluation dataset.
  4. Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.

Explanation

Correct Answer

B:

Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. This is the most relevant evidence for foundry administrator role granted to consumer application. Application inference rights should be separated from platform administration; granting project owner privileges expands the impact of a compromised app. The matching controlled remediation is: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A web front end that only….

Incorrect Answers

A:

Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This would investigate network allowlist exposes production model endpoint to test subnet rather than the documented foundry administrator role granted to consumer application issue. The relevant investigation is: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.

C:

Inspect the prompt template, target JSON schema, model output examples, parser exceptions and current evaluation dataset. This would investigate prompt omits explicit structured answer schema rather than the documented foundry administrator role granted to consumer application issue. The relevant investigation is: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.

D:

Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. This would investigate foundry private endpoint dns resolves to public ip rather than the documented foundry administrator role granted to consumer application issue. The relevant investigation is: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.

Question 335

While optimizing a production RAG or fine-tuned model service, the following condition occurs: A product support team plans expensive fine-tuning to memorize weekly price lists, even though the answers require current frequently edited catalog values. The resulting model must meet held-out quality and security criteria. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow.
  2. Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking.
  3. Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals.
  4. Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release.
  5. Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

Explanation

Correct Answers

A:

Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. This is the most relevant evidence for fine-tuning task selected when retrieval would better handle changing facts. Fine-tuning changes model behavior and knowledge imperfectly; retrieval is generally more suitable for fast-changing external facts. The matching controlled remediation is: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

E:

Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation. This targets fine-tuning task selected when retrieval would better handle changing facts. Fine-tuning changes model behavior and knowledge imperfectly; retrieval is generally more suitable for fast-changing external facts. Verify the failure through: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. Validate success with: A changed product price appears in answers after authorized index refresh without retraining the entire model.

Incorrect Answers

B:

Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking. This is associated with pure vector search misses exact regulatory clause codes, not the essential evidence-and-fix pair for fine-tuning task selected when retrieval would better handle changing facts. First examine: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. Then correct: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

C:

Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals. This is associated with synthetic training examples copy private customer identifiers, not the essential evidence-and-fix pair for fine-tuning task selected when retrieval would better handle changing facts. First examine: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. Then correct: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

D:

Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release. This is associated with fine-tuned model loses safety boundary after customization, not the essential evidence-and-fix pair for fine-tuning task selected when retrieval would better handle changing facts. First examine: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. Then correct: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

Question 336

While preparing a secure Foundry model or agent release, the following condition occurs: An enterprise disables public network access to Foundry but its container app still resolves the model service hostname to a public endpoint, resulting in failed inference calls. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.
  2. Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
  3. Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.
  4. Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

Explanation

Correct Answer

D:

Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity. This targets foundry private endpoint dns resolves to public ip. Private network security requires both endpoint approval and correct DNS resolution; a private endpoint creation event does not change every client's name resolution. Verify the failure through: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. Validate success with: Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An enterprise disables….

Incorrect Answers

A:

Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment. This could address azure cli foundry setup assumes existing model quota, but it does not solve the specified foundry private endpoint dns resolves to public ip failure. The matching remediation is: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

B:

Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This could address prompt variant comparison measures fluency not task success, but it does not solve the specified foundry private endpoint dns resolves to public ip failure. The matching remediation is: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

C:

Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This could address agent runtime managed identity cannot read retrieval data, but it does not solve the specified foundry private endpoint dns resolves to public ip failure. The matching remediation is: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

Question 337

While preparing a secure Foundry model or agent release, the following condition occurs: A team claims prompt B is better than prompt A, but B runs on a newer foundation model so the measured improvement cannot be attributed to the prompt change. The remediation must meet enterprise access and reliability requirements without a broad bypass. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.
  2. Define a versioned structured response instruction and supported JSON schema contract with parser-based validation.
  3. Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.
  4. Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

Explanation

Correct Answer

C:

Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics. This targets prompt a/b test uses different model versions in each arm. Experimental prompt comparisons require controlling confounders; a simultaneous model upgrade prevents a valid prompt-only attribution. Verify the failure through: Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes. Validate success with: The comparison isolates prompt differences and produces reproducible evidence of quality and latency trade-offs.

Incorrect Answers

A:

Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review. This could address prompt repository references secret customer examples, but it does not solve the specified prompt a/b test uses different model versions in each arm failure. The matching remediation is: Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.

B:

Define a versioned structured response instruction and supported JSON schema contract with parser-based validation. This could address prompt omits explicit structured answer schema, but it does not solve the specified prompt a/b test uses different model versions in each arm failure. The matching remediation is: Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.

D:

Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity. This could address foundry private endpoint dns resolves to public ip, but it does not solve the specified prompt a/b test uses different model versions in each arm failure. The matching remediation is: Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.

Question 338

During a retrieval or model-customization performance review, the following condition occurs: An enterprise assistant's new retrieval strategy raises link clicks but adds hallucinated recommendations, while the experiment reports only engagement as the success metric. The change must keep citations, privacy and previously approved behavior intact. Which observable postchange result proves the intended remediation succeeded?

  1. Domain terminology retrieval improves without unacceptable loss on routine guidance queries.
  2. Previously unseen product queries are monitored and subsequent vetted versions meet current quality targets without erasing old task competence.
  3. Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase.
  4. The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation.

Explanation

Correct Answer

D:

The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation. Interaction metrics do not establish answer accuracy; retrieval optimization needs labels and safety/quality measurements. a direct corrective action is to evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.

Incorrect Answers

A:

Domain terminology retrieval improves without unacceptable loss on routine guidance queries. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation.

B:

Previously unseen product queries are monitored and subsequent vetted versions meet current quality targets without erasing old task competence. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation.

C:

Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation.

Question 339

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A project deployment script succeeds in creating resources but fails when attempting model deployment because the selected subscription's capacity quota is insufficient. The deployment must retain governed identities, endpoint contracts and auditable release history. Which investigation best verifies the cause before changing production configuration?

  1. Examine model deployment quota for selected region/type, Azure CLI errors, requested capacity units and existing model allocations.
  2. Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
  3. Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.
  4. Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.

Explanation

Correct Answer

A:

Examine model deployment quota for selected region/type, Azure CLI errors, requested capacity units and existing model allocations. This is the most relevant evidence for azure cli foundry setup assumes existing model quota. Resource provisioning and model capacity allocation are separate operations; successful project creation does not reserve throughput for every selected model. The matching controlled remediation is: Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.

Incorrect Answers

B:

Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This would investigate prompt contract rollback ignores associated model version rather than the documented azure cli foundry setup assumes existing model quota issue. The relevant investigation is: Examine model deployment quota for selected region/type, Azure CLI errors, requested capacity units and existing model allocations.

C:

Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. This would investigate foundry service principal credential rotated without updating pipeline rather than the documented azure cli foundry setup assumes existing model quota issue. The relevant investigation is: Examine model deployment quota for selected region/type, Azure CLI errors, requested capacity units and existing model allocations.

D:

Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. This would investigate foundry bicep rollout omits model deployment dependencies rather than the documented azure cli foundry setup assumes existing model quota issue. The relevant investigation is: Examine model deployment quota for selected region/type, Azure CLI errors, requested capacity units and existing model allocations.

Question 340

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A withdrawn credit-risk model is marked deprecated in a wiki but remains exposed as an active registry version and continues to be selected by automated deployment tools. The resolution must preserve quality gates, documented artifacts and rollback options. Which investigation best verifies the cause before changing production configuration?

  1. Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
  2. Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
  3. Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook.
  4. Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.

Explanation

Correct Answer

B:

Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This is the most relevant evidence for retired model kept active as discoverable deployment candidate. Model lifecycle management must reflect state in the model registry and deployment references, not just informal documentation. The matching controlled remediation is: Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A withdrawn….

Incorrect Answers

A:

Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This would investigate run comparison uses incompatible validation populations rather than the documented retired model kept active as discoverable deployment candidate issue. The relevant investigation is: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A withdrawn….

C:

Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. This would investigate incident rollback artifact was deleted instead of archived rather than the documented retired model kept active as discoverable deployment candidate issue. The relevant investigation is: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A withdrawn….

D:

Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training. This would investigate feature retrieval specification missing from registered model rather than the documented retired model kept active as discoverable deployment candidate issue. The relevant investigation is: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.

Operationalizing Machine Learning and Generative AI Solutions (AI-300) Practice Tests