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 10

Question 90

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

  1. Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.
  2. Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials.
  3. Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
  4. Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

Explanation

Correct Answer

D:

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:

Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review. This could address provisioned deployment pays for idle unused capacity, but it does not solve the specified vision input sent to text-only foundation model failure. The matching remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

B:

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 vision input sent to text-only foundation model failure. The matching remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

C:

Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This could address prompt variant comparison measures fluency not task success, but it does not solve the specified vision input sent to text-only foundation model failure. The matching remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

Question 91

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A Bicep deployment provisions an Azure ML workspace but its associated storage, Key Vault and private endpoints are created after the workspace references them, producing intermittent deployment failures. The team must preserve approved access, model provenance and private network constraints. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
  2. Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
  3. Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
  4. Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.

Explanation

Correct Answer

C:

Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment. This targets bicep workspace declaration misses dependent private resources. Declarative infrastructure still requires a valid resource dependency graph and stable networking prerequisites; syntax validation alone does not enforce desired provisioning order. Verify the failure through: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. Validate success with: Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access.

Incorrect Answers

A:

Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow. This could address github action uses persistent azure client secret, but it does not solve the specified bicep workspace declaration misses dependent private resources failure. The matching remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

B:

Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules. This could address oidc subject filter trusts unreviewed pull-request branches, but it does not solve the specified bicep workspace declaration misses dependent private resources failure. The matching remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

D:

Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This could address mltable data asset schema mismatches training code, but it does not solve the specified bicep workspace declaration misses dependent private resources failure. The matching remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

Question 92

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML training pipeline intermittently starts training before its feature-engineering output is ready because the training component references a static path instead of the upstream component's declared output. 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 Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
  2. Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.
  3. Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
  4. Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.
  5. Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.

Explanation

Correct Answers

B:

Bind training input directly to the feature component's typed output to establish the correct pipeline dependency. This targets pipeline graph omits feature-build dependency. Component dependency edges in Azure ML are determined by declared data bindings, not by visual position in a notebook or YAML file. Verify the failure through: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. Validate success with: The feature job completes before training consumes its versioned output in repeated orchestrated executions.

E:

Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. This is the most relevant evidence for pipeline graph omits feature-build dependency. Component dependency edges in Azure ML are determined by declared data bindings, not by visual position in a notebook or YAML file. The matching controlled remediation is: Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.

Incorrect Answers

A:

Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes. This is associated with training script ignores reproducible seed and input contract, not the essential evidence-and-fix pair for pipeline graph omits feature-build dependency. First examine: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. Then correct: Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.

C:

Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training. This is associated with automl primary metric does not match rare-event goal, not the essential evidence-and-fix pair for pipeline graph omits feature-build dependency. First examine: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. Then correct: Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.

D:

Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates. This is associated with canary rollout sends all traffic to unvalidated candidate, not the essential evidence-and-fix pair for pipeline graph omits feature-build dependency. First examine: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. Then correct: Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.

Question 93

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training component references an image in a private Azure Container Registry but the job's identity lacks image pull privileges, so workers fail before Python starts. The change must remain limited to authorized workspaces and avoid unreviewed production impact. 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. Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error.
  3. Give the approved compute or workspace identity the necessary ACR pull access and use a validated immutable image reference.
  4. Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events.
  5. Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.

Explanation

Correct Answers

C:

Give the approved compute or workspace identity the necessary ACR pull access and use a validated immutable image reference. This targets docker environment image cannot pull from private registry. Container image pulls are authorized independently of Azure ML job submission; model training cannot start if its execution image cannot be obtained. Verify the failure through: Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. Validate success with: Compute nodes pull the exact authorized image and run the component without granting registry push permissions.

D:

Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. This is the most relevant evidence for docker environment image cannot pull from private registry. Container image pulls are authorized independently of Azure ML job submission; model training cannot start if its execution image cannot be obtained. The matching controlled remediation is: Give the approved compute or workspace identity the necessary ACR pull access and use a validated immutable image reference.

Incorrect Answers

A:

Require protected pull requests and automated component tests before changes to production training code are merged. This is associated with notebook merge bypasses protected evaluation tests, not the essential evidence-and-fix pair for docker environment image cannot pull from private registry. First examine: Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. Then correct: Give the approved compute or workspace identity the necessary ACR pull access and use a validated immutable image reference.

