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 58

Question 570

During a Foundry generative AI quality and observability incident, the following condition occurs: An enterprise support agent appears successful on isolated questions but fails follow-up conversations because the test dataset discards prior chat turns and tool context. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which investigation best verifies the cause before changing production configuration?

  1. Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.
  2. Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
  3. Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence.
  4. Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results.

Explanation

Correct Answer

A:

Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. This is the most relevant evidence for multi-turn agent evaluation uses isolated last message only. Multi-turn agents depend on conversation state; evaluating only the final prompt can miss context handling, memory and tool-use errors. The matching controlled remediation is: Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.

Incorrect Answers

B:

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 multi-turn agent evaluation uses isolated last message only issue. The relevant investigation is: Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.

C:

Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. This would investigate harmful content probe set excludes multilingual input rather than the documented multi-turn agent evaluation uses isolated last message only issue. The relevant investigation is: Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.

D:

Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results. This would investigate foundry continuous evaluation ignores production deployment version rather than the documented multi-turn agent evaluation uses isolated last message only issue. The relevant investigation is: Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.

Question 571

While deploying reproducible Azure Machine Learning infrastructure, 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 change must remain limited to authorized workspaces and avoid unreviewed production impact. Which investigation best verifies the cause before changing production configuration?

  1. Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error.
  2. Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
  3. Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance.
  4. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error. This would investigate pipeline component output type mismatches consumer 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:

Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. This would investigate oidc subject filter trusts unreviewed pull-request branches 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 GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This would investigate iac workflow lacks repeatable infrastructure validation 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 572

While optimizing a production RAG or fine-tuned model service, the following condition occurs: A customized foundation model is promoted for helpfulness gains, but regression checks reveal it now produces unsafe prohibited instructions on standard policy test inputs. The resulting model must meet held-out quality and security criteria. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage.
  2. Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release.
  3. Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking.
  4. Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior.
  5. Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.

Explanation

Correct Answers

A:

Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. This is the most relevant evidence for fine-tuned model loses safety boundary after customization. Model customization can affect safety and instruction adherence; better task metrics alone are not sufficient for release approval. The matching controlled remediation is: Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A customized….

B:

Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release. This targets fine-tuned model loses safety boundary after customization. Model customization can affect safety and instruction adherence; better task metrics alone are not sufficient for release approval. Verify the failure through: Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. Validate success with: The approved version meets safety requirements on held-out adversarial tests and its model artifact is traceable to the training record. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A customized….

Incorrect Answers

C:

Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking. This is associated with pure vector search misses exact regulatory clause codes, not the essential evidence-and-fix pair for fine-tuned model loses safety boundary after customization. First examine: Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. Then correct: Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release.

D:

Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. This is associated with supervised fine-tuning dataset includes conflicting assistant behaviors, not the essential evidence-and-fix pair for fine-tuned model loses safety boundary after customization. First examine: Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. Then correct: Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A customized….

E:

Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content. This is associated with synthetic training examples copy private customer identifiers, not the essential evidence-and-fix pair for fine-tuned model loses safety boundary after customization. First examine: Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. Then correct: Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release.

Question 573

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A drift-based retraining workflow runs every hour during a low-volume holiday weekend because its threshold ignores minimum sample size and confidence. The operator must safeguard training reproducibility and serving continuity. Which acceptance test shows the AI operations defect is corrected?

  1. Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline.
  2. Normal seasonal variation stops generating false incidents and genuine distribution changes still cross documented alert criteria.
  3. Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable.
  4. A poor candidate is retained for review without reaching production, and qualifying candidates progress through controlled canary rollout.

Explanation

Correct Answer

A:

Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline. Drift-triggered retraining must balance statistical reliability against response time; an alert based on tiny samples can be misleading. a direct corrective action is to add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A drift-based….

Incorrect Answers

B:

Normal seasonal variation stops generating false incidents and genuine distribution changes still cross documented alert criteria. That addresses a different configuration issue rather than the main requirement. Verify instead: Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline.

C:

Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable. That addresses a different configuration issue rather than the main requirement. Verify instead: Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline.

D:

