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 70

Question 690

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A production deployment references a mutable latest model alias and picks up a candidate model that bypassed validation when another team registered a new version. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
  2. Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.
  3. Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.
  4. Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.
  5. Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness.

Explanation

Correct Answers

A:

Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. This is the most relevant evidence for model registry latest alias points to unapproved experiment. Mutable model aliases simplify discovery but are unsafe production identifiers when deployment reproducibility and review are required. The matching controlled remediation is: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.

D:

Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates. This targets model registry latest alias points to unapproved experiment. Mutable model aliases simplify discovery but are unsafe production identifiers when deployment reproducibility and review are required. Verify the failure through: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. Validate success with: Recreating a production deployment resolves the same approved model artifact until an authorized promotion changes the version.

Incorrect Answers

B:

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 model registry latest alias points to unapproved experiment. First examine: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. Then correct: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.

C:

Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version. This is associated with online feature retrieval pulls values from after prediction time, not the essential evidence-and-fix pair for model registry latest alias points to unapproved experiment. First examine: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. Then correct: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.

E:

Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. This is associated with responsible ai evaluation omits demographic cohort slices, not the essential evidence-and-fix pair for model registry latest alias points to unapproved experiment. First examine: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. Then correct: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.

Question 691

During a regulated Azure ML workspace infrastructure review, the following condition occurs: An engineer runs an Azure CLI setup script that creates the model workspace in the CLI's current default subscription rather than the approved production subscription. The team must preserve approved access, model provenance and private network constraints. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
  2. Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.
  3. Grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace.
  4. Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
  5. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.

Explanation

Correct Answers

B:

Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands. This targets azure cli deployment silently targets sandbox defaults. Azure CLI context is stateful; an otherwise valid infrastructure command can target the wrong subscription when scope is not explicitly established. Verify the failure through: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Validate success with: Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources. This matters here because an engineer runs an Azure CLI setup script that creates the model workspace in the CLI's current default….

D:

Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. This is the most relevant evidence for azure cli deployment silently targets sandbox defaults. Azure CLI context is stateful; an otherwise valid infrastructure command can target the wrong subscription when scope is not explicitly established. The matching controlled remediation is: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands. This matters here because an engineer runs an Azure CLI setup script that creates the model workspace in the CLI's current default….

Incorrect Answers

A:

Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow. This is associated with github action uses persistent azure client secret, not the essential evidence-and-fix pair for azure cli deployment silently targets sandbox defaults. First examine: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Then correct: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

C:

Grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace. This is associated with registry model asset not available to second workspace, not the essential evidence-and-fix pair for azure cli deployment silently targets sandbox defaults. First examine: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Then correct: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

E:

Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This is associated with iac workflow lacks repeatable infrastructure validation, not the essential evidence-and-fix pair for azure cli deployment silently targets sandbox defaults. First examine: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Then correct: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

Question 692

As an MLOps engineer reviews a model training or inference pipeline, 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 resolution must preserve quality gates, documented artifacts and rollback options. What measured outcome validates the solution while preserving the stated constraints?

  1. Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption.
  2. Deployment reaches healthy readiness and handles a representative test request without restart loops.
  3. An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits.
  4. Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail.

Explanation

Correct Answer

A:

Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption. Endpoint infrastructure can be healthy while the caller and scoring script disagree on their data contract. a direct corrective action is to align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML….

Incorrect Answers

B:

Deployment reaches healthy readiness and handles a representative test request without restart loops. That addresses a different configuration issue rather than the main requirement. Verify instead: Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML….

C:

An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits. That addresses a different configuration issue rather than the main requirement. Verify instead: Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption.

D:

Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail. That addresses a different configuration issue rather than the main requirement. Verify instead: Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML….

Question 693

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An engineer promotes the model with the lowest training loss even though the held-out validation loss worsens, indicating overfitting. The resolution must preserve quality gates, documented artifacts and rollback options. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.
  2. Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage.
  3. Inspect class prevalence, AutoML primary metric, confusion matrix, recall and precision of candidate runs and business error costs.
  4. Inspect request volume, concurrency, endpoint latency graphs, job timing and batch-friendly data path availability.

Explanation

Correct Answer

A:

Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. This is the most relevant evidence for new candidate chosen from training instead of validation results. A training objective measures fit on observed examples; generalization claims require independent validation and selection rules. The matching controlled remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An engineer….

Incorrect Answers

