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 89

Question 880

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An interactive fraud-screening API must respond in under 200 milliseconds, but engineers deploy an Azure ML batch endpoint requiring asynchronous data job submission. The operator must safeguard training reproducibility and serving continuity. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.
  2. Inspect online endpoint traffic weights, deployment versions, request tracing, rollout approval and available prior stable deployment.
  3. Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern.
  4. Implement feasible deterministic seeding and record input data split and environment versions for each run with acknowledged nondeterministic GPU constraints.
  5. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.

Explanation

Correct Answers

A:

Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests. This targets online scoring requirement deployed as batch endpoint. Azure ML online endpoints support synchronous prediction while batch endpoints are designed for asynchronous high-volume jobs. Verify the failure through: Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. Validate success with: A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An interactive….

C:

Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. This is the most relevant evidence for online scoring requirement deployed as batch endpoint. Azure ML online endpoints support synchronous prediction while batch endpoints are designed for asynchronous high-volume jobs. The matching controlled remediation is: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An interactive….

Incorrect Answers

B:

Inspect online endpoint traffic weights, deployment versions, request tracing, rollout approval and available prior stable deployment. This is associated with canary rollout sends all traffic to unvalidated candidate, not the essential evidence-and-fix pair for online scoring requirement deployed as batch endpoint. First examine: Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. Then correct: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

D:

Implement feasible deterministic seeding and record input data split and environment versions for each run with acknowledged nondeterministic GPU constraints. This is associated with training script ignores reproducible seed and input contract, not the essential evidence-and-fix pair for online scoring requirement deployed as batch endpoint. First examine: Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. Then correct: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

E:

Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This is associated with rollback cannot recover a previous environment version, not the essential evidence-and-fix pair for online scoring requirement deployed as batch endpoint. First examine: Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. Then correct: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

Question 881

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A Foundry agent returns an unhelpful answer after a search tool timeout but logs only the final generated text, hiding the actual failing service and request correlation. The workflow must produce measurable quality, safety and performance evidence. Which acceptance test shows the AI operations defect is corrected?

  1. Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports.
  2. An intentionally degraded candidate fails before production promotion and a passing candidate proceeds with an auditable evaluation receipt.
  3. Average tokens per successful request falls while groundedness and task success remain within accepted limits.
  4. An induced tool timeout is attributable to the exact trace span and remediation can target the failing service.

Explanation

Correct Answer

D:

An induced tool timeout is attributable to the exact trace span and remediation can target the failing service. Multi-step AI agent troubleshooting needs per-tool traces, not just the final answer and an overall request status. a direct corrective action is to enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A Foundry….

Incorrect Answers

A:

Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports. That addresses a different configuration issue rather than the main requirement. Verify instead: An induced tool timeout is attributable to the exact trace span and remediation can target the failing service. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A Foundry….

B:

An intentionally degraded candidate fails before production promotion and a passing candidate proceeds with an auditable evaluation receipt. That addresses a different configuration issue rather than the main requirement. Verify instead: An induced tool timeout is attributable to the exact trace span and remediation can target the failing service.

C:

Average tokens per successful request falls while groundedness and task success remain within accepted limits. That addresses a different configuration issue rather than the main requirement. Verify instead: An induced tool timeout is attributable to the exact trace span and remediation can target the failing service.

Question 882

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A multi-node PyTorch training job starts on Azure ML GPUs but stalls during collective initialization because the managed network blocks approved inter-node rendezvous communication. The resolution must preserve quality gates, documented artifacts and rollback options. Which observable postchange result proves the intended remediation succeeded?

  1. Trials execute predictably without persistent quota-induced queueing, and tuning still explores the intended search space.
  2. Normal seasonal variation stops generating false incidents and genuine distribution changes still cross documented alert criteria.
  3. All workers join one process group and finish a representative multi-node training step without broad public inbound exposure.
  4. A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand.

Explanation

Correct Answer

C:

All workers join one process group and finish a representative multi-node training step without broad public inbound exposure. Distributed training requires connectivity and consistent rank/world-size setup among workers; GPU availability alone does not establish a working cluster. a direct corrective action is to allow the narrowly scoped supported compute-to-compute communication paths and correct the distributed training rendezvous configuration.

Incorrect Answers

A:

Trials execute predictably without persistent quota-induced queueing, and tuning still explores the intended search space. That addresses a different configuration issue rather than the main requirement. Verify instead: All workers join one process group and finish a representative multi-node training step without broad public inbound exposure.

B:

Normal seasonal variation stops generating false incidents and genuine distribution changes still cross documented alert criteria. That addresses a different configuration issue rather than the main requirement. Verify instead: All workers join one process group and finish a representative multi-node training step without broad public inbound exposure.

D:

A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand. That addresses a different configuration issue rather than the main requirement. Verify instead: All workers join one process group and finish a representative multi-node training step without broad public inbound exposure.