A poor candidate is retained for review without reaching production, and qualifying candidates progress through controlled canary rollout. That addresses a different configuration issue rather than the main requirement. Verify instead: Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline.

Question 574

During a Foundry generative AI quality and observability incident, the following condition occurs: A retrieval assistant's monthly bill grows, but its cost dashboard counts only chat completion tokens and omits repeated query and document embedding operations. 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. Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results.
  2. Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.
  3. Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples.
  4. Inspect tokens per request, input/output token ratios, concurrency, throttling status and model deployment quota.

Explanation

Correct Answer

B:

Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags. This is the most relevant evidence for token cost report omits embedding requests. GenAI cost analysis must include all model and supporting resources; tracking only final generation underestimates retrieval and indexing spend. The matching controlled remediation is: Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.

Incorrect Answers

A:

Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results. This would investigate foundry continuous evaluation ignores production deployment version rather than the documented token cost report omits embedding requests issue. The relevant investigation is: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

C:

Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. This would investigate relevance evaluator uses wrong intended user query rather than the documented token cost report omits embedding requests issue. The relevant investigation is: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

D:

Inspect tokens per request, input/output token ratios, concurrency, throttling status and model deployment quota. This would investigate genai throughput report mixes responses and tokens rather than the documented token cost report omits embedding requests issue. The relevant investigation is: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

Question 575

As an MLOps engineer reviews a model training or inference pipeline, 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 resolution must preserve quality gates, documented artifacts and rollback options. Which observable postchange result proves the intended remediation succeeded?

  1. The finished job produces a discoverable artifact that can be loaded and registered by the next pipeline stage.
  2. New deployment workflows cannot select the retired version while required historic audit artifacts remain available.
  3. The next test run appears only under the intended workspace with its parameters and model artifacts attached.
  4. A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

The finished job produces a discoverable artifact that can be loaded and registered by the next pipeline stage. 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:

New deployment workflows cannot select the retired version while required historic audit artifacts remain available. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.

C:

The next test run appears only under the intended workspace with its parameters and model artifacts attached. 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.

Question 576

During a Microsoft Foundry generative AI deployment review, the following condition occurs: An expense processing agent needs to interpret invoice images but the deployed text-only model endpoint cannot accept image content in its request schema. The deployment must retain governed identities, endpoint contracts and auditable release history. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.
  2. Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.
  3. Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses.
  4. Build and test a compatible version-pinned serving environment and promote the corrected managed model deployment.
  5. Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

Explanation

Correct Answers

C:

Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. This is the most relevant evidence for vision input sent to text-only foundation model. Model capability and endpoint payload contracts determine which modalities can be processed; a text-only deployment cannot reliably infer pixels. The matching controlled remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

E:

Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step. This targets vision input sent to text-only foundation model. Model capability and endpoint payload contracts determine which modalities can be processed; a text-only deployment cannot reliably infer pixels. Verify the failure through: Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. Validate success with: A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.

Incorrect Answers

A:

Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load. This is associated with provisioned deployment pays for idle unused capacity, not the essential evidence-and-fix pair for vision input sent to text-only foundation model. First examine: Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. Then correct: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

B:

Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This is associated with agent runtime managed identity cannot read retrieval data, not the essential evidence-and-fix pair for vision input sent to text-only foundation model. First examine: Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. Then correct: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

D:

Build and test a compatible version-pinned serving environment and promote the corrected managed model deployment. This is associated with managed foundation model deployment lacks compatible runtime image, not the essential evidence-and-fix pair for vision input sent to text-only foundation model. First examine: Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. Then correct: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

Question 577

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A model is rolled back to old weights but its scoring container still uses the new incompatible environment, so production errors continue after rollback. The operator must safeguard training reproducibility and serving continuity. Which observable postchange result proves the intended remediation succeeded?

  1. Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption.
  2. A representative rollback test restores known-good predictions and endpoint health within the recovery target.
  3. A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.
  4. P95/P99 and error-rate service objectives recover under representative peak-load traffic without unrelated scale changes.

Explanation

Correct Answer

B:

A representative rollback test restores known-good predictions and endpoint health within the recovery target. A deployment's behavior depends on the whole inference package; changing model weights alone cannot undo incompatible runtime changes. a direct corrective action is to restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.

