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 91

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

Question 901

While preparing a secure Foundry model or agent release, 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 remediation must meet enterprise access and reliability requirements without a broad bypass. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests.
  2. Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.
  3. Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.
  4. Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.
  5. Route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass.

Explanation

Correct Answers

A:

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. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A customer-service agent….

B:

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. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A customer-service agent….

Incorrect Answers

C:

Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics. This is associated with prompt a/b test uses different model versions in each arm, 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:

Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. 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.

E:

Route a controlled percentage of requests to the candidate and promote only after automated quality, safety and latency gates pass. This is associated with new foundation model replaces production without canary, 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 902

While deploying reproducible Azure Machine Learning infrastructure, 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 change must remain limited to authorized workspaces and avoid unreviewed production impact. Which investigation best verifies the cause before changing production configuration?

  1. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.
  2. Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.
  3. Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
  4. Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics.

Explanation

Correct Answer

B:

Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. This is the most relevant evidence for aml private workspace storage access fails from compute. Private endpoints require correct name resolution and route reachability; disabling public access without these dependencies can strand model training workloads. The matching controlled remediation is: Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: An organization….

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 aml private workspace storage access fails from compute issue. The relevant investigation is: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.

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 aml private workspace storage access fails from compute issue. The relevant investigation is: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.

D:

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 aml private workspace storage access fails from compute issue. The relevant investigation is: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.

Question 903

During a Foundry generative AI quality and observability incident, the following condition occurs: An incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly accessible Log Analytics workspace. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
  2. Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate.
  3. Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
  4. Inspect monitoring sample filters, event statuses, language distribution, evaluator eligibility and collected trace metadata.
  5. Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.

Explanation

Correct Answers

C:

Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This targets debug traces leak secrets and retrieved personal records. Observability data has its own privacy and security boundary; unrestricted prompt and tool payload logging can create new exposure risks. Verify the failure through: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. Validate success with: Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports. This matters here because an incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly….

E:

Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. This is the most relevant evidence for debug traces leak secrets and retrieved personal records. Observability data has its own privacy and security boundary; unrestricted prompt and tool payload logging can create new exposure risks. The matching controlled remediation is: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This matters here because an incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly….

Incorrect Answers

A:

Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This is associated with custom evaluator silently changes its scoring rubric, not the essential evidence-and-fix pair for debug traces leak secrets and retrieved personal records. First examine: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. Then correct: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.

B:

Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate. This is associated with foundry continuous evaluation ignores production deployment version, not the essential evidence-and-fix pair for debug traces leak secrets and retrieved personal records. First examine: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. Then correct: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.

D:

Inspect monitoring sample filters, event statuses, language distribution, evaluator eligibility and collected trace metadata. This is associated with continuous monitoring has no representative sampling coverage, not the essential evidence-and-fix pair for debug traces leak secrets and retrieved personal records. First examine: Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. Then correct: Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This matters here because an incident team enables verbose AI agent tracing that captures full API keys and customer documents into a broadly….

Question 904

As an AI operations team checks production agent evaluation evidence, 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 workflow must produce measurable quality, safety and performance evidence. Which acceptance test shows the AI operations defect is corrected?

  1. The service meets per-minute token and tail-latency targets under representative large-context requests.
  2. Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports.
  3. Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields.
  4. The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments.

Explanation

Correct Answer

A:

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. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A service….

Incorrect Answers

B:

Authorized engineers can reproduce request failures without finding credentials or customer PII in log exports. 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:

Evaluation scores correspond to the intended example queries and reference answers without null or swapped fields. 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 monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments. 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 905

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 observable postchange result proves the intended remediation succeeded?

  1. The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.
  2. The model version upgrade completes without an outage or unauthorized cross-region processing.
  3. Peak requests meet approved latency and throttling targets under a representative load test while capacity costs remain documented.
  4. Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked.

Explanation

Correct Answer

A:

The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected. Provisioned throughput may be billed for allocated capacity independent of actual use; deployment type should match utilization patterns. a direct corrective action is to move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A prototype assistant runs….

Incorrect Answers

B:

The model version upgrade completes without an outage or unauthorized cross-region processing. That addresses a different configuration issue rather than the main requirement. Verify instead: The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.

C:

Peak requests meet approved latency and throttling targets under a representative load test while capacity costs remain documented. That addresses a different configuration issue rather than the main requirement. Verify instead: The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.

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 prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.

Question 906

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region, but a release pipeline attempts the new deployment before checking quota. The deployment must retain governed identities, endpoint contracts and auditable release history. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
  2. Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.
  3. Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.
  4. Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
  5. Inspect deployment routing weights, evaluated model versions, incident timing, canary quality dashboards and rollback path.

Explanation

Correct Answers

A:

Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. This is the most relevant evidence for provisioned model update exceeds regional capacity ceiling. Model capacity is region and deployment-type dependent; version upgrades cannot assume unused PTUs are available on demand. The matching controlled remediation is: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This matters here because a planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region,….

