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 75

Question 740

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new managed-network isolated Azure ML workspace can train local models but fails to pull an approved model package from a registry because outbound access was not allowlisted. The change must remain limited to authorized workspaces and avoid unreviewed production impact. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
  2. Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
  3. Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema.
  4. Bind every training job and model registration to a reviewed Git commit SHA and immutable environment/data version in the workflow.

Explanation

Correct Answer

B:

Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This targets aml managed network blocks model registry egress. Workspace network isolation controls package and asset connectivity in addition to private inbound access; approved egress must be explicit. Verify the failure through: Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics. Validate success with: Authorized registry models load in the isolated environment and unrelated external destinations remain blocked. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new….

Incorrect Answers

A:

Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate. This could address github deployment pipeline omits secure environment approvals, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new….

C:

Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema. This could address pipeline component output type mismatches consumer, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.

D:

Bind every training job and model registration to a reviewed Git commit SHA and immutable environment/data version in the workflow. This could address production training script commit cannot be traced, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.

Question 741

During a regulated Azure ML workspace infrastructure review, the following condition occurs: An organization disables public access on Azure ML backing storage, but its private compute subnet cannot resolve the storage account private endpoint and training jobs time out. The team must preserve approved access, model provenance and private network constraints. Which acceptance test shows the AI operations defect is corrected?

  1. Training compute downloads required datasets over private endpoints while public storage access remains disabled.
  2. Automated model registration succeeds while the principal cannot change unrelated networks, secrets or subscriptions.
  3. Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review.
  4. Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test.

Explanation

Correct Answer

A:

Training compute downloads required datasets over private endpoints while public storage access remains disabled. Private endpoints require correct name resolution and route reachability; disabling public access without these dependencies can strand model training workloads. a direct corrective action is to link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This matters here because an organization disables public access on Azure ML backing storage, but its private compute subnet cannot resolve….

Incorrect Answers

B:

Automated model registration succeeds while the principal cannot change unrelated networks, secrets or subscriptions. That addresses a different configuration issue rather than the main requirement. Verify instead: Training compute downloads required datasets over private endpoints while public storage access remains disabled.

C:

Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review. That addresses a different configuration issue rather than the main requirement. Verify instead: Training compute downloads required datasets over private endpoints while public storage access remains disabled.

D:

Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test. That addresses a different configuration issue rather than the main requirement. Verify instead: Training compute downloads required datasets over private endpoints while public storage access remains disabled.

Question 742

During a Foundry generative AI quality and observability incident, the following condition occurs: A service dashboard reports 600 requests per minute and assumes model capacity is sufficient, even though occasional huge prompts cause token throughput saturation and throttling. The fix must preserve evaluation validity and avoid unnecessary user-data collection. What measured outcome validates the solution while preserving the stated constraints?

  1. The report reconciles billed service usage with per-feature consumption and unnecessary repeat embedding calls decline.
  2. The service meets per-minute token and tail-latency targets under representative large-context requests.
  3. An induced tool timeout is attributable to the exact trace span and remediation can target the failing service.
  4. The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query.

Explanation

Correct Answer

B:

The service meets per-minute token and tail-latency targets under representative large-context requests. Request count and generated-token throughput are different workload dimensions; equal request rates can create very different serving loads. a direct corrective action is to add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.

Incorrect Answers

A:

The report reconciles billed service usage with per-feature consumption and unnecessary repeat embedding calls decline. That addresses a different configuration issue rather than the main requirement. Verify instead: The service meets per-minute token and tail-latency targets under representative large-context requests.

C:

An induced tool timeout is attributable to the exact trace span and remediation can target the failing service. That addresses a different configuration issue rather than the main requirement. Verify instead: The service meets per-minute token and tail-latency targets under representative large-context requests.

D:

The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query. That addresses a different configuration issue rather than the main requirement. Verify instead: The service meets per-minute token and tail-latency targets under representative large-context requests.

Question 743

During a retrieval or model-customization performance review, the following condition occurs: A product support team plans expensive fine-tuning to memorize weekly price lists, even though the answers require current frequently edited catalog values. The change must keep citations, privacy and previously approved behavior intact. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
  2. Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.
  3. Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
  4. Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.

Explanation

Correct Answer

