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 67

Question 660

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is rolled back to old weights but its scoring container still uses the new incompatible environment, so production errors continue after rollback. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest.
  2. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
  3. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.
  4. Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern.
  5. Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.

Explanation

Correct Answers

A:

Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. This is the most relevant evidence for rollback cannot recover a previous environment version. A deployment's behavior depends on the whole inference package; changing model weights alone cannot undo incompatible runtime changes. The matching controlled remediation is: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….

B:

Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This targets rollback cannot recover a previous environment version. A deployment's behavior depends on the whole inference package; changing model weights alone cannot undo incompatible runtime changes. Verify the failure through: Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. Validate success with: A representative rollback test restores known-good predictions and endpoint health within the recovery target. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….

Incorrect Answers

C:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This is associated with endpoint deployment health probe fails before model initialization, not the essential evidence-and-fix pair for rollback cannot recover a previous environment version. First examine: Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. Then correct: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.

D:

Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. This is associated with online scoring requirement deployed as batch endpoint, not the essential evidence-and-fix pair for rollback cannot recover a previous environment version. First examine: Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. Then correct: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.

E:

Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs. This is associated with exploration notebook reads production data without reproducible snapshot, not the essential evidence-and-fix pair for rollback cannot recover a previous environment version. First examine: Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. Then correct: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….

Question 661

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 acceptance test shows the AI operations defect is corrected?

  1. Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
  2. Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail.
  3. A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.
  4. The promotion report presents comparable metrics with documented confidence and class distribution before model approval.

Explanation

Correct Answer

C:

A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. Azure ML online endpoints support synchronous prediction while batch endpoints are designed for asynchronous high-volume jobs. a direct corrective action is to deploy the approved model through a suitable managed online endpoint and provision capacity for synchronous requests.

Incorrect Answers

A:

Overnight processing completes within its processing window and interactive endpoint latency remains within SLA. That addresses a different configuration issue rather than the main requirement. Verify instead: A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.

B:

Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail. That addresses a different configuration issue rather than the main requirement. Verify instead: A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.

D:

The promotion report presents comparable metrics with documented confidence and class distribution before model approval. That addresses a different configuration issue rather than the main requirement. Verify instead: A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.

Question 662

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled Azure ML retraining job always updates the online endpoint even when new validation recall is worse than the currently approved model. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
  2. Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes.
  3. Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.
  4. Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records.
  5. Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.

Explanation

Correct Answers

C:

Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate. This targets retraining pipeline deploys without model quality gate. Automation of model retraining should not imply automatic unconditional promotion; evaluation gates are essential to safe model operations. Verify the failure through: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. Validate success with: A poor candidate is retained for review without reaching production, and qualifying candidates progress through controlled canary rollout. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled….

D:

Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. This is the most relevant evidence for retraining pipeline deploys without model quality gate. Automation of model retraining should not imply automatic unconditional promotion; evaluation gates are essential to safe model operations. The matching controlled remediation is: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A scheduled….

Incorrect Answers

A:

Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This is associated with rollback cannot recover a previous environment version, not the essential evidence-and-fix pair for retraining pipeline deploys without model quality gate. First examine: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. Then correct: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.

B:

Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. This is associated with data drift monitor uses wrong reference season, not the essential evidence-and-fix pair for retraining pipeline deploys without model quality gate. First examine: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. Then correct: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.

E:

Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This is associated with missing feature values escape input drift checks, not the essential evidence-and-fix pair for retraining pipeline deploys without model quality gate. First examine: Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. Then correct: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.

Question 663

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A scheduled Azure ML pipeline appears fast but returns last week's encoded features because a preprocessing component is reused under inputs that do not capture the changed transformation configuration. The operator must safeguard training reproducibility and serving continuity. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds.
  2. Bind training input directly to the feature component's typed output to establish the correct pipeline dependency.
  3. Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.
  4. Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

Explanation

Correct Answer

D:

Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed. This targets pipeline cache reuses stale transform artifact. Pipeline reuse is correct only when the declared inputs and environment represent all behaviorally relevant computation dependencies. Verify the failure through: Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. Validate success with: A rerun executes the revised transform and its output lineage identifies the current code and dataset rather than a stale cached job.

Incorrect Answers

A:

Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds. This could address data drift monitor uses wrong reference season, but it does not solve the specified pipeline cache reuses stale transform artifact failure. The matching remediation is: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

B:

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 pipeline cache reuses stale transform artifact failure. The matching remediation is: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