D:

Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This targets provisioned model update exceeds regional capacity ceiling. Model capacity is region and deployment-type dependent; version upgrades cannot assume unused PTUs are available on demand. Verify the failure through: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. Validate success with: The model version upgrade completes without an outage or unauthorized cross-region processing. This matters here because a planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region,….

Incorrect Answers

B:

Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions. This is associated with network allowlist exposes production model endpoint to test subnet, not the essential evidence-and-fix pair for provisioned model update exceeds regional capacity ceiling. First examine: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. Then correct: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.

C:

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 provisioned model update exceeds regional capacity ceiling. First examine: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. Then correct: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.

E:

Inspect deployment routing weights, evaluated model versions, incident timing, canary quality dashboards and rollback path. This is associated with new foundation model replaces production without canary, not the essential evidence-and-fix pair for provisioned model update exceeds regional capacity ceiling. First examine: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. Then correct: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.

Question 907

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional GPU-family vCPU quota than the subscription currently has. The team must preserve approved access, model provenance and private network constraints. Which targeted Azure AI operations change best addresses the documented problem?

  1. Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.
  2. Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
  3. Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
  4. Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration.

Explanation

Correct Answer

C:

Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This targets compute cluster cannot allocate requested gpu quota. Azure ML computes draw from Azure regional VM family quota; declaring a cluster does not reserve unlimited GPU instances. Verify the failure through: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. Validate success with: The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement. This matters here because a distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional….

Incorrect Answers

A:

Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands. This could address azure cli deployment silently targets sandbox defaults, but it does not solve the specified compute cluster cannot allocate requested gpu quota failure. The matching remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.

B:

Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This could address datastore uri selects the incorrect storage container, but it does not solve the specified compute cluster cannot allocate requested gpu quota failure. The matching remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.

D:

Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration. This could address workspace dependencies point to unrelated secrets vault, but it does not solve the specified compute cluster cannot allocate requested gpu quota failure. The matching remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This matters here because a distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional….

Question 908

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the evaluation measures only fluency and omits task completion and grounding. 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. Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
  2. Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
  3. Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests.
  4. Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds.
  5. Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.

Explanation

Correct Answers

A:

Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This targets prompt variant comparison measures fluency not task success. A fluent response can still be wrong or unhelpful; prompt tuning requires evaluation metrics tied to application goals. Verify the failure through: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. Validate success with: The selected prompt improves successful issue resolution without factual regressions on the held-out support dataset. This matters here because a new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the….

D:

Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. This is the most relevant evidence for prompt variant comparison measures fluency not task success. A fluent response can still be wrong or unhelpful; prompt tuning requires evaluation metrics tied to application goals. The matching controlled remediation is: Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This matters here because a new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the….

Incorrect Answers

B:

Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This is associated with foundry administrator role granted to consumer application, not the essential evidence-and-fix pair for prompt variant comparison measures fluency not task success. First examine: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. Then correct: Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.

C:

Examine prompt role separation, retrieval snippets, untrusted-content boundary, tool permissions and injection regression tests. This is associated with prompt includes untrusted retrieved instructions as system policy, not the essential evidence-and-fix pair for prompt variant comparison measures fluency not task success. First examine: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. Then correct: Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.

E:

Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This is associated with few-shot prompt examples bias outputs toward one subgroup, not the essential evidence-and-fix pair for prompt variant comparison measures fluency not task success. First examine: Review prompt variant outputs, evaluator criteria, human task labels, relevance/groundedness scores and business acceptance thresholds. Then correct: Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This matters here because a new troubleshooting prompt sounds polished in sample responses but fails to give actionable next steps because the….

Question 909

While preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its LLM successfully but receives access denied when querying an Azure AI Search index because the assigned managed identity lacks search data reader rights. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which acceptance test shows the AI operations defect is corrected?

  1. The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls.
  2. Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
  3. A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
  4. Repeatable IaC releases create the expected project and model deployment before starting inference smoke tests.

Explanation

Correct Answer

B:

Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied. Foundry model access and Azure AI Search data-plane authorization are separate permission boundaries for a retrieval-augmented agent. a direct corrective action is to grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its….

Incorrect Answers

A:

The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.

C:

A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.

D:

Repeatable IaC releases create the expected project and model deployment before starting inference smoke tests. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A Foundry agent invokes its….

Question 910

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. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema.
  2. Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline.
  3. Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
  4. Grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace.

Explanation

Correct Answer

B:

Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline. This targets 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. Verify the failure through: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations. Validate success with: The same versioned component runs against authorized data in two workspaces without editing its source implementation. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A pipeline….

Incorrect Answers

A:

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 reusable component hardcodes workspace-specific asset path failure. The matching remediation is: Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline.

C:

Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This could address datastore uri selects the incorrect storage container, but it does not solve the specified reusable component hardcodes workspace-specific asset path failure. The matching remediation is: Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline.

D:

Grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace. This could address registry model asset not available to second workspace, but it does not solve the specified reusable component hardcodes workspace-specific asset path failure. The matching 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….

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