Question 883

During a Microsoft Foundry generative AI deployment review, the following condition occurs: An engineer commits a Foundry service API key directly in a Bicep parameter file, making the key readable in repository history despite later deletion. The deployment must retain governed identities, endpoint contracts and auditable release history. Which acceptance test shows the AI operations defect is corrected?

  1. Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked.
  2. The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.
  3. The project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback.
  4. The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls.

Explanation

Correct Answer

D:

The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls. Declarative infrastructure should manage references and identities rather than persist credentials as version-controlled cleartext values. a direct corrective action is to revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds. This matters here because an engineer commits a Foundry service API key directly in a Bicep parameter file, making the key readable in….

Incorrect Answers

A:

Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked. That addresses a different configuration issue rather than the main requirement. Verify instead: The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls. This matters here because an engineer commits a Foundry service API key directly in a Bicep parameter file, making the key readable in….

B:

The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected. That addresses a different configuration issue rather than the main requirement. Verify instead: The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls.

C:

The project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback. That addresses a different configuration issue rather than the main requirement. Verify instead: The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls.

Question 884

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A global customer-support agent project is provisioned in a region that does not offer the selected foundation model deployment type, preventing its evaluation pipeline from starting. The deployment must retain governed identities, endpoint contracts and auditable release history. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
  2. Deploy the governed Foundry resource and project in a supported compliant region with an available model option.
  3. Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
  4. Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.

Explanation

Correct Answer

B:

Deploy the governed Foundry resource and project in a supported compliant region with an available model option. This targets foundry project created in mismatched resource location. A Foundry project depends on its parent resource location and model/service availability; creating a project does not guarantee every model is deployable there. Verify the failure through: Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes. Validate success with: The project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback. This matters here because a global customer-support agent project is provisioned in a region that does not offer the selected foundation model….

Incorrect Answers

A:

Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates. This could address multilingual model selection fails target-language quality, but it does not solve the specified foundry project created in mismatched resource location failure. The matching remediation is: Deploy the governed Foundry resource and project in a supported compliant region with an available model option.

C:

Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This could address foundry bicep rollout omits model deployment dependencies, but it does not solve the specified foundry project created in mismatched resource location failure. The matching remediation is: Deploy the governed Foundry resource and project in a supported compliant region with an available model option.

D:

Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds. This could address foundry infrastructure parameters embed a secret in source repository, but it does not solve the specified foundry project created in mismatched resource location failure. The matching remediation is: Deploy the governed Foundry resource and project in a supported compliant region with an available model option.

Question 885

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A deployed churn model receives increasing nulls in a new CRM field but its data drift monitor tracks only average values and ignores missingness and schema validity. The operator must safeguard training reproducibility and serving continuity. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.
  2. Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
  3. Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.
  4. Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling.
  5. Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

Explanation

Correct Answers

A:

Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This targets missing feature values escape input drift checks. Data quality and data distribution drift are related but distinct signals; averages alone can conceal feature loss. Verify the failure through: Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. Validate success with: An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A deployed….

D:

Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. This is the most relevant evidence for missing feature values escape input drift checks. Data quality and data distribution drift are related but distinct signals; averages alone can conceal feature loss. The matching controlled remediation is: Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A deployed….

Incorrect Answers

B:

Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts. This is associated with endpoint latency average conceals tail degradation, not the essential evidence-and-fix pair for missing feature values escape input drift checks. First examine: Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. Then correct: Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.

C:

Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates. This is associated with canary rollout sends all traffic to unvalidated candidate, not the essential evidence-and-fix pair for missing feature values escape input drift checks. First examine: Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. Then correct: Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.

E:

Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join. This is associated with accuracy monitoring lacks delayed outcome labels, not the essential evidence-and-fix pair for missing feature values escape input drift checks. First examine: Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. Then correct: Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A deployed….

Question 886

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled Azure ML pipeline appears fast but returns last week's encoded features because a preprocessing component is reused under inputs that do not capture the changed transformation configuration. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Configure tail-latency and error-rate dashboards with capacity remedies appropriate to the measured bottleneck.
  2. Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage.
  3. Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.
  4. Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.
  5. Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

Explanation

Correct Answers

B:

Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. This is the most relevant evidence for pipeline cache reuses stale transform artifact. Pipeline reuse is correct only when the declared inputs and environment represent all behaviorally relevant computation dependencies. The matching controlled remediation is: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled….

E:

Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed. This targets pipeline cache reuses stale transform artifact. Pipeline reuse is correct only when the declared inputs and environment represent all behaviorally relevant computation dependencies. Verify the failure through: Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. Validate success with: A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled….

Incorrect Answers

A:

Configure tail-latency and error-rate dashboards with capacity remedies appropriate to the measured bottleneck. This is associated with endpoint latency average conceals tail degradation, not the essential evidence-and-fix pair for pipeline cache reuses stale transform artifact. First examine: Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. Then correct: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