B:

Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation. This targets fine-tuning task selected when retrieval would better handle changing facts. Fine-tuning changes model behavior and knowledge imperfectly; retrieval is generally more suitable for fast-changing external facts. Verify the failure through: Inspect information update frequency, retrieval freshness requirement, model task errors, training cost and data-change workflow. Validate success with: A changed product price appears in answers after authorized index refresh without retraining the entire model. This matters here because a product support team plans expensive fine-tuning to memorize weekly price lists, even though the answers require….

Incorrect Answers

A:

Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This could address fine-tune production endpoint references deleted training artifact, but it does not solve the specified fine-tuning task selected when retrieval would better handle changing facts failure. The matching remediation is: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation. This matters here because a product support team plans expensive fine-tuning to memorize weekly price lists, even though the answers require….

C:

Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model. This could address embedding model replaced without reindexing stored vectors, but it does not solve the specified fine-tuning task selected when retrieval would better handle changing facts failure. The matching remediation is: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

D:

Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This could address fine-tune evaluation lacks drift checks for new customer terminology, but it does not solve the specified fine-tuning task selected when retrieval would better handle changing facts failure. The matching remediation is: Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

Question 744

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 production-safe remediation should the engineer apply to this AI workflow?

  1. Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.
  2. Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply.
  3. Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.
  4. Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.

Explanation

Correct Answer

B:

Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply. This targets iac workflow lacks repeatable infrastructure validation. Infrastructure automation should detect configuration drift and unexpected destructive changes before a production deployment proceeds. Verify the failure through: Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. Validate success with: 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….

Incorrect Answers

A:

Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access. This could address job identity lacks blob reader data-plane rights, but it does not solve the specified iac workflow lacks repeatable infrastructure validation failure. The matching remediation is: Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply.

C:

Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This could address aml private workspace storage access fails from compute, but it does not solve the specified iac workflow lacks repeatable infrastructure validation failure. The matching remediation is: Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply.

D:

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 iac workflow lacks repeatable infrastructure validation failure. The matching remediation is: Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply.

Question 745

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A drift-based retraining workflow runs every hour during a low-volume holiday weekend because its threshold ignores minimum sample size and confidence. The operator must safeguard training reproducibility and serving continuity. Which 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. Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining.
  3. Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
  4. Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.

Explanation

Correct Answer

B:

Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining. This targets retraining alarm triggers on insufficient sample volume. Drift-triggered retraining must balance statistical reliability against response time; an alert based on tiny samples can be misleading. Verify the failure through: Review monitoring window, input sample count, drift statistic, alert routing and retraining schedule history. Validate success with: Stable low-volume periods stop needless retraining while sustained meaningful drift invokes the reviewed pipeline. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A drift-based….

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 retraining alarm triggers on insufficient sample volume failure. The matching remediation is: Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A drift-based….

C:

Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs. This could address exploration notebook reads production data without reproducible snapshot, but it does not solve the specified retraining alarm triggers on insufficient sample volume failure. The matching remediation is: Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining.

D:

Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This could address missing feature values escape input drift checks, but it does not solve the specified retraining alarm triggers on insufficient sample volume failure. The matching remediation is: Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining.

Question 746

While preparing a secure Foundry model or agent release, the following condition occurs: An engineer commits a Foundry service API key directly in a Bicep parameter file, making the key readable in repository history despite later deletion. 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. Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
  2. Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
  3. Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.
  4. Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.

Explanation

Correct Answer

D:

Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds. This targets foundry infrastructure parameters embed a secret in source repository. Declarative infrastructure should manage references and identities rather than persist credentials as version-controlled cleartext values. Verify the failure through: Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events. Validate success with: The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An engineer commits a….

Incorrect Answers

A:

Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This could address foundry administrator role granted to consumer application, but it does not solve the specified foundry infrastructure parameters embed a secret in source repository failure. The matching remediation is: Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.

B:

Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests. This could address interactive inference deployed on unsuitable batch-style compute, but it does not solve the specified foundry infrastructure parameters embed a secret in source repository failure. The matching remediation is: Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.

C:

Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates. This could address foundry environment mixes development and production agent resources, but it does not solve the specified foundry infrastructure parameters embed a secret in source repository failure. The matching remediation is: Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.

