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 19

Question 180

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A feature-engineering change is merged directly to the main branch without running schema and leakage tests, and the next scheduled model training uses incompatible features. The team must preserve approved access, model provenance and private network constraints. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Require protected pull requests and automated component tests before changes to production training code are merged.
  2. Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
  3. Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
  4. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.
  5. Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.

Explanation

Correct Answers

A:

Require protected pull requests and automated component tests before changes to production training code are merged. This targets notebook merge bypasses protected evaluation tests. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. Verify the failure through: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Validate success with: A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence. This matters here because a feature-engineering change is merged directly to the main branch without running schema and leakage tests, and the….

B:

Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This is the most relevant evidence for notebook merge bypasses protected evaluation tests. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. The matching controlled remediation is: Require protected pull requests and automated component tests before changes to production training code are merged. This matters here because a feature-engineering change is merged directly to the main branch without running schema and leakage tests, and the….

Incorrect Answers

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 notebook merge bypasses protected evaluation tests. First examine: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Then correct: Require protected pull requests and automated component tests before changes to production training code are merged.

D:

Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This is associated with iac workflow lacks repeatable infrastructure validation, not the essential evidence-and-fix pair for notebook merge bypasses protected evaluation tests. First examine: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Then correct: Require protected pull requests and automated component tests before changes to production training code are merged.

E:

Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This is associated with aml managed network blocks model registry egress, not the essential evidence-and-fix pair for notebook merge bypasses protected evaluation tests. First examine: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Then correct: Require protected pull requests and automated component tests before changes to production training code are merged.

Question 181

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A Foundry agent evaluation job runs against a CSV whose expected_answer column was mapped as user_query, so relevance and groundedness results are invalid. The workflow must produce measurable quality, safety and performance evidence. Which observable postchange result proves the intended remediation succeeded?

  1. Unsupported claims fail the release gate even when the answers are grammatically smooth.
  2. Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports.
  3. The evaluation reveals and measures failures that depend on follow-up context and the selected agent version improves those cases.
  4. Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.

Explanation

Correct Answer

D:

Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields. Generative evaluation depends on the semantic role of each dataset field; a syntactically valid CSV is not necessarily an evaluable response set. a direct corrective action is to correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.

Incorrect Answers

A:

Unsupported claims fail the release gate even when the answers are grammatically smooth. That addresses a different configuration issue rather than the main requirement. Verify instead: Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.

B:

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: Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.

C:

The evaluation reveals and measures failures that depend on follow-up context and the selected agent version improves those cases. That addresses a different configuration issue rather than the main requirement. Verify instead: Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.

Question 182

While preparing a secure Foundry model or agent release, the following condition occurs: An enterprise disables public network access to Foundry but its container app still resolves the model service hostname to a public endpoint, resulting in failed inference calls. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.
  2. Permit only the required documented tool and service destinations via supported private or managed-network egress controls.
  3. Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.
  4. Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.
  5. Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.

Explanation

Correct Answers

C:

Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity. This targets foundry private endpoint dns resolves to public ip. Private network security requires both endpoint approval and correct DNS resolution; a private endpoint creation event does not change every client's name resolution. Verify the failure through: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. Validate success with: Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An enterprise disables….

D:

Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. This is the most relevant evidence for foundry private endpoint dns resolves to public ip. Private network security requires both endpoint approval and correct DNS resolution; a private endpoint creation event does not change every client's name resolution. The matching controlled remediation is: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An enterprise disables….

Incorrect Answers

A:

Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics. This is associated with prompt a/b test uses different model versions in each arm, not the essential evidence-and-fix pair for foundry private endpoint dns resolves to public ip. First examine: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. Then correct: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

B:

Permit only the required documented tool and service destinations via supported private or managed-network egress controls. This is associated with agent tool calls fail behind overbroad outbound block, not the essential evidence-and-fix pair for foundry private endpoint dns resolves to public ip. First examine: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. Then correct: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

E:

Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This is associated with network allowlist exposes production model endpoint to test subnet, not the essential evidence-and-fix pair for foundry private endpoint dns resolves to public ip. First examine: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. Then correct: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

Question 183

While preparing a secure Foundry model or agent release, the following condition occurs: A high-volume assistant deployment repeatedly hits throughput saturation during business-hour spikes because its provisioned throughput units were selected from average rather than peak token load. 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. Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
  2. Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.
  3. Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials.
  4. Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

Explanation

Correct Answer

