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 90

Question 890

As an MLOps engineer reviews a model training or inference pipeline, 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 resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?

  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. Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity.
  4. Register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test.

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. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team….

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. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A platform team….

C:

Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity. This could address sweep concurrency overwhelms scarce gpu quota, 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:

Register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test. This could address mlflow registry artifact cannot load on serving target, 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 891

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A legal-document summarizer routinely receives 110,000-token inputs, but the selected model deployment has an insufficient supported context window and rejects or truncates requests. The deployment must retain governed identities, endpoint contracts and auditable release history. What measured outcome validates the solution while preserving the stated constraints?

  1. The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate.
  2. A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
  3. Prompt tests retain representative behavior without exposing customer identities in accessible Git history or future deployments.
  4. Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code.

Explanation

Correct Answer

B:

A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. Model suitability depends on context limits and task capability, not just a broad 'generative model' label. a direct corrective action is to choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements. This matters here because a legal-document summarizer routinely receives 110,000-token inputs, but the selected model deployment has an….

Incorrect Answers

A:

The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate. That addresses a different configuration issue rather than the main requirement. Verify instead: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

C:

Prompt tests retain representative behavior without exposing customer identities in accessible Git history or future deployments. That addresses a different configuration issue rather than the main requirement. Verify instead: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

D:

Failed canary metrics restore 100% of traffic to the last approved deployment without changing unrelated agent code. That addresses a different configuration issue rather than the main requirement. Verify instead: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

Question 892

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. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.
  2. Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics.
  3. Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance.
  4. Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback.

Explanation

Correct Answer

A:

Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This is the most relevant evidence for iac workflow lacks repeatable infrastructure validation. Infrastructure automation should detect configuration drift and unexpected destructive changes before a production deployment proceeds. The matching controlled remediation is: 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

B:

Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics. This would investigate aml managed network blocks model registry egress rather than the documented iac workflow lacks repeatable infrastructure validation issue. The relevant investigation is: Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.

C:

Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. This would investigate oidc subject filter trusts unreviewed pull-request branches rather than the documented iac workflow lacks repeatable infrastructure validation issue. The relevant investigation is: Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.

D:

Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. This would investigate training environment lacks pinned package versions rather than the documented iac workflow lacks repeatable infrastructure validation issue. The relevant investigation is: Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.

Question 893

During a production Azure Machine Learning model lifecycle incident, 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 operator must safeguard training reproducibility and serving continuity. Which targeted Azure AI operations change best addresses the documented problem?

  1. Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity.
  2. Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining.
  3. Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.
  4. Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.

Explanation

Correct Answer

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 during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A scheduled….

Incorrect Answers

A:

Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity. This could address sweep concurrency overwhelms scarce gpu quota, but it does not solve the specified retraining pipeline deploys without model quality gate failure. The matching remediation is: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.

B:

Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining. This could address retraining alarm triggers on insufficient sample volume, but it does not solve the specified retraining pipeline deploys without model quality gate failure. The matching remediation is: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A scheduled….

D:

Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join. This could address accuracy monitoring lacks delayed outcome labels, but it does not solve the specified retraining pipeline deploys without model quality gate failure. The matching remediation is: Require objective quality and responsible AI approval thresholds before registering and promoting each retrained candidate.

Question 894

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A customer-service agent follows imperative instructions embedded in a retrieved help-center article because the prompt mixes document contents into its high-priority system instructions. The deployment must retain governed identities, endpoint contracts and auditable release history. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.
  2. Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
  3. Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests.
  4. Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions.
  5. Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

Explanation

Correct Answers

C:

Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. This is the most relevant evidence for prompt includes untrusted retrieved instructions as system policy. Retrieved text is task data, not an authorization source; prompt composition must preserve a trust boundary around untrusted context. The matching controlled remediation is: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

E:

Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling. This targets prompt includes untrusted retrieved instructions as system policy. Retrieved text is task data, not an authorization source; prompt composition must preserve a trust boundary around untrusted context. Verify the failure through: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. Validate success with: Adversarial test documents no longer cause unauthorized agent actions while the assistant still answers legitimate questions from the content.