Question 747

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A candidate model seems to outperform production by comparing AUC from a balanced sample with accuracy from an unbalanced live population. The operator must safeguard training reproducibility and serving continuity. Which investigation best verifies the cause before changing production configuration?

  1. Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage.
  2. Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
  3. Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
  4. Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern.

Explanation

Correct Answer

B:

Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This is the most relevant evidence for run comparison uses incompatible validation populations. A metric comparison is meaningful only when evaluation data and definitions align; different cohorts and metrics can invert model rankings. The matching controlled remediation is: Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A candidate….

Incorrect Answers

A:

Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. This would investigate pipeline cache reuses stale transform artifact rather than the documented run comparison uses incompatible validation populations issue. The relevant investigation is: Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.

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 run comparison uses incompatible validation populations issue. The relevant investigation is: Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A candidate….

D:

Compare application latency SLA, current endpoint type, request/response behavior, compute resources and intended inference pattern. This would investigate online scoring requirement deployed as batch endpoint rather than the documented run comparison uses incompatible validation populations issue. The relevant investigation is: Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.

Question 748

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A central model team registers a reusable component in a shared Azure ML registry, but application workspace users cannot resolve the component because registry access was never granted. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which acceptance test shows the AI operations defect is corrected?

  1. The job reads the required training blobs and cannot write or list unrelated protected containers.
  2. A validation job loads the intended features with the declared schema and rejects incompatible input files.
  3. Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry.
  4. The same versioned component runs against authorized data in two workspaces without editing its source implementation.

Explanation

Correct Answer

C:

Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry. Cross-workspace registries support reusing vetted assets but do not automatically authorize every workspace or resolve unknown versions. a direct corrective action is to grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A central model….

Incorrect Answers

A:

The job reads the required training blobs and cannot write or list unrelated protected containers. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry.

B:

A validation job loads the intended features with the declared schema and rejects incompatible input files. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A central model….

D:

The same versioned component runs against authorized data in two workspaces without editing its source implementation. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A central model….

Question 749

As an AI operations team checks production agent evaluation evidence, 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 workflow must produce measurable quality, safety and performance evidence. Which investigation best verifies the cause before changing production configuration?

  1. Inspect monitoring sample filters, event statuses, language distribution, evaluator eligibility and collected trace metadata.
  2. Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
  3. Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.
  4. Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.

Explanation

Correct Answer

C:

Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags. This is the most relevant evidence for token cost report omits embedding requests. GenAI cost analysis must include all model and supporting resources; tracking only final generation underestimates retrieval and indexing spend. The matching controlled remediation is: Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A retrieval….

Incorrect Answers

A:

Inspect monitoring sample filters, event statuses, language distribution, evaluator eligibility and collected trace metadata. This would investigate continuous monitoring has no representative sampling coverage rather than the documented token cost report omits embedding requests issue. The relevant investigation is: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

B:

Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. This would investigate prompt truncation strategy increases generated-token spend rather than the documented token cost report omits embedding requests issue. The relevant investigation is: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

D:

Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. This would investigate multi-turn agent evaluation uses isolated last message only rather than the documented token cost report omits embedding requests issue. The relevant investigation is: Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

Question 750

While preparing a secure Foundry model or agent release, the following condition occurs: A nightly GenAIOps evaluation workflow stops connecting to its Foundry project after the release team revokes an old client secret used by the CI job. The remediation must meet enterprise access and reliability requirements without a broad bypass. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
  2. Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.
  3. Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.
  4. Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.

Explanation

Correct Answer

C:

Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access. This targets foundry service principal credential rotated without updating pipeline. CI authentication is a separate dependency of a GenAIOps deployment; token renewal and secret rotation require an explicit supported credential flow. Verify the failure through: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. Validate success with: The workflow authenticates through a governed identity after old secrets are disabled and completes the intended evaluation without privileged keys in source control. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A nightly GenAIOps….

Incorrect Answers

A:

Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This could address foundry bicep rollout omits model deployment dependencies, but it does not solve the specified foundry service principal credential rotated without updating pipeline failure. The matching remediation is: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

B:

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 foundry service principal credential rotated without updating pipeline failure. The matching remediation is: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

D:

Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step. This could address vision input sent to text-only foundation model, but it does not solve the specified foundry service principal credential rotated without updating pipeline failure. The matching remediation is: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

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