B:

Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits. This targets provisioned throughput capacity insufficient at peak traffic. Provisioned model throughput constrains admitted tokens and request demand; average daily request counts cannot establish a safe peak capacity allocation. Verify the failure through: Inspect input/output token volume, peak concurrent requests, provisioned throughput allocation, throttling codes and deployment latency percentiles. Validate success with: Peak requests meet approved latency and throttling targets under a representative load test while capacity costs remain documented.

Incorrect Answers

A:

Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This could address few-shot prompt examples bias outputs toward one subgroup, but it does not solve the specified provisioned throughput capacity insufficient at peak traffic failure. The matching remediation is: Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.

C:

Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials. This could address serverless model endpoint unavailable to chosen identity, but it does not solve the specified provisioned throughput capacity insufficient at peak traffic failure. The matching remediation is: Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.

D:

Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step. This could address vision input sent to text-only foundation model, but it does not solve the specified provisioned throughput capacity insufficient at peak traffic failure. The matching remediation is: Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.

Question 184

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A withdrawn credit-risk model is marked deprecated in a wiki but remains exposed as an active registry version and continues to be selected by automated deployment tools. The operator must safeguard training reproducibility and serving continuity. Which acceptance test shows the AI operations defect is corrected?

  1. Historical inference replay uses only features available before prediction time and realistic performance survives evaluation.
  2. New deployment workflows cannot select the retired version while required historic audit artifacts remain available.
  3. All workers join one process group and finish a representative multi-node training step without broad public inbound exposure.
  4. Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria.

Explanation

Correct Answer

B:

New deployment workflows cannot select the retired version while required historic audit artifacts remain available. Model lifecycle management must reflect state in the model registry and deployment references, not just informal documentation. a direct corrective action is to archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.

Incorrect Answers

A:

Historical inference replay uses only features available before prediction time and realistic performance survives evaluation. That addresses a different configuration issue rather than the main requirement. Verify instead: New deployment workflows cannot select the retired version while required historic audit artifacts remain available.

C:

All workers join one process group and finish a representative multi-node training step without broad public inbound exposure. That addresses a different configuration issue rather than the main requirement. Verify instead: New deployment workflows cannot select the retired version while required historic audit artifacts remain available.

D:

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: New deployment workflows cannot select the retired version while required historic audit artifacts remain available.

Question 185

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML sweep job ranks candidate forecasting models by validation loss although the operational requirement is minimum mean absolute error, causing a poorer business model to win. The operator must safeguard training reproducibility and serving continuity. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
  2. Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
  3. Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.
  4. Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal.

Explanation

Correct Answer

D:

Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal. This targets hyperparameter sweep minimizes the wrong objective. Hyperparameter sweep selection depends on the configured primary metric and goal, not an implicit interpretation of business success. Verify the failure through: Examine sweep primary_metric, goal direction, logged metric names, candidate ranking and the held-out evaluation calculation. Validate success with: The winning child run has the best intended validation metric among eligible candidates and is reevaluated on unseen holdout data.

Incorrect Answers

A:

Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This could address rollback cannot recover a previous environment version, but it does not solve the specified hyperparameter sweep minimizes the wrong objective failure. The matching remediation is: Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal.

B:

Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature. This could address autologging excludes required model artifact, but it does not solve the specified hyperparameter sweep minimizes the wrong objective failure. The matching remediation is: Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal.

C:

Bind training input directly to the feature component's typed output to establish the correct pipeline dependency. This could address pipeline graph omits feature-build dependency, but it does not solve the specified hyperparameter sweep minimizes the wrong objective failure. The matching remediation is: Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal.

Question 186

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A GenAI application releases its Foundry project and calls a model name before that model deployment is created, causing intermittent first-run errors. The deployment must retain governed identities, endpoint contracts and auditable release history. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.
  2. Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
  3. Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.
  4. Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.

Explanation

Correct Answer

B:

Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This targets foundry bicep rollout omits model deployment dependencies. Infrastructure-as-code can provision the platform consistently only when dependencies and deployment readiness are managed explicitly. Verify the failure through: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. Validate success with: Repeatable IaC releases create the expected project and model deployment before starting inference smoke tests.

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 foundry bicep rollout omits model deployment dependencies failure. The matching remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.

C:

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 bicep rollout omits model deployment dependencies failure. The matching remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.

D:

Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review. This could address prompt repository references secret customer examples, but it does not solve the specified foundry bicep rollout omits model deployment dependencies failure. The matching remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.