Incorrect Answers

A:

Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion. This is associated with foundry deployment alias changes model behavior unexpectedly, not the essential evidence-and-fix pair for prompt includes untrusted retrieved instructions as system policy. First examine: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. Then correct: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

B:

Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This is associated with prompt variant comparison measures fluency not task success, not the essential evidence-and-fix pair for prompt includes untrusted retrieved instructions as system policy. First examine: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. Then correct: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

D:

Inspect deployed prompt content, Git repository history, CI release manifest, approval records and available prompt asset versions. This is associated with prompt hotfix bypasses git review and loses rollback history, not the essential evidence-and-fix pair for prompt includes untrusted retrieved instructions as system policy. First examine: Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. Then correct: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

Question 895

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A web front end that only calls an approved LLM deployment is assigned Foundry resource management privileges, allowing it to modify deployments and project settings. The deployment must retain governed identities, endpoint contracts and auditable release history. Which acceptance test shows the AI operations defect is corrected?

  1. Approved production callers pass tests while an untrusted test subnet cannot invoke the protected endpoint.
  2. Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
  3. The front end scores authorized requests but cannot create, delete or reconfigure model deployments.
  4. Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked.

Explanation

Correct Answer

C:

The front end scores authorized requests but cannot create, delete or reconfigure model deployments. Application inference rights should be separated from platform administration; granting project owner privileges expands the impact of a compromised app. a direct corrective action is to replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This matters here because a web front end that only calls an approved LLM deployment is assigned Foundry resource management privileges,….

Incorrect Answers

A:

Approved production callers pass tests while an untrusted test subnet cannot invoke the protected endpoint. That addresses a different configuration issue rather than the main requirement. Verify instead: The front end scores authorized requests but cannot create, delete or reconfigure model deployments.

B:

Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact. That addresses a different configuration issue rather than the main requirement. Verify instead: The front end scores authorized requests but cannot create, delete or reconfigure model deployments.

D:

Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked. That addresses a different configuration issue rather than the main requirement. Verify instead: The front end scores authorized requests but cannot create, delete or reconfigure model deployments.

Question 896

While preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application releases its Foundry project and calls a model name before that model deployment is created, causing intermittent first-run errors. The 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. Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.
  2. Permit only the required documented tool and service destinations via supported private or managed-network egress controls.
  3. Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
  4. Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.

Explanation

Correct Answer

C:

Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This targets foundry bicep rollout omits model deployment dependencies. Infrastructure-as-code can provision the platform consistently only when dependencies and deployment readiness are managed explicitly. Verify the failure through: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. Validate success with: Repeatable IaC releases create the expected project and model deployment before starting inference smoke tests. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application….

Incorrect Answers

A:

Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates. This could address foundry environment mixes development and production agent resources, but it does not solve the specified foundry bicep rollout omits model deployment dependencies failure. The matching remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application….

B:

Permit only the required documented tool and service destinations via supported private or managed-network egress controls. This could address agent tool calls fail behind overbroad outbound block, but it does not solve the specified foundry bicep rollout omits model deployment dependencies failure. The matching remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.

D:

Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow. This could address prompt contract rollback ignores associated model version, but it does not solve the specified foundry bicep rollout omits model deployment dependencies failure. The matching remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.

Question 897

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. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.
  2. Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.
  3. Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.
  4. Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.
  5. Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.

Explanation

Correct Answers

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….

E:

Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. This is the most relevant evidence for 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. The matching controlled remediation is: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A nightly GenAIOps….

Incorrect Answers

A:

Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces. This is associated with agent tool calls fail behind overbroad outbound block, not the essential evidence-and-fix pair for foundry service principal credential rotated without updating pipeline. First examine: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. Then correct: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

B:

Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds. This is associated with foundry infrastructure parameters embed a secret in source repository, not the essential evidence-and-fix pair for foundry service principal credential rotated without updating pipeline. First examine: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. Then correct: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

