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 37

Question 360

While preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application shares one Foundry project and keys between development and production, so test deployments can overwrite production agent configuration. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which observable postchange result proves the intended remediation succeeded?

  1. The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls.
  2. A test prompt or model deployment change affects only the development environment until an approved promotion occurs.
  3. Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
  4. The managed identity invokes the approved endpoint and a revoked developer key is no longer needed for production inference.

Explanation

Correct Answer

B:

A test prompt or model deployment change affects only the development environment until an approved promotion occurs. AI application environments need isolation across model deployment configuration, identity and release workflow, not just different branch names. a direct corrective action is to separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

Incorrect Answers

A:

The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls. That addresses a different configuration issue rather than the main requirement. Verify instead: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

C:

Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied. That addresses a different configuration issue rather than the main requirement. Verify instead: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

D:

The managed identity invokes the approved endpoint and a revoked developer key is no longer needed for production inference. That addresses a different configuration issue rather than the main requirement. Verify instead: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

Question 361

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new Azure ML workspace starts but managed training cannot retrieve approved secrets because deployment references a Key Vault belonging to an unrelated project. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.
  2. Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
  3. Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.
  4. Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

Explanation

Correct Answer

D:

Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file. This is the most relevant evidence for workspace dependencies point to unrelated secrets vault. A workspace can exist while supporting Key Vault, storage or monitoring dependencies are incorrectly associated; successful resource creation alone is not end-to-end readiness. The matching controlled remediation is: Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration.

Incorrect Answers

A:

Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. This would investigate interactive compute instances remain running while unused rather than the documented workspace dependencies point to unrelated secrets vault issue. The relevant investigation is: Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

B:

Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. This would investigate versionless dataset reference breaks reproducibility rather than the documented workspace dependencies point to unrelated secrets vault issue. The relevant investigation is: Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

C:

Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments. This would investigate datastore authentication relies on expiring account key rather than the documented workspace dependencies point to unrelated secrets vault issue. The relevant investigation is: Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.

Question 362

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A chat assistant must return low-latency answers but the team selects an offline batch inference architecture that produces responses only after a scheduled job completes. The deployment must retain governed identities, endpoint contracts and auditable release history. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
  2. Route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass.
  3. Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
  4. Define a versioned structured response instruction and supported JSON schema contract with parser-based validation.

Explanation

Correct Answer

C:

Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests. This targets interactive inference deployed on unsuitable batch-style compute. Generative chat workloads ordinarily require online serving semantics; scheduled batch compute cannot satisfy an interactive response deadline. Verify the failure through: Check application response SLA, workload concurrency, chosen Foundry model endpoint type and current request queuing behavior. Validate success with: Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.

Incorrect Answers

A:

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 interactive inference deployed on unsuitable batch-style compute failure. The matching remediation is: Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.

B:

Route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass. This could address new foundation model replaces production without canary, but it does not solve the specified interactive inference deployed on unsuitable batch-style compute failure. The matching remediation is: Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.

D:

Define a versioned structured response instruction and supported JSON schema contract with parser-based validation. This could address prompt omits explicit structured answer schema, but it does not solve the specified interactive inference deployed on unsuitable batch-style compute failure. The matching remediation is: Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.

Question 363

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A support bot is configured to use the latest model version and starts giving different structured JSON responses after a provider-side model update. The deployment must retain governed identities, endpoint contracts and auditable release history. What measured outcome validates the solution while preserving the stated constraints?

  1. Replaying approved test prompts yields compatible output contracts until the next reviewed version is promoted.
  2. Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
  3. Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
  4. The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.

Explanation

Correct Answer

A:

Replaying approved test prompts yields compatible output contracts until the next reviewed version is promoted. Model version and deployment configuration are production artifacts; unreviewed changes can break prompt, tool and schema compatibility. a direct corrective action is to pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.

Incorrect Answers

B:

Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact. That addresses a different configuration issue rather than the main requirement. Verify instead: Replaying approved test prompts yields compatible output contracts until the next reviewed version is promoted.

C:

Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied. That addresses a different configuration issue rather than the main requirement. Verify instead: Replaying approved test prompts yields compatible output contracts until the next reviewed version is promoted.

D:

The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected. That addresses a different configuration issue rather than the main requirement. Verify instead: Replaying approved test prompts yields compatible output contracts until the next reviewed version is promoted.

Question 364

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A responsible AI dashboard is shared widely with raw personal records and explanations containing identifiers rather than access-controlled aggregate findings. The resolution must preserve quality gates, documented artifacts and rollback options. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback.
  2. Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings.
  3. Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.
  4. Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
  5. Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

Explanation

Correct Answers

B:

Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. This is the most relevant evidence for model evaluation exposes sensitive examples in explainability report. Responsible AI review includes protecting personal data in explanatory artifacts, not only calculating model performance metrics. The matching controlled remediation is: Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.

C:

Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers. This targets model evaluation exposes sensitive examples in explainability report. Responsible AI review includes protecting personal data in explanatory artifacts, not only calculating model performance metrics. Verify the failure through: Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. Validate success with: Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.

Incorrect Answers

A:

Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback. This is associated with mlflow registry artifact cannot load on serving target, not the essential evidence-and-fix pair for model evaluation exposes sensitive examples in explainability report. First examine: Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. Then correct: Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.

D:

Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation. This is associated with distributed training uses one shard for every worker, not the essential evidence-and-fix pair for model evaluation exposes sensitive examples in explainability report. First examine: Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. Then correct: Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.

E:

Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This is associated with responsible ai evaluation omits demographic cohort slices, not the essential evidence-and-fix pair for model evaluation exposes sensitive examples in explainability report. First examine: Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. Then correct: Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.

Question 365

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An engineer promotes the model with the lowest training loss even though the held-out validation loss worsens, indicating overfitting. The operator must safeguard training reproducibility and serving continuity. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.
  2. Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.
  3. Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
  4. Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.

Explanation

Correct Answer

B:

Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold. This targets new candidate chosen from training instead of validation results. A training objective measures fit on observed examples; generalization claims require independent validation and selection rules. Verify the failure through: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. Validate success with: The selected version meets validation criteria without depending on apparent fit to the training examples alone. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An engineer….

Incorrect Answers

A:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This could address endpoint deployment health probe fails before model initialization, but it does not solve the specified new candidate chosen from training instead of validation results failure. The matching remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

C:

Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation. This could address distributed training uses one shard for every worker, but it does not solve the specified new candidate chosen from training instead of validation results failure. The matching remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

D:

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 new candidate chosen from training instead of validation results failure. The matching remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

Question 366

While preparing a secure Foundry model or agent release, the following condition occurs: An agent receives a newly released model under full production traffic before anyone verifies tool calling and safety regressions. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which observable postchange result proves the intended remediation succeeded?

  1. Peak requests meet approved latency and throttling targets under a representative load test while capacity costs remain documented.
  2. Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code.
  3. Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
  4. Quality improves on relevant cohorts without exposing personal information or degrading approved common-case answers.

Explanation

Correct Answer

B:

Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code. Gradual rollout with a known-good model mitigates production blast radius when foundation model behavior changes. a direct corrective action is to route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass.

Incorrect Answers

A:

Peak requests meet approved latency and throttling targets under a representative load test while capacity costs remain documented. That addresses a different configuration issue rather than the main requirement. Verify instead: Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code.

C:

Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact. That addresses a different configuration issue rather than the main requirement. Verify instead: Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code.

D:

Quality improves on relevant cohorts without exposing personal information or degrading approved common-case answers. That addresses a different configuration issue rather than the main requirement. Verify instead: Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code.

Question 367

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An interactive fraud-screening API must respond in under 200 milliseconds, but engineers deploy an Azure ML batch endpoint requiring asynchronous data job submission. The resolution must preserve quality gates, documented artifacts and rollback options. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
  2. Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.
  3. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
  4. Move the approved bulk workload to a managed batch endpoint or batch inference job while preserving online capacity for interactive calls.

Explanation

Correct Answer

B:

Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests. This targets online scoring requirement deployed as batch endpoint. Azure ML online endpoints support synchronous prediction while batch endpoints are designed for asynchronous high-volume jobs. Verify the failure through: Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. Validate success with: A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An interactive….

Incorrect Answers

A:

Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training. This could address automl primary metric does not match rare-event goal, but it does not solve the specified online scoring requirement deployed as batch endpoint failure. The matching remediation is: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

C:

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 online scoring requirement deployed as batch endpoint failure. The matching remediation is: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

D:

Move the approved bulk workload to a managed batch endpoint or batch inference job while preserving online capacity for interactive calls. This could address overnight bulk scoring saturates interactive online endpoint, but it does not solve the specified online scoring requirement deployed as batch endpoint failure. The matching remediation is: Deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

Question 368

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An engineer promotes the model with the lowest training loss even though the held-out validation loss worsens, indicating overfitting. The operator must safeguard training reproducibility and serving continuity. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.
  2. Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
  3. Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry.
  4. Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests.
  5. Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

Explanation

Correct Answers

A:

Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. This is the most relevant evidence for new candidate chosen from training instead of validation results. A training objective measures fit on observed examples; generalization claims require independent validation and selection rules. The matching controlled remediation is: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

E:

Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold. This targets new candidate chosen from training instead of validation results. A training objective measures fit on observed examples; generalization claims require independent validation and selection rules. Verify the failure through: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. Validate success with: The selected version meets validation criteria without depending on apparent fit to the training examples alone.

Incorrect Answers

B:

Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This is associated with mlflow tracking uri sends notebook runs to wrong workspace, not the essential evidence-and-fix pair for new candidate chosen from training instead of validation results. First examine: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. Then correct: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

C:

Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry. This is associated with sweep concurrency overwhelms scarce gpu quota, not the essential evidence-and-fix pair for new candidate chosen from training instead of validation results. First examine: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. Then correct: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

D:

Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests. This is associated with endpoint scoring script expects wrong json schema, not the essential evidence-and-fix pair for new candidate chosen from training instead of validation results. First examine: Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. Then correct: Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.

Question 369

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

  1. Reports distinguish provisional drift/latency signals from later evidence-based accuracy and recall.
  2. Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline.
  3. An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits.
  4. Offline validation and online scoring use equivalent feature definitions and identical customer keys without silent missing-value substitution.

Explanation

Correct Answer

B:

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.

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: Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline.

C:

An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits. 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:

Offline validation and online scoring use equivalent feature definitions and identical customer keys without silent missing-value substitution. 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 370

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A registered MLflow model loads on a developer laptop but fails at Azure ML endpoint startup because its conda dependencies and model signature were not packaged with the artifact. The resolution must preserve quality gates, documented artifacts and rollback options. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback.
  2. Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings.
  3. Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
  4. Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook.

Explanation

Correct Answer

A:

Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback. This is the most relevant evidence for mlflow registry artifact cannot load on serving target. MLflow model registration is not proof of portability; required execution environment and signature must accompany the model artifact. The matching controlled remediation is: Register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A registered….

Incorrect Answers

B:

Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. This would investigate model evaluation exposes sensitive examples in explainability report rather than the documented mlflow registry artifact cannot load on serving target issue. The relevant investigation is: Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A registered….

C:

Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes. This would investigate training script ignores reproducible seed and input contract rather than the documented mlflow registry artifact cannot load on serving target issue. The relevant investigation is: Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback.

D:

Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. This would investigate incident rollback artifact was deleted instead of archived rather than the documented mlflow registry artifact cannot load on serving target issue. The relevant investigation is: Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback.

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