C:

Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds. This could address run comparison uses incompatible validation populations, but it does not solve the specified pipeline cache reuses stale transform artifact failure. The matching remediation is: Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.

Question 664

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A model platform pipeline applies Bicep changes immediately and breaks a production workspace because it never checks syntax, resource drift or the expected scope. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which acceptance test shows the AI operations defect is corrected?

  1. Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access.
  2. Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review.
  3. Authorized registry models load in the isolated environment and unrelated external destinations remain blocked.
  4. The job consumes the intended dataset version and staging files are not silently mixed into production runs.

Explanation

Correct Answer

B:

Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review. Infrastructure automation should detect configuration drift and unexpected destructive changes before a production deployment proceeds. a direct corrective action is to add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A model platform….

Incorrect Answers

A:

Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access. That addresses a different configuration issue rather than the main requirement. Verify instead: Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review.

C:

Authorized registry models load in the isolated environment and unrelated external destinations remain blocked. That addresses a different configuration issue rather than the main requirement. Verify instead: Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A model platform….

D:

The job consumes the intended dataset version and staging files are not silently mixed into production runs. That addresses a different configuration issue rather than the main requirement. Verify instead: Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review.

Question 665

While optimizing a production RAG or fine-tuned model service, the following condition occurs: A CI pipeline immediately swaps a production fine-tuned model for each completed experiment without validating cost, quality and deployment compatibility. The resulting model must meet held-out quality and security criteria. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.
  2. Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
  3. Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking.
  4. Examine fine-tuning run outputs, model registry versions, promotion approvals, held-out evaluations and rollout routing settings.
  5. Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow.

Explanation

Correct Answers

A:

Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions. This targets fine-tuned candidate bypasses promotion review after training. Training completion is a research milestone, not authorization for production; fine-tuned releases need controlled model registration, approval and rollout. Verify the failure through: Examine fine-tuning run outputs, model registry versions, promotion approvals, held-out evaluations and rollout routing settings. Validate success with: A bad candidate remains isolated while an approved model reaches production with known-good rollback and auditable comparison results. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A CI pipeline….

D:

Examine fine-tuning run outputs, model registry versions, promotion approvals, held-out evaluations and rollout routing settings. This is the most relevant evidence for fine-tuned candidate bypasses promotion review after training. Training completion is a research milestone, not authorization for production; fine-tuned releases need controlled model registration, approval and rollout. The matching controlled remediation is: Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: A CI pipeline….

Incorrect Answers

B:

Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This is associated with fine-tune production endpoint references deleted training artifact, not the essential evidence-and-fix pair for fine-tuned candidate bypasses promotion review after training. First examine: Examine fine-tuning run outputs, model registry versions, promotion approvals, held-out evaluations and rollout routing settings. Then correct: Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.

C:

Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking. This is associated with pure vector search misses exact regulatory clause codes, not the essential evidence-and-fix pair for fine-tuned candidate bypasses promotion review after training. First examine: Examine fine-tuning run outputs, model registry versions, promotion approvals, held-out evaluations and rollout routing settings. Then correct: Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.

E:

Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. This is associated with fine-tuning task selected when retrieval would better handle changing facts, not the essential evidence-and-fix pair for fine-tuned candidate bypasses promotion review after training. First examine: Examine fine-tuning run outputs, model registry versions, promotion approvals, held-out evaluations and rollout routing settings. Then correct: Register fine-tuned candidates as versioned artifacts, enforce evaluation and security gates, then canary only approved versions.

Question 666

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A platform team deletes the previously approved model after a new deployment, then cannot restore service when the new model fails canary checks. The operator must safeguard training reproducibility and serving continuity. Which targeted Azure AI operations change best addresses the documented problem?

  1. Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.
  2. Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time.
  3. Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.
  4. Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.

Explanation

Correct Answer

A:

Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed. This targets incident rollback artifact was deleted instead of archived. Archiving and retention support model provenance and rollback; immediate deletion of the only stable model makes a deployment irreversible. Verify the failure through: Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. Validate success with: A failed canary can restore the last approved model version without retraining or inventing replacement artifacts.

Incorrect Answers

B:

Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time. This could address feature retrieval specification missing from registered model, but it does not solve the specified incident rollback artifact was deleted instead of archived failure. The matching remediation is: Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.

C:

Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This could address automated ml experiment uses leakage feature, but it does not solve the specified incident rollback artifact was deleted instead of archived failure. The matching remediation is: Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.