D:

Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review. This is associated with prompt repository references secret customer examples, not the essential evidence-and-fix pair for foundry service principal credential rotated without updating pipeline. First examine: Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. Then correct: Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A nightly GenAIOps….

Question 898

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A registered MLflow model loads on a developer laptop but fails at Azure ML endpoint startup because its conda dependencies and model signature were not packaged with the artifact. The resolution must preserve quality gates, documented artifacts and rollback options. 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. The managed endpoint loads the registered model and accepts test payloads matching its signature.
  3. A failed canary can restore the last approved model version without retraining or inventing replacement artifacts.
  4. Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria.

Explanation

Correct Answer

B:

The managed endpoint loads the registered model and accepts test payloads matching its signature. MLflow model registration is not proof of portability; required execution environment and signature must accompany the model artifact. a direct corrective action is to register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A registered….

Incorrect Answers

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: The managed endpoint loads the registered model and accepts test payloads matching its signature.

C:

A failed canary can restore the last approved model version without retraining or inventing replacement artifacts. That addresses a different configuration issue rather than the main requirement. Verify instead: The managed endpoint loads the registered model and accepts test payloads matching its signature.

D:

Promotion evidence reports acceptable cohort outcomes or blocks release when a disparity breaches approved fairness criteria. That addresses a different configuration issue rather than the main requirement. Verify instead: The managed endpoint loads the registered model and accepts test payloads matching its signature.

Question 899

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A nightly 15-million-row customer scoring task is sent as individual requests to a production real-time endpoint, degrading its daytime customer traffic. The resolution must preserve quality gates, documented artifacts and rollback options. Which observable postchange result proves the intended remediation succeeded?

  1. Deployment reaches healthy readiness and handles a representative test request without restart loops.
  2. Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
  3. A representative rollback test restores known-good predictions and endpoint health within the recovery target.
  4. Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.

Explanation

Correct Answer

B:

Overnight processing completes within its processing window and interactive endpoint latency remains within SLA. Batch scoring and synchronous online inference serve different workload shapes and should not contend for capacity unnecessarily. a direct corrective action is to move the approved bulk workload to a managed batch endpoint or batch inference job while preserving online capacity for interactive calls. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A nightly….

Incorrect Answers

A:

Deployment reaches healthy readiness and handles a representative test request without restart loops. That addresses a different configuration issue rather than the main requirement. Verify instead: Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.

C:

A representative rollback test restores known-good predictions and endpoint health within the recovery target. That addresses a different configuration issue rather than the main requirement. Verify instead: Overnight processing completes within its processing window and interactive endpoint latency remains within SLA. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A nightly….

D:

Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers. That addresses a different configuration issue rather than the main requirement. Verify instead: Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.

Question 900

While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A release workflow deploys Azure ML resources using a long-lived service-principal secret stored in GitHub, violating a keyless identity standard and complicating rotation. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which investigation best verifies the cause before changing production configuration?

  1. Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence.
  2. Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
  3. Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.
  4. Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors.

Explanation

Correct Answer

C:

Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This is the most relevant evidence for github action uses persistent azure client secret. GitHub Actions OpenID Connect can exchange scoped workflow identity for Azure access; persistent secrets are unnecessary when federation is correctly configured. The matching controlled remediation is: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A release….

Incorrect Answers

A:

Inspect az account subscription context, deployment scope flags, tenant identity, Bicep parameter file and cloud audit evidence. This would investigate azure cli deployment silently targets sandbox defaults rather than the documented github action uses persistent azure client secret issue. The relevant investigation is: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.

B:

Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This would investigate notebook merge bypasses protected evaluation tests rather than the documented github action uses persistent azure client secret issue. The relevant investigation is: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A release….

D:

Inspect MLTable path definitions, transformation instructions, sampled file headers, declared feature schema and job parsing errors. This would investigate mltable data asset schema mismatches training code rather than the documented github action uses persistent azure client secret issue. The relevant investigation is: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A release….

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