B:

Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. This would investigate pipeline cache reuses stale transform artifact rather than the documented new candidate chosen from training instead of validation results issue. The relevant investigation is: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.

C:

Inspect class prevalence, AutoML primary metric, confusion matrix, recall and precision of candidate runs and business error costs. This would investigate automl primary metric does not match rare-event goal rather than the documented new candidate chosen from training instead of validation results issue. The relevant investigation is: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.

D:

Inspect request volume, concurrency, endpoint latency graphs, job timing and batch-friendly data path availability. This would investigate overnight bulk scoring saturates interactive online endpoint rather than the documented new candidate chosen from training instead of validation results issue. The relevant investigation is: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.

Question 694

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML training pipeline intermittently starts training before its feature-engineering output is ready because the training component references a static path instead of the upstream component's declared output. The operator must safeguard training reproducibility and serving continuity. What measured outcome validates the solution while preserving the stated constraints?

  1. A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand.
  2. The winning child run has the best intended validation metric among eligible candidates and is reevaluated on unseen holdout data.
  3. Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
  4. The feature job completes before training consumes its versioned output in repeated orchestrated executions.

Explanation

Correct Answer

D:

The feature job completes before training consumes its versioned output in repeated orchestrated executions. Component dependency edges in Azure ML are determined by declared data bindings, not by visual position in a notebook or YAML file. a direct corrective action is to bind training input directly to the feature component's typed output to establish the correct pipeline dependency. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML….

Incorrect Answers

A:

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: The feature job completes before training consumes its versioned output in repeated orchestrated executions.

B:

The winning child run has the best intended validation metric among eligible candidates and is reevaluated on unseen holdout data. That addresses a different configuration issue rather than the main requirement. Verify instead: The feature job completes before training consumes its versioned output in repeated orchestrated executions.

C:

Overnight processing completes within its processing window and interactive endpoint latency remains within SLA. That addresses a different configuration issue rather than the main requirement. Verify instead: The feature job completes before training consumes its versioned output in repeated orchestrated executions.

Question 695

During a Foundry generative AI quality and observability incident, the following condition occurs: A Foundry quality monitor aggregates responses from old and new agent deployments, masking a groundedness regression in the new version. The fix must preserve evaluation validity and avoid unnecessary user-data collection. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate.
  2. Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
  3. Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
  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:

Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate. This targets foundry continuous evaluation ignores production deployment version. Aggregate monitoring can hide release-specific failures; quality assessment needs traceable version attribution. Verify the failure through: Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results. Validate success with: A canary regression is visible independently of stable baseline traffic before expanding rollout. This matters here because a Foundry quality monitor aggregates responses from old and new agent deployments, masking a groundedness regression….

Incorrect Answers

B:

Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This could address debug traces leak secrets and retrieved personal records, but it does not solve the specified foundry continuous evaluation ignores production deployment version failure. The matching remediation is: Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate. This matters here because a Foundry quality monitor aggregates responses from old and new agent deployments, masking a groundedness regression….

C:

Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change. This could address generation latency spike blamed on retrieval without breakdown, but it does not solve the specified foundry continuous evaluation ignores production deployment version failure. The matching remediation is: Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate.

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 foundry continuous evaluation ignores production deployment version failure. The matching remediation is: Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate.

Question 696

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML training pipeline intermittently starts training before its feature-engineering output is ready because the training component references a static path instead of the upstream component's declared output. The resolution must preserve quality gates, documented artifacts and rollback options. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry.
  2. Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.
  3. Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results.
  4. Compare notebook kernel package list, managed job environment asset, dependency lock file and the remote import traceback.

Explanation

Correct Answer

B:

Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. This is the most relevant evidence for pipeline graph omits feature-build dependency. Component dependency edges in Azure ML are determined by declared data bindings, not by visual position in a notebook or YAML file. The matching controlled remediation is: Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.

Incorrect Answers

A:

Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry. This would investigate sweep concurrency overwhelms scarce gpu quota rather than the documented pipeline graph omits feature-build dependency issue. The relevant investigation is: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.

C:

Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. This would investigate endpoint deployment health probe fails before model initialization rather than the documented pipeline graph omits feature-build dependency issue. The relevant investigation is: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.

D:

Compare notebook kernel package list, managed job environment asset, dependency lock file and the remote import traceback. This would investigate notebook experiment installs packages only in interactive kernel rather than the documented pipeline graph omits feature-build dependency issue. The relevant investigation is: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.