B:

Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error. This is associated with pipeline component output type mismatches consumer, not the essential evidence-and-fix pair for docker environment image cannot pull from private registry. First examine: Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. Then correct: Give the approved compute or workspace identity the necessary ACR pull access and use a validated immutable image reference.

E:

Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This is associated with mltable data asset schema mismatches training code, not the essential evidence-and-fix pair for docker environment image cannot pull from private registry. First examine: Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. Then correct: Give the approved compute or workspace identity the necessary ACR pull access and use a validated immutable image reference.

Question 94

As an MLOps engineer reviews a model training or inference pipeline, 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 resolution must preserve quality gates, documented artifacts and rollback options. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.
  2. Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness.
  3. Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.
  4. Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
  5. Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.

Explanation

Correct Answers

A:

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.

B:

Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. This is the most relevant evidence for 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. The matching controlled remediation is: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

Incorrect Answers

C:

Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed. This is associated with incident rollback artifact was deleted instead of archived, not the essential evidence-and-fix pair for responsible ai evaluation omits demographic cohort slices. First examine: Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. Then correct: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

D:

Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. This is associated with model registry latest alias points to unapproved experiment, not the essential evidence-and-fix pair for responsible ai evaluation omits demographic cohort slices. First examine: Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. Then correct: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

E:

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 responsible ai evaluation omits demographic cohort slices. First examine: Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. Then correct: Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.

Question 95

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A managed online deployment repeatedly restarts because its startup script throws a missing-file exception before the liveness probe can succeed. The operator must safeguard training reproducibility and serving continuity. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests.
  2. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
  3. Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
  4. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

Explanation

Correct Answer

D:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This targets endpoint deployment health probe fails before model initialization. Successful model registration does not guarantee scoring container initialization; startup dependencies must be validated in deployed environment. Verify the failure through: Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. Validate success with: Deployment reaches healthy readiness and handles a representative test request without restart loops.

Incorrect Answers

A:

Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests. This could address endpoint scoring script expects wrong json schema, but it does not solve the specified endpoint deployment health probe fails before model initialization failure. The matching remediation is: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

B:

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 endpoint deployment health probe fails before model initialization failure. The matching remediation is: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

C:

Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This could address mlflow tracking uri sends notebook runs to wrong workspace, but it does not solve the specified endpoint deployment health probe fails before model initialization failure. The matching remediation is: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

Question 96

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A Foundry agent invokes its LLM successfully but receives access denied when querying an Azure AI Search index because the assigned managed identity lacks search data reader rights. The deployment must retain governed identities, endpoint contracts and auditable release history. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Inspect endpoint authentication modes, deployment authorization, production managed identity, assigned roles and failed token exchanges.
  2. Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests.
  3. Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.
  4. Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.

Explanation

Correct Answer

B:

Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests. This is the most relevant evidence for agent runtime managed identity cannot read retrieval data. Foundry model access and Azure AI Search data-plane authorization are separate permission boundaries for a retrieval-augmented agent. The matching controlled remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.

Incorrect Answers

A:

Inspect endpoint authentication modes, deployment authorization, production managed identity, assigned roles and failed token exchanges. This would investigate serverless model endpoint unavailable to chosen identity rather than the documented agent runtime managed identity cannot read retrieval data issue. The relevant investigation is: Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests.

C:

Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs. This would investigate foundry environment mixes development and production agent resources rather than the documented agent runtime managed identity cannot read retrieval data issue. The relevant investigation is: Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests.

D:

Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This would investigate network allowlist exposes production model endpoint to test subnet rather than the documented agent runtime managed identity cannot read retrieval data issue. The relevant investigation is: Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests.

Question 97

While optimizing a production RAG or fine-tuned model service, the following condition occurs: A RAG search index blends keyword and vector results but weights retired versions of a procedure equally with current publications, so old policy text appears first. The resulting model must meet held-out quality and security criteria. Which investigation best verifies the cause before changing production configuration?

  1. Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior.
  2. Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall.
  3. Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents.
  4. Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.

Explanation

Correct Answer

D:

Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata. This is the most relevant evidence for hybrid retrieval double-counts outdated documents. Hybrid scoring does not inherently enforce document freshness or authoritative version; metadata filtering is a separate ranking control. The matching controlled remediation is: Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.

Incorrect Answers

A:

Inspect fine-tuning records, role/message formatting, target response schemas, label consistency and curated holdout behavior. This would investigate supervised fine-tuning dataset includes conflicting assistant behaviors rather than the documented hybrid retrieval double-counts outdated documents issue. The relevant investigation is: Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.

B:

Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. This would investigate rag similarity threshold filters all relevant evidence rather than the documented hybrid retrieval double-counts outdated documents issue. The relevant investigation is: Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.

C:

Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents. This would investigate rag a/b experiment judges only click-through not factuality rather than the documented hybrid retrieval double-counts outdated documents issue. The relevant investigation is: Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.

Question 98

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML production model serves predictions, but the operator reports daily accuracy without any actual outcome labels arriving until several weeks later. The operator must safeguard training reproducibility and serving continuity. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.
  2. Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
  3. Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics.
  4. Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests.
  5. Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds.

Explanation

Correct Answers

A:

Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join. This targets accuracy monitoring lacks delayed outcome labels. Model performance against ground truth cannot be measured correctly before outcomes are known; operational health signals are not substitutes for labeled accuracy. Verify the failure through: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. Validate success with: Reports distinguish provisional drift/latency signals from later evidence-based accuracy and recall.

C:

Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. This is the most relevant evidence for accuracy monitoring lacks delayed outcome labels. Model performance against ground truth cannot be measured correctly before outcomes are known; operational health signals are not substitutes for labeled accuracy. The matching controlled remediation is: Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

Incorrect Answers

B:

Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts. This is associated with endpoint latency average conceals tail degradation, not the essential evidence-and-fix pair for accuracy monitoring lacks delayed outcome labels. First examine: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. Then correct: Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

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 accuracy monitoring lacks delayed outcome labels. First examine: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. Then correct: Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

E:

Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds. This is associated with data drift monitor uses wrong reference season, not the essential evidence-and-fix pair for accuracy monitoring lacks delayed outcome labels. First examine: Inspect prediction and ground-truth join keys, label availability delay, inference logging and published monitoring metrics. Then correct: Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

Question 99

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A repeated model-training command yields unpredictably different evaluation results because its random seed and dataset split are not fixed or logged across Azure ML runs. 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 tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job.
  2. Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
  3. Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs.
  4. Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.

Explanation

Correct Answer

B:

Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes. This is the most relevant evidence for training script ignores reproducible seed and input contract. ML model reproducibility depends on data, environment and randomness control; a single identical command string does not fix every stochastic dependency. The matching controlled remediation is: Implement feasible deterministic seeding and record input data split and environment versions for each run with acknowledged nondeterministic GPU constraints. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A repeated….

Incorrect Answers

A:

Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job. This would investigate mlflow experiment logs omit run parameters rather than the documented training script ignores reproducible seed and input contract issue. The relevant investigation is: Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.

C:

Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. This would investigate autologging excludes required model artifact rather than the documented training script ignores reproducible seed and input contract issue. The relevant investigation is: Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.

D:

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 training script ignores reproducible seed and input contract issue. The relevant investigation is: Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.

Question 100

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A Bicep deployment provisions an Azure ML workspace but its associated storage, Key Vault and private endpoints are created after the workspace references them, producing intermittent deployment failures. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
  2. Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
  3. Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
  4. Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
  5. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.

Explanation

Correct Answers

A:

Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment. This targets bicep workspace declaration misses dependent private resources. Declarative infrastructure still requires a valid resource dependency graph and stable networking prerequisites; syntax validation alone does not enforce desired provisioning order. Verify the failure through: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. Validate success with: Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access.

C:

Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. This is the most relevant evidence for bicep workspace declaration misses dependent private resources. Declarative infrastructure still requires a valid resource dependency graph and stable networking prerequisites; syntax validation alone does not enforce desired provisioning order. The matching controlled remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

Incorrect Answers

B:

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 bicep workspace declaration misses dependent private resources. First examine: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. Then correct: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

D:

Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment. This is associated with training environment lacks pinned package versions, not the essential evidence-and-fix pair for bicep workspace declaration misses dependent private resources. First examine: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. Then correct: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

E:

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 bicep workspace declaration misses dependent private resources. First examine: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. Then correct: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

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