D:

Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates. This could address model registry latest alias points to unapproved experiment, but it does not solve the specified incident rollback artifact was deleted instead of archived failure. The matching remediation is: Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.

Question 667

During a Foundry generative AI quality and observability incident, the following condition occurs: A retrieval assistant's monthly bill grows, but its cost dashboard counts only chat completion tokens and omits repeated query and document embedding operations. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.
  2. Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
  3. Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.
  4. Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.

Explanation

Correct Answer

A:

Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend. This targets token cost report omits embedding requests. GenAI cost analysis must include all model and supporting resources; tracking only final generation underestimates retrieval and indexing spend. Verify the failure through: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags. Validate success with: The report reconciles billed service usage with per-feature consumption and unnecessary repeat embedding calls decline.

Incorrect Answers

B:

Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This could address custom evaluator silently changes its scoring rubric, but it does not solve the specified token cost report omits embedding requests failure. The matching remediation is: Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.

C:

Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers. This could address agent traces omit downstream tool failure reason, but it does not solve the specified token cost report omits embedding requests failure. The matching remediation is: Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.

D:

Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand. This could address genai throughput report mixes responses and tokens, but it does not solve the specified token cost report omits embedding requests failure. The matching remediation is: Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.

Question 668

While preparing a secure Foundry model or agent release, the following condition occurs: A prototype assistant runs only a few tests per day but reserves a large provisioned-throughput deployment, creating a high recurring bill even when no requests arrive. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which targeted Azure AI operations change best addresses the documented problem?

  1. Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
  2. Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.
  3. Build and test a compatible version-pinned serving environment and promote the corrected managed model deployment.
  4. Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.

Explanation

Correct Answer

B:

Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review. This targets provisioned deployment pays for idle unused capacity. Provisioned throughput may be billed for allocated capacity independent of actual use; deployment type should match utilization patterns. Verify the failure through: Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load. Validate success with: The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.

Incorrect Answers

A:

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 deployment pays for idle unused capacity failure. The matching remediation is: Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.

C:

Build and test a compatible version-pinned serving environment and promote the corrected managed model deployment. This could address managed foundation model deployment lacks compatible runtime image, but it does not solve the specified provisioned deployment pays for idle unused capacity failure. The matching remediation is: Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.

D:

Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This could address agent runtime managed identity cannot read retrieval data, but it does not solve the specified provisioned deployment pays for idle unused capacity failure. The matching remediation is: Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.

Question 669

While preparing a secure Foundry model or agent release, the following condition occurs: A GenAI team commits real customer tickets containing identifiers as few-shot prompt examples in a shared Git repository, exposing data beyond the approved processing boundary. 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. Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.
  2. Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.
  3. Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
  4. Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

Explanation

Correct Answer

A:

Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review. This targets prompt repository references secret customer examples. Source control is not an appropriate unreviewed store for sensitive customer data; prompt versioning requires privacy-preserving examples and access governance. Verify the failure through: Inspect prompt repository history, example dataset provenance, PII classification, branch access controls and affected downstream forks. Validate success with: Prompt tests retain representative behavior without exposing customer identities in accessible Git history or future deployments.

Incorrect Answers

B:

Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling. This could address prompt includes untrusted retrieved instructions as system policy, but it does not solve the specified prompt repository references secret customer examples failure. The matching remediation is: Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.

C:

Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This could address prompt variant comparison measures fluency not task success, but it does not solve the specified prompt repository references secret customer examples failure. The matching remediation is: Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.

D:

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 prompt repository references secret customer examples failure. The matching remediation is: Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.

Question 670

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline component is published for reuse but includes a hard-coded workspace datastore URI, causing executions in a second workspace to read an unavailable path. 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. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.
  2. Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error.
  3. Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
  4. Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.

Explanation

Correct Answer

D:

Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations. This is the most relevant evidence for reusable component hardcodes workspace-specific asset path. Portable Azure ML components describe computation and typed interfaces rather than assuming a single workspace's storage layout. The matching controlled remediation is: Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline….

Incorrect Answers

A:

Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This would investigate iac workflow lacks repeatable infrastructure validation rather than the documented reusable component hardcodes workspace-specific asset path issue. The relevant investigation is: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.

B:

Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error. This would investigate pipeline component output type mismatches consumer rather than the documented reusable component hardcodes workspace-specific asset path issue. The relevant investigation is: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline….

C:

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 reusable component hardcodes workspace-specific asset path issue. The relevant investigation is: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.

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