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 28

Question 270

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A candidate model seems to outperform production by comparing AUC from a balanced sample with accuracy from an unbalanced live population. The resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity.
  2. Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
  3. Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.
  4. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

Explanation

Correct Answer

C:

Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds. This targets run comparison uses incompatible validation populations. A metric comparison is meaningful only when evaluation data and definitions align; different cohorts and metrics can invert model rankings. Verify the failure through: Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. Validate success with: The promotion report presents comparable metrics with documented confidence and class distribution before model approval.

Incorrect Answers

A:

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 run comparison uses incompatible validation populations failure. The matching remediation is: Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.

B:

Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This could address mlflow tracking uri sends notebook runs to wrong workspace, but it does not solve the specified run comparison uses incompatible validation populations failure. The matching remediation is: Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.

D:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This could address endpoint deployment health probe fails before model initialization, but it does not solve the specified run comparison uses incompatible validation populations failure. The matching remediation is: Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.

Question 271

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A research group leaves dedicated Azure ML compute instances running overnight although the instances are idle and only used during scheduled notebook sessions. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.
  2. Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
  3. Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.
  4. Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.
  5. Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management.

Explanation

Correct Answers

A:

Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. This is the most relevant evidence for interactive compute instances remain running while unused. Compute instances and managed compute clusters have different operating models; idle instance cost is not eliminated by an unrelated model deployment setting. The matching controlled remediation is: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.

B:

Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances. This targets interactive compute instances remain running while unused. Compute instances and managed compute clusters have different operating models; idle instance cost is not eliminated by an unrelated model deployment setting. Verify the failure through: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. Validate success with: Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.

Incorrect Answers

C:

Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This is associated with aml private workspace storage access fails from compute, not the essential evidence-and-fix pair for interactive compute instances remain running while unused. First examine: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. Then correct: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.

D:

Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file. This is associated with workspace dependencies point to unrelated secrets vault, not the essential evidence-and-fix pair for interactive compute instances remain running while unused. First examine: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. Then correct: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.

E:

Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management. This is associated with datastore authentication relies on expiring account key, not the essential evidence-and-fix pair for interactive compute instances remain running while unused. First examine: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. Then correct: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.

Question 272

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML online endpoint reports HTTP 400/500 errors because the deployed scoring code expects a named features field but the calling service sends a raw nested array. The operator must safeguard training reproducibility and serving continuity. Which investigation best verifies the cause before changing production configuration?

  1. Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern.
  2. Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation.
  3. Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest.
  4. Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes.

Explanation

Correct Answer

B:

Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation. This is the most relevant evidence for endpoint scoring script expects wrong json schema. Endpoint infrastructure can be healthy while the caller and scoring script disagree on their data contract. The matching controlled remediation is: Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML….

Incorrect Answers

A:

Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. This would investigate online scoring requirement deployed as batch endpoint rather than the documented endpoint scoring script expects wrong json schema issue. The relevant investigation is: Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML….

C:

Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. This would investigate rollback cannot recover a previous environment version rather than the documented endpoint scoring script expects wrong json schema issue. The relevant investigation is: Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation.

D:

Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. This would investigate data drift monitor uses wrong reference season rather than the documented endpoint scoring script expects wrong json schema issue. The relevant investigation is: Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation.

Question 273

While preparing a secure Foundry model or agent release, the following condition occurs: A prototype assistant runs only a few tests per day but reserves a large provisioned-throughput deployment, creating a high recurring bill even when no requests arrive. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which investigation best verifies the cause before changing production configuration?

  1. Inspect input/output token volume, peak concurrent requests, provisioned throughput allocation, throttling codes and deployment latency percentiles.
  2. Compare model deployment version pinning, response schemas, regression dataset, rollout timeline and application parser errors.
  3. Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.
  4. Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.

Explanation

Correct Answer

C:

Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load. This is the most relevant evidence for provisioned deployment pays for idle unused capacity. Provisioned throughput may be billed for allocated capacity independent of actual use; deployment type should match utilization patterns. The matching controlled remediation is: Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.

Incorrect Answers

A:

Inspect input/output token volume, peak concurrent requests, provisioned throughput allocation, throttling codes and deployment latency percentiles. This would investigate provisioned throughput capacity insufficient at peak traffic rather than the documented provisioned deployment pays for idle unused capacity issue. The relevant investigation is: Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.

B:

Compare model deployment version pinning, response schemas, regression dataset, rollout timeline and application parser errors. This would investigate foundry deployment alias changes model behavior unexpectedly rather than the documented provisioned deployment pays for idle unused capacity issue. The relevant investigation is: Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.

D:

Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces. This would investigate agent tool calls fail behind overbroad outbound block rather than the documented provisioned deployment pays for idle unused capacity issue. The relevant investigation is: Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.

Question 274

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A GenAI application shares one Foundry project and keys between development and production, so test deployments can overwrite production agent configuration. The deployment must retain governed identities, endpoint contracts and auditable release history. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.
  2. Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.
  3. Route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass.
  4. Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.

Explanation

Correct Answer

B:

Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates. This targets foundry environment mixes development and production agent resources. AI application environments need isolation across model deployment configuration, identity and release workflow, not just different branch names. Verify the failure through: Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs. Validate success with: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

Incorrect Answers

A:

Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access. This could address foundry service principal credential rotated without updating pipeline, but it does not solve the specified foundry environment mixes development and production agent resources failure. The matching remediation is: Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

C:

Route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass. This could address new foundation model replaces production without canary, but it does not solve the specified foundry environment mixes development and production agent resources failure. The matching remediation is: Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

D:

Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection. This could address foundry project links to wrong deployed model resource, but it does not solve the specified foundry environment mixes development and production agent resources failure. The matching remediation is: Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

Question 275

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A model retraining pipeline silently picks up new records every week because its input references an Azure ML data asset's latest version rather than the approved immutable snapshot. The team must preserve approved access, model provenance and private network constraints. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
  2. Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.
  3. Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates.
  4. Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error.
  5. Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.

Explanation

Correct Answers

A:

Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. This is the most relevant evidence for versionless dataset reference breaks reproducibility. A data asset reference without explicit versioning can change the effective training corpus between runs and invalidate reproducible model comparisons. The matching controlled remediation is: Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates. This matters here because a model retraining pipeline silently picks up new records every week because its input references an Azure ML data….

C:

Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates. This targets versionless dataset reference breaks reproducibility. A data asset reference without explicit versioning can change the effective training corpus between runs and invalidate reproducible model comparisons. Verify the failure through: Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. Validate success with: Replaying a prior run uses identical input version and produces traceable comparison metrics before a new snapshot is promoted. This matters here because a model retraining pipeline silently picks up new records every week because its input references an Azure ML data….

Incorrect Answers

B:

Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This is associated with mltable data asset schema mismatches training code, not the essential evidence-and-fix pair for versionless dataset reference breaks reproducibility. First examine: Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. Then correct: Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates. This matters here because a model retraining pipeline silently picks up new records every week because its input references an Azure ML data….

D:

Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error. This is associated with pipeline component output type mismatches consumer, not the essential evidence-and-fix pair for versionless dataset reference breaks reproducibility. First examine: Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. Then correct: Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates.

E:

Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant. This is associated with workspace contributor role granted to untrusted automation, not the essential evidence-and-fix pair for versionless dataset reference breaks reproducibility. First examine: Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. Then correct: Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates.

Question 276

During a regulated Azure ML workspace infrastructure review, 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 team must preserve approved access, model provenance and private network constraints. Which observable postchange result proves the intended remediation succeeded?

  1. The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution.
  2. A validation job loads the intended features with the declared schema and rejects incompatible input files.
  3. Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.
  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.

Incorrect Answers

A:

The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution. 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:

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.

C:

Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments. 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.

Question 277

While preparing a secure Foundry model or agent release, the following condition occurs: A nightly GenAIOps evaluation workflow stops connecting to its Foundry project after the release team revokes an old client secret used by the CI job. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.
  2. Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes.
  3. Compare model deployment version pinning, response schemas, regression dataset, rollout timeline and application parser errors.
  4. Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.

Explanation

Correct Answer

