Microsoft AI-300 Practice Test 99
Question 980
During a regulated Azure ML workspace infrastructure review, 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 team must preserve approved access, model provenance and private network constraints. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events.
- Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records.
- Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors.
- Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
Explanation
Correct Answer
C:Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors. This is the most relevant evidence for 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. The matching controlled 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 a tabular classification pipeline expects named columns but a newly registered MLTable asset points to CSV files….
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 mltable data asset schema mismatches training code issue. The relevant investigation is: Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors.
B:Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. This would investigate github deployment pipeline omits secure environment approvals rather than the documented mltable data asset schema mismatches training code issue. The relevant investigation is: Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors. This matters here because a tabular classification pipeline expects named columns but a newly registered MLTable asset points to CSV files….
D: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 mltable data asset schema mismatches training code issue. The relevant investigation is: Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors.
Question 981
During a retrieval or model-customization performance review, the following condition occurs: A customer support model fine-tuned on historical chats becomes inconsistent because examples mix strict JSON tool calls with casual prose for identical task types. The change must keep citations, privacy and previously approved behavior intact. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating.
- Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage.
- Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior.
- Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
- Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.
Explanation
Correct Answers
A:Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating. This targets supervised fine-tuning dataset includes conflicting assistant behaviors. Supervised fine-tuning learns patterns in labeled examples; contradictory targets can degrade reliability even when many examples are provided. Verify the failure through: Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. Validate success with: The customized model returns the approved structured behavior on held-out scenarios without a spike in schema violations. This matters here because a customer support model fine-tuned on historical chats becomes inconsistent because examples mix strict JSON tool….
C:Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. This is the most relevant evidence for supervised fine-tuning dataset includes conflicting assistant behaviors. Supervised fine-tuning learns patterns in labeled examples; contradictory targets can degrade reliability even when many examples are provided. The matching controlled remediation is: Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating. This matters here because a customer support model fine-tuned on historical chats becomes inconsistent because examples mix strict JSON tool….
Incorrect Answers
B:Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. This is associated with fine-tuned model loses safety boundary after customization, not the essential evidence-and-fix pair for supervised fine-tuning dataset includes conflicting assistant behaviors. First examine: Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. Then correct: Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating.
D:Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This is associated with fine-tune production endpoint references deleted training artifact, not the essential evidence-and-fix pair for supervised fine-tuning dataset includes conflicting assistant behaviors. First examine: Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. Then correct: Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating. This matters here because a customer support model fine-tuned on historical chats becomes inconsistent because examples mix strict JSON tool….
E:Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This is associated with hybrid retrieval double-counts outdated documents, not the essential evidence-and-fix pair for supervised fine-tuning dataset includes conflicting assistant behaviors. First examine: Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. Then correct: Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating. This matters here because a customer support model fine-tuned on historical chats becomes inconsistent because examples mix strict JSON tool….
Question 982
While preparing a secure Foundry model or agent release, the following condition occurs: A customer assistant must handle Turkish and Arabic queries, yet the chosen model is approved based only on English benchmark scores and performs poorly in the required languages. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which investigation best verifies the cause before changing production configuration?
- Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.
- Compare model deployment version pinning, response schemas, regression dataset, rollout timeline and application parser errors.
- Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
- Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
Explanation
Correct Answer
C:Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. This is the most relevant evidence for multilingual model selection fails target-language quality. Model selection for a multilingual workload requires evaluation in the actual languages and use cases rather than generic model rankings. The matching controlled remediation is: Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A customer assistant must….
Incorrect Answers
A:Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This would investigate network allowlist exposes production model endpoint to test subnet rather than the documented multilingual model selection fails target-language quality issue. The relevant investigation is: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
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 multilingual model selection fails target-language quality issue. The relevant investigation is: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
D:Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. This would investigate provisioned model update exceeds regional capacity ceiling rather than the documented multilingual model selection fails target-language quality issue. The relevant investigation is: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
Question 983
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A team claims prompt B is better than prompt A, but B runs on a newer foundation model so the measured improvement cannot be attributed to the prompt change. The deployment must retain governed identities, endpoint contracts and auditable release history. Which investigation best verifies the cause before changing production configuration?
- Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.
- Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization.
- Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.
- Inspect prompt repository history, example dataset provenance, PII classification, branch access controls and affected downstream forks.
Explanation
Correct Answer
C:Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes. This is the most relevant evidence for prompt a/b test uses different model versions in each arm. Experimental prompt comparisons require controlling confounders; a simultaneous model upgrade prevents a valid prompt-only attribution. The matching controlled remediation is: Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics. This matters here because a team claims prompt B is better than prompt A, but B runs on a newer foundation model so the measured improvement….
Incorrect Answers
A:Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. This would investigate prompt variant comparison measures fluency not task success rather than the documented prompt a/b test uses different model versions in each arm issue. The relevant investigation is: Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.
B:Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. This would investigate foundry project links to wrong deployed model resource rather than the documented prompt a/b test uses different model versions in each arm issue. The relevant investigation is: Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.
D:Inspect prompt repository history, example dataset provenance, PII classification, branch access controls and affected downstream forks. This would investigate prompt repository references secret customer examples rather than the documented prompt a/b test uses different model versions in each arm issue. The relevant investigation is: Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.
Question 984
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A retail demand model triggers constant drift alerts because its production Christmas data is compared only against a summer reference dataset without accounting for known seasonal regimes. The operator must safeguard training reproducibility and serving continuity. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes.
- Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records.
- Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
- Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook.
Explanation
Correct Answer
A:Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. This is the most relevant evidence for data drift monitor uses wrong reference season. Data drift measurement depends on a chosen reference distribution; a statistically different season is not automatically a harmful model change. The matching controlled remediation is: Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A retail demand….
Incorrect Answers
B:Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. This would investigate retraining pipeline deploys without model quality gate rather than the documented data drift monitor uses wrong reference season issue. The relevant investigation is: Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A retail demand….
C: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 data drift monitor uses wrong reference season issue. The relevant investigation is: Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A retail demand….
D:Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. This would investigate incident rollback artifact was deleted instead of archived rather than the documented data drift monitor uses wrong reference season issue. The relevant investigation is: Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes.
Question 985
While optimizing a production RAG or fine-tuned model service, the following condition occurs: An operations chatbot answers 'I cannot find it' to precise internal procedure questions because its vector search similarity threshold was raised above scores returned by the relevant documents. The resulting model must meet held-out quality and security criteria. Which TWO complementary choices identify the issue and correct it? Select TWO.
- Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall.
- Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
- Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
- Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.
- Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
Explanation
Correct Answers
A:Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. This is the most relevant evidence for rag similarity threshold filters all relevant evidence. Vector similarity thresholds control recall and precision; a threshold chosen without validation can suppress even the best available evidence. The matching controlled remediation is: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: An operations chatbot….
B:Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise. This targets rag similarity threshold filters all relevant evidence. Vector similarity thresholds control recall and precision; a threshold chosen without validation can suppress even the best available evidence. Verify the failure through: Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. Validate success with: Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: An operations chatbot….
Incorrect Answers
C:Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails. This is associated with rag a/b experiment judges only click-through not factuality, not the essential evidence-and-fix pair for rag similarity threshold filters all relevant evidence. First examine: Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. Then correct: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
D:Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata. This is associated with hybrid retrieval double-counts outdated documents, not the essential evidence-and-fix pair for rag similarity threshold filters all relevant evidence. First examine: Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. Then correct: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: An operations chatbot….
E:Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This is associated with fine-tune production endpoint references deleted training artifact, not the essential evidence-and-fix pair for rag similarity threshold filters all relevant evidence. First examine: Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. Then correct: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
Question 986
While preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot produces less useful answers for one customer cohort because all examples in its template come from a narrow set of customer situations. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which production-safe remediation should the engineer apply to this AI workflow?
- Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
- Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
- Store reviewed prompt templates and configuration in version control and deploy immutable approved revisions through the release workflow.
- Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.
Explanation
Correct Answer
A:Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This targets few-shot prompt examples bias outputs toward one subgroup. Prompt variants can embed unrepresentative examples that change behavior; dataset diversity must be checked as carefully as model quality. Verify the failure through: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. Validate success with: Quality improves on relevant cohorts without exposing personal information or degrading approved common-case answers. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot….
Incorrect Answers
B:Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests. This could address interactive inference deployed on unsuitable batch-style compute, but it does not solve the specified few-shot prompt examples bias outputs toward one subgroup failure. The matching remediation is: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
C:Store reviewed prompt templates and configuration in version control and deploy immutable approved revisions through the release workflow. This could address prompt hotfix bypasses git review and loses rollback history, but it does not solve the specified few-shot prompt examples bias outputs toward one subgroup failure. The matching remediation is: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot….
D:Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling. This could address prompt includes untrusted retrieved instructions as system policy, but it does not solve the specified few-shot prompt examples bias outputs toward one subgroup failure. The matching remediation is: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
Question 987
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. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
- Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
- Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records.
- Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
Explanation
Correct Answer
A: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
B:Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. This would investigate bicep workspace declaration misses dependent private resources rather than the documented azure cli deployment silently targets sandbox defaults issue. The relevant investigation is: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
C:Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. This would investigate github deployment pipeline omits secure environment approvals rather than the documented azure cli deployment silently targets sandbox defaults issue. The relevant investigation is: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
D: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 azure cli deployment silently targets sandbox defaults issue. The relevant investigation is: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
Question 988
During a Foundry generative AI quality and observability incident, the following condition occurs: An incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly accessible Log Analytics workspace. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which production-safe remediation should the engineer apply to this AI workflow?
- Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.
- Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
- Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
- Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.
Explanation
Correct Answer
B:Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This targets debug traces leak secrets and retrieved personal records. Observability data has its own privacy and security boundary; unrestricted prompt and tool payload logging can create new exposure risks. Verify the failure through: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. Validate success with: Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports. This matters here because an incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly….
Incorrect Answers
A:Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers. This could address agent traces omit downstream tool failure reason, but it does not solve the specified debug traces leak secrets and retrieved personal records failure. The matching remediation is: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
C:Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand. This could address genai throughput report mixes responses and tokens, but it does not solve the specified debug traces leak secrets and retrieved personal records failure. The matching remediation is: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
D:Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric. This could address relevance evaluator uses wrong intended user query, but it does not solve the specified debug traces leak secrets and retrieved personal records failure. The matching remediation is: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
Question 989
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A fraud-screening AutoML run optimizes overall accuracy on a highly imbalanced dataset and selects a model that misses most fraud cases. The resolution must preserve quality gates, documented artifacts and rollback options. Which production-safe remediation should the engineer apply to this AI workflow?
- Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
- Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.
- Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.
- Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
Explanation
Correct Answer
D:Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training. This targets automl primary metric does not match rare-event goal. Accuracy can look high when predicting the majority class; model selection metrics should reflect the operational target and class imbalance. Verify the failure through: Inspect class prevalence, AutoML primary metric, confusion matrix, recall and precision of candidate runs and business error costs. Validate success with: Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A….
Incorrect Answers
A:Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs. This could address exploration notebook reads production data without reproducible snapshot, but it does not solve the specified automl primary metric does not match rare-event goal failure. The matching remediation is: Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
B:Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This could address automated ml experiment uses leakage feature, but it does not solve the specified automl primary metric does not match rare-event goal failure. The matching remediation is: Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
C:Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This could address missing feature values escape input drift checks, but it does not solve the specified automl primary metric does not match rare-event goal failure. The matching remediation is: Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
Question 990
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML training pipeline logs losses successfully but fails its packaging stage because MLflow autologging was configured with model logging disabled and no manual model artifact was saved. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
- Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.
- Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
- Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.
- Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs.
Explanation
Correct Answers
C:Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature. This targets autologging excludes required model artifact. Metrics and model artifacts are separately tracked by MLflow, so useful loss curves do not imply a registered loadable model exists. Verify the failure through: Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. Validate success with: The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML….
E:Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. This is the most relevant evidence for autologging excludes required model artifact. Metrics and model artifacts are separately tracked by MLflow, so useful loss curves do not imply a registered loadable model exists. The matching controlled remediation is: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML….
Incorrect Answers
A:Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This is associated with run comparison uses incompatible validation populations, not the essential evidence-and-fix pair for autologging excludes required model artifact. First examine: Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. Then correct: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
B:Bind training input directly to the feature component's typed output to establish the correct pipeline dependency. This is associated with pipeline graph omits feature-build dependency, not the essential evidence-and-fix pair for autologging excludes required model artifact. First examine: Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. Then correct: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
D: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 autologging excludes required model artifact. First examine: Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. Then correct: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML….