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 82

Question 810

During a Foundry generative AI quality and observability incident, the following condition occurs: A retrieval assistant generates fluent answers citing unrelated documents, yet the release dashboard declares success based solely on readability. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series.
  2. Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments.
  3. Apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts.
  4. Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.
  5. Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.

Explanation

Correct Answers

B:

Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments. This is the most relevant evidence for groundedness metric conflated with response fluency. Readability and factual support are distinct dimensions of GenAI output quality; polished prose is not evidence that retrieved sources justify a claim. The matching controlled remediation is: Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency. This matters here because a retrieval assistant generates fluent answers citing unrelated documents, yet the release dashboard declares….

D:

Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency. This targets groundedness metric conflated with response fluency. Readability and factual support are distinct dimensions of GenAI output quality; polished prose is not evidence that retrieved sources justify a claim. Verify the failure through: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments. Validate success with: Unsupported claims fail the release gate even when the answers are grammatically smooth. This matters here because a retrieval assistant generates fluent answers citing unrelated documents, yet the release dashboard declares….

Incorrect Answers

A:

Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. This is associated with custom evaluator silently changes its scoring rubric, not the essential evidence-and-fix pair for groundedness metric conflated with response fluency. First examine: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments. Then correct: Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.

C:

Apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts. This is associated with continuous monitoring has no representative sampling coverage, not the essential evidence-and-fix pair for groundedness metric conflated with response fluency. First examine: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments. Then correct: Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.

E:

Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections. This is associated with multi-turn agent evaluation uses isolated last message only, not the essential evidence-and-fix pair for groundedness metric conflated with response fluency. First examine: Inspect evaluator definitions, retrieved source contexts, response citations, groundedness scoring and sampled human reference judgments. Then correct: Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.

Question 811

During a retrieval or model-customization performance review, the following condition occurs: A benefits assistant returns a false eligibility statement because its document chunker splits a policy paragraph away from a nearby exception that changes the rule. The change must keep citations, privacy and previously approved behavior intact. Which targeted Azure AI operations change best addresses the documented problem?

  1. Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together.
  2. Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking.
  3. Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.
  4. Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.

Explanation

Correct Answer

A:

Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together. This targets rag retrieval chunks truncate critical policy exception. Chunk segmentation changes which context is available to the model; cutting a qualification out of its parent rule can produce confidently unsupported answers. Verify the failure through: Examine source document structure, chunk boundaries, overlap size, retrieved context, query examples and groundedness errors. Validate success with: Evaluation questions about eligibility include the correct exception and still return concise supported citations. This matters here because a benefits assistant returns a false eligibility statement because its document chunker splits a policy paragraph….

Incorrect Answers

B:

Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking. This could address pure vector search misses exact regulatory clause codes, but it does not solve the specified rag retrieval chunks truncate critical policy exception failure. The matching remediation is: Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together. This matters here because a benefits assistant returns a false eligibility statement because its document chunker splits a policy paragraph….

C:

Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This could address hybrid retrieval double-counts outdated documents, but it does not solve the specified rag retrieval chunks truncate critical policy exception failure. The matching remediation is: Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together.

D:

Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation. This could address fine-tuning task selected when retrieval would better handle changing facts, but it does not solve the specified rag retrieval chunks truncate critical policy exception failure. The matching remediation is: Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together.

Question 812

During a Foundry generative AI quality and observability incident, the following condition occurs: A user-facing agent becomes slow after an LLM deployment change, but the team only records total response time and cannot tell retrieval delay from model generation delay. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which observable postchange result proves the intended remediation succeeded?

  1. The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments.
  2. An induced tool timeout is attributable to the exact trace span and remediation can target the failing service.
  3. The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components.
  4. The evaluation reveals and measures failures that depend on follow-up context and the selected agent version improves those cases.

Explanation

Correct Answer

C:

The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components. Latency budgets should separate agent orchestration, retrieval and generation; total duration alone cannot locate the bottleneck. a direct corrective action is to instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change. This matters here because a user-facing agent becomes slow after an LLM deployment change, but the team only records total response time and….

Incorrect Answers

A:

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 responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components.

B:

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 responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components.

D:

The evaluation reveals and measures failures that depend on follow-up context and the selected agent version improves those cases. That addresses a different configuration issue rather than the main requirement. Verify instead: The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components. This matters here because a user-facing agent becomes slow after an LLM deployment change, but the team only records total response time and….

Question 813

During a retrieval or model-customization performance review, the following condition occurs: A team tunes its retrieval parameters against the same 300 hand-labeled questions later used as the formal deployment acceptance test, overstating generalization. The change must keep citations, privacy and previously approved behavior intact. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
  2. Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set.
  3. Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.
  4. Split labeled queries into development and untouched final evaluation sets, with repeatable leakage-resistant A/B comparisons.

Explanation

Correct Answer

D:

Split labeled queries into development and untouched final evaluation sets, with repeatable leakage-resistant A/B comparisons. This targets offline rag evaluator leaks training questions into test set. Repeated optimization against the final test set leaks evaluation information into model selection, making reported quality overly optimistic. Verify the failure through: Examine question-set provenance, tuning history, held-out set separation, document version and evaluator configuration. Validate success with: Candidate rankings remain robust on previously unseen held-out queries and the acceptance test cannot be tuned after results are disclosed. This matters here because a team tunes its retrieval parameters against the same 300 hand-labeled questions later used as the formal….

Incorrect Answers

A:

Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails. This could address rag a/b experiment judges only click-through not factuality, but it does not solve the specified offline rag evaluator leaks training questions into test set failure. The matching remediation is: Split labeled queries into development and untouched final evaluation sets, with repeatable leakage-resistant A/B comparisons.

B:

Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set. This could address synthetic data overwhelms minority real-world edge cases, but it does not solve the specified offline rag evaluator leaks training questions into test set failure. The matching remediation is: Split labeled queries into development and untouched final evaluation sets, with repeatable leakage-resistant A/B comparisons.

C:

Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This could address hybrid retrieval double-counts outdated documents, but it does not solve the specified offline rag evaluator leaks training questions into test set failure. The matching remediation is: Split labeled queries into development and untouched final evaluation sets, with repeatable leakage-resistant A/B comparisons.

Question 814

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 investigation best verifies the cause before changing production configuration?

  1. Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.
  2. Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events.
  3. Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.
  4. Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.

Explanation

Correct Answer

B:

Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events. This is the most relevant evidence for 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. The matching controlled remediation is: Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An engineer commits a….

Incorrect Answers

A:

Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. This would investigate foundry administrator role granted to consumer application rather than the documented foundry infrastructure parameters embed a secret in source repository issue. The relevant investigation is: Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events.

C:

Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. This would investigate foundry private endpoint dns resolves to public ip rather than the documented foundry infrastructure parameters embed a secret in source repository issue. The relevant investigation is: Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events.

D:

Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This would investigate prompt contract rollback ignores associated model version rather than the documented foundry infrastructure parameters embed a secret in source repository issue. The relevant investigation is: Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events.

Question 815

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A tool-enabled finance agent passes harmful-text screening but executes instructions inside a hostile retrieved web page because its safety suite contains no prompt-injection or tool-misuse cases. The workflow must produce measurable quality, safety and performance evidence. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
  2. Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series.
  3. Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
  4. Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.
  5. Make required quality/safety criteria explicit CI gates and stop deployment when evaluated scores fail the approved tolerances.

Explanation

Correct Answers

A:

Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution. This targets content safety evaluation omits prompt injection tests. Harmful-content detection alone does not test whether an agent obeys malicious instructions inserted into lower-trust retrieved material. Verify the failure through: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Validate success with: An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.

C:

Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. This is the most relevant evidence for content safety evaluation omits prompt injection tests. Harmful-content detection alone does not test whether an agent obeys malicious instructions inserted into lower-trust retrieved material. The matching controlled remediation is: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.

Incorrect Answers

B:

Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. This is associated with custom evaluator silently changes its scoring rubric, not the essential evidence-and-fix pair for content safety evaluation omits prompt injection tests. First examine: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Then correct: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.

D:

Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers. This is associated with agent traces omit downstream tool failure reason, not the essential evidence-and-fix pair for content safety evaluation omits prompt injection tests. First examine: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Then correct: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.

E:

Make required quality/safety criteria explicit CI gates and stop deployment when evaluated scores fail the approved tolerances. This is associated with evaluation workflow fails to block degraded agent deployment, not the essential evidence-and-fix pair for content safety evaluation omits prompt injection tests. First examine: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Then correct: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.

Question 816

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A team upgrades a custom evaluator prompt and compares this month's agent scores to last month's, even though the grading rubric and baseline model changed. The workflow must produce measurable quality, safety and performance evidence. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.
  2. Segment continuous evaluation by model/agent deployment version and configure a focused regression alert for the candidate.
  3. Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series.
  4. Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
  5. Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency.

Explanation

Correct Answers

C:

Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. This is the most relevant evidence for custom evaluator silently changes its scoring rubric. Evaluation metrics are outputs of versioned assessment logic; changing a judge or rubric can change scores without any underlying agent change. The matching controlled remediation is: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A team….

D:

Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This targets custom evaluator silently changes its scoring rubric. Evaluation metrics are outputs of versioned assessment logic; changing a judge or rubric can change scores without any underlying agent change. Verify the failure through: Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. Validate success with: Historical baselines can be reproduced with the same evaluator version and new rubric results are labeled separately. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A team….

Incorrect Answers

A:

Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. This is associated with multi-turn agent evaluation uses isolated last message only, not the essential evidence-and-fix pair for custom evaluator silently changes its scoring rubric. First examine: Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. Then correct: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.

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 custom evaluator silently changes its scoring rubric. First examine: Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. Then correct: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.

E:

Add context-groundedness and relevance evaluation on representative answers alongside coherence and fluency. This is associated with groundedness metric conflated with response fluency, not the essential evidence-and-fix pair for custom evaluator silently changes its scoring rubric. First examine: Review evaluator code and prompt versions, rubric labels, baseline sample scores and published metric time series. Then correct: Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A team….

Question 817

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML training pipeline intermittently starts training before its feature-engineering output is ready because the training component references a static path instead of the upstream component's declared output. The operator must safeguard training reproducibility and serving continuity. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Examine sweep primary_metric, goal direction, logged metric names, candidate ranking and the held-out evaluation calculation.
  2. Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.
  3. Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input.
  4. Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results.

Explanation

Correct Answer

B:

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

Incorrect Answers

A:

Examine sweep primary_metric, goal direction, logged metric names, candidate ranking and the held-out evaluation calculation. This would investigate hyperparameter sweep minimizes the wrong objective rather than the documented pipeline graph omits feature-build dependency issue. The relevant investigation is: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.

C:

Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input. This would investigate training job does not persist output artifacts rather than the documented pipeline graph omits feature-build dependency issue. The relevant investigation is: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.

D:

Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. This would investigate endpoint deployment health probe fails before model initialization rather than the documented pipeline graph omits feature-build dependency issue. The relevant investigation is: Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML….

Question 818

During a retrieval or model-customization performance review, the following condition occurs: A domain RAG service changes the query embedding model but keeps document vectors created by a different model, producing irrelevant similarity matches. The change must keep citations, privacy and previously approved behavior intact. Which acceptance test shows the AI operations defect is corrected?

  1. The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation.
  2. Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely.
  3. A changed product price appears in answers after authorized index refresh without retraining the entire model.
  4. Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users.

Explanation

Correct Answer

B:

Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely. Embedding vectors from different model spaces are not generally interchangeable even when their dimension counts happen to match. a direct corrective action is to re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.

Incorrect Answers

A:

The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely.

C:

A changed product price appears in answers after authorized index refresh without retraining the entire model. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely.

D:

Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely.

Question 819

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. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training.
  2. Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
  3. Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance.
  4. Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.
  5. Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.

Explanation

Correct Answers

B:

Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow. This targets 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. Verify the failure through: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Validate success with: The approved branch deploys using short-lived federated tokens, and old client secrets can be revoked without breaking releases. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A release….

D:

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:

Rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This is associated with mltable data asset schema mismatches training code, not the essential evidence-and-fix pair for github action uses persistent azure client secret. First examine: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Then correct: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.

C:

Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. This is associated with oidc subject filter trusts unreviewed pull-request branches, not the essential evidence-and-fix pair for github action uses persistent azure client secret. First examine: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Then correct: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.

E:

Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment. This is associated with bicep workspace declaration misses dependent private resources, not the essential evidence-and-fix pair for github action uses persistent azure client secret. First examine: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Then correct: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.

Question 820

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

  1. Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
  2. Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.
  3. Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.
  4. Apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts.

Explanation

Correct Answer

A:

Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand. This targets genai throughput report mixes responses and tokens. Request count and generated-token throughput are different workload dimensions; equal request rates can create very different serving loads. Verify the failure through: Inspect tokens per request, input/output token ratios, concurrency, throttling status and model deployment quota. Validate success with: The service meets per-minute token and tail-latency targets under representative large-context requests. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A service….

Incorrect Answers

B:

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

C:

Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections. This could address multi-turn agent evaluation uses isolated last message only, but it does not solve the specified genai throughput report mixes responses and tokens failure. The matching remediation is: Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.

D:

Apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts. This could address continuous monitoring has no representative sampling coverage, but it does not solve the specified genai throughput report mixes responses and tokens failure. The matching remediation is: 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….

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