Question 697

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An engineer promotes the model with the lowest training loss even though the held-out validation loss worsens, indicating overfitting. The resolution must preserve quality gates, documented artifacts and rollback options. Which acceptance test shows the AI operations defect is corrected?

  1. Local notebook and managed job both import the same pinned dependency and generate comparable model outputs.
  2. New deployment workflows cannot select the retired version while required historic audit artifacts remain available.
  3. The selected version meets validation criteria without depending on apparent fit to the training examples alone.
  4. Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported.

Explanation

Correct Answer

C:

The selected version meets validation criteria without depending on apparent fit to the training examples alone. A training objective measures fit on observed examples; generalization claims require independent validation and selection rules. a direct corrective action is to use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An engineer….

Incorrect Answers

A:

Local notebook and managed job both import the same pinned dependency and generate comparable model outputs. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected version meets validation criteria without depending on apparent fit to the training examples alone.

B:

New deployment workflows cannot select the retired version while required historic audit artifacts remain available. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected version meets validation criteria without depending on apparent fit to the training examples alone.

D:

Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected version meets validation criteria without depending on apparent fit to the training examples alone. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An engineer….

Question 698

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML production model serves predictions, but the operator reports daily accuracy without any actual outcome labels arriving until several weeks later. The resolution must preserve quality gates, documented artifacts and rollback options. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
  2. Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
  3. Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes.
  4. Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.

Explanation

Correct Answer

D:

Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. This is the most relevant evidence for accuracy monitoring lacks delayed outcome labels. Model performance against ground truth cannot be measured correctly before outcomes are known; operational health signals are not substitutes for labeled accuracy. The matching controlled remediation is: Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

Incorrect Answers

A:

Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. This would investigate model registry latest alias points to unapproved experiment rather than the documented accuracy monitoring lacks delayed outcome labels issue. The relevant investigation is: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.

B:

Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts. This would investigate endpoint latency average conceals tail degradation rather than the documented accuracy monitoring lacks delayed outcome labels issue. The relevant investigation is: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.

C:

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 accuracy monitoring lacks delayed outcome labels issue. The relevant investigation is: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.

Question 699

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An AutoML classification search reports near-perfect accuracy because the supplied training dataset includes a field recorded only after the real customer outcome is known. The resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
  2. Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.
  3. Add the vetted package to a versioned Azure ML environment and submit the notebook's training logic as a reproducible job.
  4. Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

Explanation

Correct Answer

B:

Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This targets automated ml experiment uses leakage feature. Automated model search cannot correct information leakage caused by improperly constructed input data and validation boundaries. Verify the failure through: Review AutoML featurization, data collection timestamps, target leakage candidates, split strategy and training-versus-production feature availability. Validate success with: Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An AutoML….

Incorrect Answers

A:

Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This could address rollback cannot recover a previous environment version, but it does not solve the specified automated ml experiment uses leakage feature failure. The matching remediation is: Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.

C:

Add the vetted package to a versioned Azure ML environment and submit the notebook's training logic as a reproducible job. This could address notebook experiment installs packages only in interactive kernel, but it does not solve the specified automated ml experiment uses leakage feature failure. The matching remediation is: Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.

D:

Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed. This could address pipeline cache reuses stale transform artifact, but it does not solve the specified automated ml experiment uses leakage feature failure. The matching remediation is: Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An AutoML….

Question 700

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A new Azure ML workspace starts but managed training cannot retrieve approved secrets because deployment references a Key Vault belonging to an unrelated project. The team must preserve approved access, model provenance and private network constraints. Which investigation best verifies the cause before changing production configuration?

  1. Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.
  2. Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest.
  3. Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.
  4. Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum.

Explanation

Correct Answer

C:

Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file. This is the most relevant evidence for workspace dependencies point to unrelated secrets vault. A workspace can exist while supporting Key Vault, storage or monitoring dependencies are incorrectly associated; successful resource creation alone is not end-to-end readiness. The matching controlled remediation is: Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration. This matters here because a new Azure ML workspace starts but managed training cannot retrieve approved secrets because deployment references….

Incorrect Answers

A:

Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations. This would investigate reusable component hardcodes workspace-specific asset path rather than the documented workspace dependencies point to unrelated secrets vault issue. The relevant investigation is: Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

B:

Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest. This would investigate azure ml workspace deployed in the wrong subscription rather than the documented workspace dependencies point to unrelated secrets vault issue. The relevant investigation is: Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

D:

Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. This would investigate datastore uri selects the incorrect storage container rather than the documented workspace dependencies point to unrelated secrets vault issue. The relevant investigation is: Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

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