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 100

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.

  1. Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
  2. Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.
  3. Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
  4. Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.
  5. 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….

Question 991

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. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Inspect monitoring sample filters, event statuses, language distribution, evaluator eligibility and collected trace metadata.
  2. Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles.
  3. Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.
  4. Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.

Explanation

Correct Answer

C:

Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. This is the most relevant evidence for 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. The matching controlled remediation is: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. 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:

Inspect monitoring sample filters, event statuses, language distribution, evaluator eligibility and collected trace metadata. This would investigate continuous monitoring has no representative sampling coverage rather than the documented debug traces leak secrets and retrieved personal records issue. The relevant investigation is: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.

B:

Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. This would investigate generation latency spike blamed on retrieval without breakdown rather than the documented debug traces leak secrets and retrieved personal records issue. The relevant investigation is: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. This matters here because an incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly….

D:

Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. This would investigate content safety evaluation omits prompt injection tests rather than the documented debug traces leak secrets and retrieved personal records issue. The relevant investigation is: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.

Question 992

While optimizing a production RAG or fine-tuned model service, the following condition occurs: A RAG search index blends keyword and vector results but weights retired versions of a procedure equally with current publications, so old policy text appears first. The resulting model must meet held-out quality and security criteria. Which targeted Azure AI operations change best addresses the documented problem?

  1. Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
  2. Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.
  3. Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
  4. Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.

Explanation

Correct Answer

B:

Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This targets hybrid retrieval double-counts outdated documents. Hybrid scoring does not inherently enforce document freshness or authoritative version; metadata filtering is a separate ranking control. Verify the failure through: Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata. Validate success with: Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A RAG search index….

Incorrect Answers

A:

Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails. This could address rag a/b experiment judges only click-through not factuality, but it does not solve the specified hybrid retrieval double-counts outdated documents failure. The matching remediation is: Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.

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 hybrid retrieval double-counts outdated documents failure. The matching remediation is: Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A RAG search index….

D:

Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions. This could address fine-tuned candidate bypasses promotion review after training, but it does not solve the specified hybrid retrieval double-counts outdated documents failure. The matching remediation is: Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.

Question 993

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A team upgrades a custom evaluator prompt and compares this month's agent scores to last month's, even though the grading rubric and baseline model changed. The workflow must produce measurable quality, safety and performance evidence. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Make required quality/safety criteria explicit CI gates and stop deployment when evaluated scores fail the approved tolerances.
  2. Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content.
  3. Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
  4. Apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts.

Explanation

Correct Answer

C:

Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This targets custom evaluator silently changes its scoring rubric. Evaluation metrics are outputs of versioned assessment logic; changing a judge or rubric can change scores without any underlying agent change. Verify the failure through: Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. Validate success with: Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A team….

Incorrect Answers

A:

Make required quality/safety criteria explicit CI gates and stop deployment when evaluated scores fail the approved tolerances. This could address evaluation workflow fails to block degraded agent deployment, but it does not solve the specified custom evaluator silently changes its scoring rubric failure. The matching remediation is: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.

B:

Extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content. This could address harmful content probe set excludes multilingual input, but it does not solve the specified custom evaluator silently changes its scoring rubric failure. The matching remediation is: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.

D:

Apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts. This could address continuous monitoring has no representative sampling coverage, but it does not solve the specified custom evaluator silently changes its scoring rubric failure. The matching remediation is: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.

Question 994

During a Microsoft Foundry generative AI deployment review, 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 deployment must retain governed identities, endpoint contracts and auditable release history. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
  2. Inspect deployment routing weights, evaluated model versions, incident timing, canary quality dashboards and rollback path.
  3. Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution.
  4. Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.

Explanation

Correct Answer

C:

Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. This is the most relevant evidence for 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. The matching controlled remediation is: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This matters here because a loan-support chatbot produces less useful answers for one customer cohort because all examples in its template….

Incorrect Answers

A:

Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions. This would investigate prompt hotfix bypasses git review and loses rollback history rather than the documented few-shot prompt examples bias outputs toward one subgroup issue. The relevant investigation is: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution.

B:

Inspect deployment routing weights, evaluated model versions, incident timing, canary quality dashboards and rollback path. This would investigate new foundation model replaces production without canary rather than the documented few-shot prompt examples bias outputs toward one subgroup issue. The relevant investigation is: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution.

D:

Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes. This would investigate prompt a/b test uses different model versions in each arm rather than the documented few-shot prompt examples bias outputs toward one subgroup issue. The relevant investigation is: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution.

Question 995

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A public-facing GenAI service is cleared for launch after English safety checks, but hostile user requests in supported non-English languages bypass the tested safety evaluator. The workflow must produce measurable quality, safety and performance evidence. Which acceptance test shows the AI operations defect is corrected?

  1. Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports.
  2. Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable.
  3. An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.
  4. The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query.

Explanation

Correct Answer