A:

Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. This is the most relevant evidence for foundry service principal credential rotated without updating pipeline. CI authentication is a separate dependency of a GenAIOps deployment; token renewal and secret rotation require an explicit supported credential flow. The matching controlled remediation is: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

Incorrect Answers

B:

Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes. This would investigate foundry project created in mismatched resource location rather than the documented foundry service principal credential rotated without updating pipeline issue. The relevant investigation is: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.

C:

Compare model deployment version pinning, response schemas, regression dataset, rollout timeline and application parser errors. This would investigate foundry deployment alias changes model behavior unexpectedly rather than the documented foundry service principal credential rotated without updating pipeline issue. The relevant investigation is: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.

D:

Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. This would investigate foundry administrator role granted to consumer application rather than the documented foundry service principal credential rotated without updating pipeline issue. The relevant investigation is: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.

Question 278

While preparing a secure Foundry model or agent release, the following condition occurs: A legal-document summarizer routinely receives 110,000-token inputs, but the selected model deployment has an insufficient supported context window and rejects or truncates requests. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which acceptance test shows the AI operations defect is corrected?

  1. A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.
  2. A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
  3. A test prompt or model deployment change affects only the development environment until an approved promotion occurs.
  4. Clean inference workers initialize the model and produce valid outputs for representative tokenization inputs.

Explanation

Correct Answer

B:

A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. Model suitability depends on context limits and task capability, not just a broad 'generative model' label. a direct corrective action is to choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.

Incorrect Answers

A:

A realistic image invoice yields extracted required details without unsupported request content or invented visual observations. That addresses a different configuration issue rather than the main requirement. Verify instead: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

C:

A test prompt or model deployment change affects only the development environment until an approved promotion occurs. That addresses a different configuration issue rather than the main requirement. Verify instead: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

D:

Clean inference workers initialize the model and produce valid outputs for representative tokenization inputs. That addresses a different configuration issue rather than the main requirement. Verify instead: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

Question 279

During a Foundry generative AI quality and observability incident, 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 fix must preserve evaluation validity and avoid unnecessary user-data collection. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.
  2. Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence.
  3. Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
  4. Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records.
  5. Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

Explanation

Correct Answers

B:

Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. This is the most relevant evidence for harmful content probe set excludes multilingual input. Safety evaluation quality depends on representative inputs; English-only coverage cannot establish protection for a multilingual product. The matching controlled remediation is: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content. This matters here because a public-facing GenAI service is cleared for launch after English safety checks, but hostile user requests in….

E:

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 a public-facing GenAI service is cleared for launch after English safety checks, but hostile user requests in….

Incorrect Answers

A:

Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run. This is associated with genai evaluation dataset lacks expected answer column mapping, not the essential evidence-and-fix pair for harmful content probe set excludes multilingual input. First examine: Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. Then correct: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

C:

Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change. This is associated with generation latency spike blamed on retrieval without breakdown, not the essential evidence-and-fix pair for harmful content probe set excludes multilingual input. First examine: Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. Then correct: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

D:

Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records. This is associated with evaluation workflow fails to block degraded agent deployment, not the essential evidence-and-fix pair for harmful content probe set excludes multilingual input. First examine: Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. Then correct: Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.

Question 280

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A Python scoring pipeline passes locally but fails on managed compute after a dependency release changes a library API because its Azure ML environment specifies unbounded package versions. The team must preserve approved access, model provenance and private network constraints. Which investigation best verifies the cause before changing production configuration?

  1. Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events.
  2. Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
  3. Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
  4. Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback.

Explanation

Correct Answer

D:

Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. This is the most relevant evidence for training environment lacks pinned package versions. Azure ML environment assets package execution dependencies; reproducibility requires explicit versions rather than assuming the newest package is compatible. The matching controlled remediation is: Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.

Incorrect Answers

A:

Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. This would investigate docker environment image cannot pull from private registry rather than the documented training environment lacks pinned package versions issue. The relevant investigation is: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback.

B:

Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. This would investigate job identity lacks blob reader data-plane rights rather than the documented training environment lacks pinned package versions issue. The relevant investigation is: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback.

C:

Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. This would investigate versionless dataset reference breaks reproducibility rather than the documented training environment lacks pinned package versions issue. The relevant investigation is: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback.

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