Microsoft AI-300 Practice Test 16
Question 150
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A GitHub deployment workload that only uploads models receives broad subscription Contributor rights, enabling it to modify unrelated application infrastructure. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
- Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
- Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema.
- Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.
- Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
Explanation
Correct Answers
A:Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant. This targets workspace contributor role granted to untrusted automation. An Azure resource role assignment grants management-plane capabilities according to scope and cannot be justified solely by pipeline convenience. Verify the failure through: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. Validate success with: Automated model registration succeeds while the principal cannot change unrelated networks, secrets or subscriptions. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A GitHub….
E:Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. This is the most relevant evidence for workspace contributor role granted to untrusted automation. An Azure resource role assignment grants management-plane capabilities according to scope and cannot be justified solely by pipeline convenience. The matching controlled remediation is: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A GitHub….
Incorrect Answers
B:Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances. This is associated with interactive compute instances remain running while unused, not the essential evidence-and-fix pair for workspace contributor role granted to untrusted automation. First examine: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. Then correct: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
C:Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema. This is associated with pipeline component output type mismatches consumer, not the essential evidence-and-fix pair for workspace contributor role granted to untrusted automation. First examine: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. Then correct: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
D:Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments. This is associated with datastore authentication relies on expiring account key, not the essential evidence-and-fix pair for workspace contributor role granted to untrusted automation. First examine: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. Then correct: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
Question 151
While preparing a secure Foundry model or agent release, the following condition occurs: A web front end that only calls an approved LLM deployment is assigned Foundry resource management privileges, allowing it to modify deployments and project settings. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which targeted Azure AI operations change best addresses the documented problem?
- Store reviewed prompt templates and configuration in version control and deploy immutable approved revisions through the release workflow.
- Deploy the governed Foundry resource and project in a supported compliant region with an available model option.
- Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
- Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.
Explanation
Correct Answer
C:Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This targets foundry administrator role granted to consumer application. Application inference rights should be separated from platform administration; granting project owner privileges expands the impact of a compromised app. Verify the failure through: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. Validate success with: The front end scores authorized requests but cannot create, delete or reconfigure model deployments. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A web front end that only….
Incorrect Answers
A: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 foundry administrator role granted to consumer application failure. The matching remediation is: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
B:Deploy the governed Foundry resource and project in a supported compliant region with an available model option. This could address foundry project created in mismatched resource location, but it does not solve the specified foundry administrator role granted to consumer application failure. The matching remediation is: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
D: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 administrator role granted to consumer application failure. The matching remediation is: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
Question 152
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A GitHub deployment workload that only uploads models receives broad subscription Contributor rights, enabling it to modify unrelated application infrastructure. 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.
- Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest.
- Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
- Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
Explanation
Correct Answer
C:Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. This is the most relevant evidence for workspace contributor role granted to untrusted automation. An Azure resource role assignment grants management-plane capabilities according to scope and cannot be justified solely by pipeline convenience. The matching controlled remediation is: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
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 workspace contributor role granted to untrusted automation issue. The relevant investigation is: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
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 contributor role granted to untrusted automation issue. The relevant investigation is: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
D: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 workspace contributor role granted to untrusted automation issue. The relevant investigation is: Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
Question 153
During a Foundry generative AI quality and observability incident, the following condition occurs: A support bot repeats its complete policy corpus in every prompt, increasing token costs and latency, although only a few retrieved paragraphs are relevant to each answer. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which investigation best verifies the cause before changing production configuration?
- Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.
- Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs.
- Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records.
- Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
Explanation
Correct Answer
D:Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. This is the most relevant evidence for prompt truncation strategy increases generated-token spend. Context volume affects token cost and latency; sending unnecessary text on every request is not equivalent to more reliable grounding. The matching controlled remediation is: Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples. This matters here because a support bot repeats its complete policy corpus in every prompt, increasing token costs and latency, although only….
Incorrect Answers
A:Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. This would investigate debug traces leak secrets and retrieved personal records rather than the documented prompt truncation strategy increases generated-token spend issue. The relevant investigation is: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
B:Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs. This would investigate agent traces omit downstream tool failure reason rather than the documented prompt truncation strategy increases generated-token spend issue. The relevant investigation is: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
C:Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records. This would investigate evaluation workflow fails to block degraded agent deployment rather than the documented prompt truncation strategy increases generated-token spend issue. The relevant investigation is: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
Question 154
As an AI operations team checks production agent evaluation evidence, 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 workflow must produce measurable quality, safety and performance evidence. Which production-safe remediation should the engineer apply to this AI workflow?
- Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
- Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
- Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate.
- Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.
Explanation
Correct Answer
C: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.
Incorrect Answers
A: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 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.
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.
D:Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency. This could address groundedness metric conflated with response fluency, 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 155
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A Bicep deployment provisions an Azure ML workspace but its associated storage, Key Vault and private endpoints are created after the workspace references them, producing intermittent deployment failures. The team must preserve approved access, model provenance and private network constraints. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
- Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
- Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.
- Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records.
Explanation
Correct Answer
A:Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. This is the most relevant evidence for bicep workspace declaration misses dependent private resources. Declarative infrastructure still requires a valid resource dependency graph and stable networking prerequisites; syntax validation alone does not enforce desired provisioning order. The matching controlled remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
Incorrect Answers
B: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 bicep workspace declaration misses dependent private resources issue. The relevant investigation is: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
C:Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This would investigate github action uses persistent azure client secret rather than the documented bicep workspace declaration misses dependent private resources issue. The relevant investigation is: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
D: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 bicep workspace declaration misses dependent private resources issue. The relevant investigation is: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
Question 156
While optimizing a production RAG or fine-tuned model service, the following condition occurs: A product support team plans expensive fine-tuning to memorize weekly price lists, even though the answers require current frequently edited catalog values. The resulting model must meet held-out quality and security criteria. Which investigation best verifies the cause before changing production configuration?
- Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior.
- Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow.
- Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents.
- Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence.
Explanation
Correct Answer
B:Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. This is the most relevant evidence for fine-tuning task selected when retrieval would better handle changing facts. Fine-tuning changes model behavior and knowledge imperfectly; retrieval is generally more suitable for fast-changing external facts. The matching controlled remediation is: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.
Incorrect Answers
A:Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. This would investigate supervised fine-tuning dataset includes conflicting assistant behaviors rather than the documented fine-tuning task selected when retrieval would better handle changing facts issue. The relevant investigation is: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow.
C:Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents. This would investigate rag a/b experiment judges only click-through not factuality rather than the documented fine-tuning task selected when retrieval would better handle changing facts issue. The relevant investigation is: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow.
D:Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. This would investigate fine-tune evaluation lacks drift checks for new customer terminology rather than the documented fine-tuning task selected when retrieval would better handle changing facts issue. The relevant investigation is: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow.
Question 157
During a regulated Azure ML workspace infrastructure review, the following condition occurs: An Azure ML training job authenticates with a managed identity but fails to download input data because it has workspace rights without Storage Blob Data Reader on the data container. The team must preserve approved access, model provenance and private network constraints. Which investigation best verifies the cause before changing production configuration?
- Check the component's registry name and version, target workspace identity, registry read permissions and referenced environment dependencies.
- Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
- Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.
- Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest.
Explanation
Correct Answer
B:Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. This is the most relevant evidence for job identity lacks blob reader data-plane rights. Workspace RBAC and Azure Storage data-plane roles are distinct; successful workspace authentication does not authorize every blob read. The matching controlled remediation is: Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.
Incorrect Answers
A:Check the component's registry name and version, target workspace identity, registry read permissions and referenced environment dependencies. This would investigate registry model asset not available to second workspace rather than the documented job identity lacks blob reader data-plane rights issue. The relevant investigation is: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
C:Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments. This would investigate datastore authentication relies on expiring account key rather than the documented job identity lacks blob reader data-plane rights issue. The relevant investigation is: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
D: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 job identity lacks blob reader data-plane rights issue. The relevant investigation is: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
Question 158
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A customer-service agent follows imperative instructions embedded in a retrieved help-center article because the prompt mixes document contents into its high-priority system instructions. The deployment must retain governed identities, endpoint contracts and auditable release history. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution.
- Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests.
- Inspect prompt repository history, example dataset provenance, PII classification, branch access controls and affected downstream forks.
- Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
Explanation
Correct Answer
B:Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. This is the most relevant evidence for prompt includes untrusted retrieved instructions as system policy. Retrieved text is task data, not an authorization source; prompt composition must preserve a trust boundary around untrusted context. The matching controlled remediation is: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling. This matters here because a customer-service agent follows imperative instructions embedded in a retrieved help-center article because the….
Incorrect Answers
A:Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. This would investigate few-shot prompt examples bias outputs toward one subgroup rather than the documented prompt includes untrusted retrieved instructions as system policy issue. The relevant investigation is: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. This matters here because a customer-service agent follows imperative instructions embedded in a retrieved help-center article because the….
C: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 includes untrusted retrieved instructions as system policy issue. The relevant investigation is: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests.
D:Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. This would investigate multilingual model selection fails target-language quality rather than the documented prompt includes untrusted retrieved instructions as system policy issue. The relevant investigation is: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests.
Question 159
While optimizing a production RAG or fine-tuned model service, the following condition occurs: A fine-tuned model endpoint cannot be recreated during disaster recovery because the training checkpoint and tokenizer artifacts were deleted after deployment. The resulting model must meet held-out quality and security criteria. Which targeted Azure AI operations change best addresses the documented problem?
- Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating.
- Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.
- Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
- Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
Explanation
Correct Answer
D:Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This targets fine-tune production endpoint references deleted training artifact. Custom model lifecycle management includes training lineage and artifact retention; an online endpoint alone is not a durable source of the full fine-tuned model package. Verify the failure through: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. Validate success with: A disaster-recovery deployment loads the reviewed customized model with matching tokenizer and runtime without repeating unrecoverable training.
Incorrect Answers
A:Clean and stratify the supervised fine-tuning data to a coherent supported task format before retraining and evaluating. This could address supervised fine-tuning dataset includes conflicting assistant behaviors, but it does not solve the specified fine-tune production endpoint references deleted training artifact failure. The matching remediation is: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
B:Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation. This could address fine-tuning task selected when retrieval would better handle changing facts, but it does not solve the specified fine-tune production endpoint references deleted training artifact failure. The matching remediation is: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
C:Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model. This could address embedding model replaced without reindexing stored vectors, but it does not solve the specified fine-tune production endpoint references deleted training artifact failure. The matching remediation is: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
Question 160
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 production-safe remediation should the engineer apply to this AI workflow?
- Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
- Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.
- Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.
- Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.
Explanation
Correct Answer
C:Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold. This targets 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. Verify the failure through: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. Validate success with: The selected version meets validation criteria without depending on apparent fit to the training examples alone.
Incorrect Answers
A:Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training. This could address automl primary metric does not match rare-event goal, but it does not solve the specified new candidate chosen from training instead of validation results failure. The matching remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.
B:Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This could address responsible ai evaluation omits demographic cohort slices, but it does not solve the specified new candidate chosen from training instead of validation results failure. The matching remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.
D: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 new candidate chosen from training instead of validation results failure. The matching remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.