B:

Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable. Safety evaluation quality depends on representative inputs; English-only coverage cannot establish protection for a multilingual product. a direct corrective action is to extend safety testing to representative supported languages and calibrate policy thresholds without weakening necessary allowed content. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A….

Incorrect Answers

A:

Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports. That addresses a different configuration issue rather than the main requirement. Verify instead: Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable.

C:

An adversarial document cannot cause unapproved transactions while authorized research questions still succeed. That addresses a different configuration issue rather than the main requirement. Verify instead: Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable.

D:

The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query. That addresses a different configuration issue rather than the main requirement. Verify instead: Multilingual adversarial probes are handled consistently within the approved safety policy and ordinary requests remain usable.

Question 996

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 targeted Azure AI operations change best addresses the documented problem?

  1. Store reviewed prompt templates and configuration in version control and deploy immutable approved revisions through the release workflow.
  2. Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.
  3. Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
  4. Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.

Explanation

Correct Answer

D:

Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics. This targets 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. Verify the failure through: Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes. Validate success with: The comparison isolates prompt differences and produces reproducible evidence of quality and latency trade-offs. 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:

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 prompt a/b test uses different model versions in each arm failure. The matching remediation is: Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.

B:

Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity. This could address foundry private endpoint dns resolves to public ip, but it does not solve the specified prompt a/b test uses different model versions in each arm failure. The matching 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….

C:

Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This could address prompt variant comparison measures fluency not task success, but it does not solve the specified prompt a/b test uses different model versions in each arm failure. The matching remediation is: Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.

Question 997

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. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
  2. Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
  3. Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration.
  4. Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management.

Explanation

Correct Answer

B:

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 a GitHub deployment workload that only uploads models receives broad subscription Contributor rights, enabling it to….

Incorrect Answers

A:

Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules. This could address oidc subject filter trusts unreviewed pull-request branches, but it does not solve the specified workspace contributor role granted to untrusted automation failure. The matching remediation is: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.

C:

Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration. This could address workspace dependencies point to unrelated secrets vault, but it does not solve the specified workspace contributor role granted to untrusted automation failure. The matching remediation is: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.

D:

Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management. This could address datastore authentication relies on expiring account key, but it does not solve the specified workspace contributor role granted to untrusted automation failure. The matching remediation is: Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.

Question 998

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the evaluation measures only fluency and omits task completion and grounding. 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?

  1. Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
  2. Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
  3. Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.
  4. Inspect the prompt template, target JSON schema, model output examples, parser exceptions and current evaluation dataset.

Explanation

Correct Answer

C:

Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. This is the most relevant evidence for prompt variant comparison measures fluency not task success. A fluent response can still be wrong or unhelpful; prompt tuning requires evaluation metrics tied to application goals. The matching controlled remediation is: Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This matters here because a new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the….

Incorrect Answers

A:

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 prompt variant comparison measures fluency not task success issue. The relevant investigation is: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.

B:

Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions. This would investigate prompt hotfix bypasses git review and loses rollback history rather than the documented prompt variant comparison measures fluency not task success issue. The relevant investigation is: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.

D:

Inspect the prompt template, target JSON schema, model output examples, parser exceptions and current evaluation dataset. This would investigate prompt omits explicit structured answer schema rather than the documented prompt variant comparison measures fluency not task success issue. The relevant investigation is: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. This matters here because a new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the….

Question 999

While preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its LLM successfully but receives access denied when querying an Azure AI Search index because the assigned managed identity lacks search data reader rights. 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?

  1. Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.
  2. Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
  3. Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.
  4. Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.

Explanation

Correct Answer

D:

Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This targets agent runtime managed identity cannot read retrieval data. Foundry model access and Azure AI Search data-plane authorization are separate permission boundaries for a retrieval-augmented agent. Verify the failure through: Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests. Validate success with: Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its….

Incorrect Answers

A:

Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates. This could address foundry environment mixes development and production agent resources, but it does not solve the specified agent runtime managed identity cannot read retrieval data failure. The matching remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its….

B:

Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates. This could address multilingual model selection fails target-language quality, but it does not solve the specified agent runtime managed identity cannot read retrieval data failure. The matching remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.

C:

Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection. This could address foundry project links to wrong deployed model resource, but it does not solve the specified agent runtime managed identity cannot read retrieval data failure. The matching remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its….

Question 1000

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A scheduled Azure ML pipeline appears fast but returns last week's encoded features because a preprocessing component is reused under inputs that do not capture the changed transformation configuration. The operator must safeguard training reproducibility and serving continuity. Which acceptance test shows the AI operations defect is corrected?

  1. Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields.
  2. Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria.
  3. A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.
  4. The feature job completes before training consumes its versioned output in repeated orchestrated executions.

Explanation

Correct Answer

C:

A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job. Pipeline reuse is correct only when the declared inputs and environment represent all behaviorally relevant computation dependencies. a direct corrective action is to version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A scheduled….

Incorrect Answers

A:

Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.

B:

Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.

D:

The feature job completes before training consumes its versioned output in repeated orchestrated executions. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.

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