Question 187

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A model is trained across four GPU workers but all workers ingest the same unsharded dataset in each epoch, wasting resources and biasing effective training statistics. The operator must safeguard training reproducibility and serving continuity. Which targeted Azure AI operations change best addresses the documented problem?

  1. Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.
  2. Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
  3. Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal.
  4. Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

Explanation

Correct Answer

D:

Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation. This targets distributed training uses one shard for every worker. Data-parallel training must coordinate sampling and gradient aggregation; launching multiple processes does not automatically shard training data. Verify the failure through: Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. Validate success with: Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.

Incorrect Answers

A:

Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers. This could address model evaluation exposes sensitive examples in explainability report, but it does not solve the specified distributed training uses one shard for every worker failure. The matching remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

B:

Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs. This could address exploration notebook reads production data without reproducible snapshot, but it does not solve the specified distributed training uses one shard for every worker failure. The matching remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

C:

Configure the sweep to optimize the explicitly logged business-aligned metric with the correct minimize/maximize goal. This could address hyperparameter sweep minimizes the wrong objective, but it does not solve the specified distributed training uses one shard for every worker failure. The matching remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

Question 188

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: Two Azure ML training runs produce different validation scores but the team cannot determine whether learning rate or data version changed because the Python scripts log only final accuracy. The operator must safeguard training reproducibility and serving continuity. Which observable postchange result proves the intended remediation succeeded?

  1. Reports distinguish provisional drift/latency signals from later evidence-based accuracy and recall.
  2. The feature job completes before training consumes its versioned output in repeated orchestrated executions.
  3. A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand.
  4. Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported.

Explanation

Correct Answer

C:

A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand. MLflow experiment tracking associates metadata with run IDs, but unlogged hyperparameters and datasets cannot be recovered reliably from a final metric alone. a direct corrective action is to add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment.

Incorrect Answers

A:

Reports distinguish provisional drift/latency signals from later evidence-based accuracy and recall. That addresses a different configuration issue rather than the main requirement. Verify instead: A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand.

B:

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 reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand.

D:

Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported. That addresses a different configuration issue rather than the main requirement. Verify instead: A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand.

Question 189

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional GPU-family vCPU quota than the subscription currently has. The team must preserve approved access, model provenance and private network constraints. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability.
  2. Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
  3. Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
  4. Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.
  5. Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.

Explanation

Correct Answers

A:

Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. This is the most relevant evidence for compute cluster cannot allocate requested gpu quota. Azure ML computes draw from Azure regional VM family quota; declaring a cluster does not reserve unlimited GPU instances. The matching controlled remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This matters here because a distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional….

B:

Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This targets compute cluster cannot allocate requested gpu quota. Azure ML computes draw from Azure regional VM family quota; declaring a cluster does not reserve unlimited GPU instances. Verify the failure through: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. Validate success with: The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement. This matters here because a distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional….

Incorrect Answers

C:

Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate. This is associated with github deployment pipeline omits secure environment approvals, not the essential evidence-and-fix pair for compute cluster cannot allocate requested gpu quota. First examine: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. Then correct: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This matters here because a distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional….

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 compute cluster cannot allocate requested gpu quota. First examine: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. Then correct: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.

E:

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 compute cluster cannot allocate requested gpu quota. First examine: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. Then correct: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.

Question 190

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A churn model is registered and deployed, but online inference uses different feature lookup keys from training because the model artifact lacks the feature retrieval specification. The resolution must preserve quality gates, documented artifacts and rollback options. Which investigation best verifies the cause before changing production configuration?

  1. Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.
  2. Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
  3. Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
  4. Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.

Explanation

Correct Answer

D:

Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training. This is the most relevant evidence for feature retrieval specification missing from registered model. Model weights alone do not specify how feature values were retrieved; production consistency requires a versioned feature contract. The matching controlled remediation is: Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time.

Incorrect Answers

A:

Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. This would investigate accuracy monitoring lacks delayed outcome labels rather than the documented feature retrieval specification missing from registered model issue. The relevant investigation is: Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.

B:

Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This would investigate retired model kept active as discoverable deployment candidate rather than the documented feature retrieval specification missing from registered model issue. The relevant investigation is: Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.

C:

Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. This would investigate model registry latest alias points to unapproved experiment rather than the documented feature retrieval specification missing from registered model issue. The relevant investigation is: Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.

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