Incorrect Answers

A:

Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption. That addresses a different configuration issue rather than the main requirement. Verify instead: A representative rollback test restores known-good predictions and endpoint health within the recovery target.

C:

A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. That addresses a different configuration issue rather than the main requirement. Verify instead: A representative rollback test restores known-good predictions and endpoint health within the recovery target.

D:

P95/P99 and error-rate service objectives recover under representative peak-load traffic without unrelated scale changes. That addresses a different configuration issue rather than the main requirement. Verify instead: A representative rollback test restores known-good predictions and endpoint health within the recovery target.

Question 578

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team deletes the previously approved model after a new deployment, then cannot restore service when the new model fails canary checks. The resolution must preserve quality gates, documented artifacts and rollback options. What measured outcome validates the solution while preserving the stated constraints?

  1. A failed canary can restore the last approved model version without retraining or inventing replacement artifacts.
  2. Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria.
  3. The promotion report presents comparable metrics with documented confidence and class distribution before model approval.
  4. New deployment workflows cannot select the retired version while required historic audit artifacts remain available.

Explanation

Correct Answer

A:

A failed canary can restore the last approved model version without retraining or inventing replacement artifacts. Archiving and retention support model provenance and rollback; immediate deletion of the only stable model makes a deployment irreversible. a direct corrective action is to retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team….

Incorrect Answers

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 failed canary can restore the last approved model version without retraining or inventing replacement artifacts.

C:

The promotion report presents comparable metrics with documented confidence and class distribution before model approval. That addresses a different configuration issue rather than the main requirement. Verify instead: A failed canary can restore the last approved model version without retraining or inventing replacement artifacts.

D:

New deployment workflows cannot select the retired version while required historic audit artifacts remain available. That addresses a different configuration issue rather than the main requirement. Verify instead: A failed canary can restore the last approved model version without retraining or inventing replacement artifacts.

Question 579

While deploying reproducible Azure Machine Learning infrastructure, 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 change must remain limited to authorized workspaces and avoid unreviewed production impact. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
  2. Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.
  3. Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
  4. Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
  5. Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

Explanation

Correct Answers

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.

E:

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

Incorrect Answers

B:

Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This is associated with github action uses persistent azure client secret, not the essential evidence-and-fix pair for azure cli deployment silently targets sandbox defaults. First examine: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Then correct: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

C:

Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This is associated with datastore uri selects the incorrect storage container, not the essential evidence-and-fix pair for azure cli deployment silently targets sandbox defaults. First examine: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Then correct: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

D:

Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules. This is associated with oidc subject filter trusts unreviewed pull-request branches, not the essential evidence-and-fix pair for azure cli deployment silently targets sandbox defaults. First examine: Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. Then correct: Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.

Question 580

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A loan-classification model meets aggregate accuracy targets but its acceptance review never checks false-negative rates by relevant customer cohorts, obscuring a material disparity. The operator must safeguard training reproducibility and serving continuity. Which targeted Azure AI operations change best addresses the documented problem?

  1. Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.
  2. Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time.
  3. Write the model into the declared Azure ML job output path and track the versioned artifact used in registration.
  4. Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

Explanation

Correct Answer

D:

Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This targets responsible ai evaluation omits demographic cohort slices. Aggregate predictive quality does not establish responsible use across affected groups; evaluation must examine relevant harm and fairness dimensions. Verify the failure through: Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. Validate success with: Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A….

Incorrect Answers

A:

Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates. This could address model registry latest alias points to unapproved experiment, but it does not solve the specified responsible ai evaluation omits demographic cohort slices failure. The matching remediation is: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A….

B:

Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time. This could address feature retrieval specification missing from registered model, but it does not solve the specified responsible ai evaluation omits demographic cohort slices failure. The matching remediation is: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A….

C:

Write the model into the declared Azure ML job output path and track the versioned artifact used in registration. This could address training job does not persist output artifacts, but it does not solve the specified responsible ai evaluation omits demographic cohort slices failure. The matching remediation is: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

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