C:

Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. This is associated with pipeline graph omits feature-build dependency, not the essential evidence-and-fix pair for pipeline cache reuses stale transform artifact. First examine: Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. Then correct: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

D:

Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds. This is associated with run comparison uses incompatible validation populations, not the essential evidence-and-fix pair for pipeline cache reuses stale transform artifact. First examine: Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. Then correct: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

Question 887

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A tabular classification pipeline expects named columns but a newly registered MLTable asset points to CSV files with a different header and type inference rules. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which targeted Azure AI operations change best addresses the documented problem?

  1. Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.
  2. Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply.
  3. Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
  4. Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline.

Explanation

Correct Answer

A:

Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This targets mltable data asset schema mismatches training code. An Azure ML data asset describes dataset structure and access; registration success does not prove its schema matches a consuming model. Verify the failure through: Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors. Validate success with: A validation job loads the intended features with the declared schema and rejects incompatible input files. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A tabular….

Incorrect Answers

B:

Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply. This could address iac workflow lacks repeatable infrastructure validation, but it does not solve the specified mltable data asset schema mismatches training code failure. The matching remediation is: Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.

C:

Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment. This could address training environment lacks pinned package versions, but it does not solve the specified mltable data asset schema mismatches training code failure. The matching remediation is: Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.

D:

Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline. This could address reusable component hardcodes workspace-specific asset path, but it does not solve the specified mltable data asset schema mismatches training code failure. The matching remediation is: Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A tabular….

Question 888

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled Azure ML retraining job always updates the online endpoint even when new validation recall is worse than the currently approved model. The resolution must preserve quality gates, documented artifacts and rollback options. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.
  2. Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.
  3. Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records.
  4. Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling.

Explanation

Correct Answer

C:

Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. This is the most relevant evidence for retraining pipeline deploys without model quality gate. Automation of model retraining should not imply automatic unconditional promotion; evaluation gates are essential to safe model operations. The matching controlled remediation is: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled….

Incorrect Answers

A:

Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. This would investigate new candidate chosen from training instead of validation results rather than the documented retraining pipeline deploys without model quality gate issue. The relevant investigation is: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records.

B:

Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. This would investigate accuracy monitoring lacks delayed outcome labels rather than the documented retraining pipeline deploys without model quality gate issue. The relevant investigation is: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled….

D:

Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. This would investigate missing feature values escape input drift checks rather than the documented retraining pipeline deploys without model quality gate issue. The relevant investigation is: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records.

Question 889

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline component is published for reuse but includes a hard-coded workspace datastore URI, causing executions in a second workspace to read an unavailable path. The change must remain limited to authorized workspaces and avoid unreviewed production impact. What measured outcome validates the solution while preserving the stated constraints?

  1. A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files.
  2. Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry.
  3. A validation job loads the intended features with the declared schema and rejects incompatible input files.
  4. The same versioned component runs against authorized data in two workspaces without editing its source implementation.

Explanation

Correct Answer

D:

The same versioned component runs against authorized data in two workspaces without editing its source implementation. Portable Azure ML components describe computation and typed interfaces rather than assuming a single workspace's storage layout. a direct corrective action is to replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline….

Incorrect Answers

A:

A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files. That addresses a different configuration issue rather than the main requirement. Verify instead: The same versioned component runs against authorized data in two workspaces without editing its source implementation.

B:

Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry. That addresses a different configuration issue rather than the main requirement. Verify instead: The same versioned component runs against authorized data in two workspaces without editing its source implementation.

C:

A validation job loads the intended features with the declared schema and rejects incompatible input files. That addresses a different configuration issue rather than the main requirement. Verify instead: The same versioned component runs against authorized data in two workspaces without editing its source implementation. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline….

Question 890

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team deletes the previously approved model after a new deployment, then cannot restore service when the new model fails canary checks. The resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.
  2. Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time.
  3. Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity.
  4. Register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test.

Explanation

Correct Answer

A:

Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed. This targets incident rollback artifact was deleted instead of archived. Archiving and retention support model provenance and rollback; immediate deletion of the only stable model makes a deployment irreversible. Verify the failure through: Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. Validate success with: A failed canary can restore the last approved model version without retraining or inventing replacement artifacts. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team….

Incorrect Answers

B:

Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time. This could address feature retrieval specification missing from registered model, but it does not solve the specified incident rollback artifact was deleted instead of archived failure. The matching remediation is: Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team….

C:

Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity. This could address sweep concurrency overwhelms scarce gpu quota, but it does not solve the specified incident rollback artifact was deleted instead of archived failure. The matching remediation is: Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.

D:

Register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test. This could address mlflow registry artifact cannot load on serving target, but it does not solve the specified incident rollback artifact was deleted instead of archived failure. The matching remediation is: Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.

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