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 77

Question 760

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

  1. The selected prompt improves successful issue resolution without factual regressions on the held-out support dataset.
  2. Adversarial test documents no longer cause unauthorized agent actions while the assistant still answers legitimate questions from the content.
  3. Requests from the approved VNet resolve the private address and succeed, while public connectivity remains blocked.
  4. Every production prompt version resolves to a reviewed commit and a failed change can be rolled back without copying an unknown portal draft.

Explanation

Correct Answer

A:

The selected prompt improves successful issue resolution without factual regressions on the held-out support dataset. A fluent response can still be wrong or unhelpful; prompt tuning requires evaluation metrics tied to application goals. a direct corrective action is to 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:

Adversarial test documents no longer cause unauthorized agent actions while the assistant still answers legitimate questions from the content. That addresses a different configuration issue rather than the main requirement. Verify instead: The selected prompt improves successful issue resolution without factual regressions on the held-out support dataset.

C:

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 selected prompt improves successful issue resolution without factual regressions on the held-out support dataset.

D:

Every production prompt version resolves to a reviewed commit and a failed change can be rolled back without copying an unknown portal draft. That addresses a different configuration issue rather than the main requirement. Verify instead: 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….

Question 761

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A data scientist runs a local notebook intending to log results to a governed Azure ML workspace, but the MLflow tracking URI still points to an earlier sandbox workspace. The resolution must preserve quality gates, documented artifacts and rollback options. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Add the vetted package to a versioned Azure ML environment and submit the notebook's training logic as a reproducible job.
  2. Examine sweep primary_metric, goal direction, logged metric names, candidate ranking and the held-out evaluation calculation.
  3. Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
  4. Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process.
  5. Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift.

Explanation

Correct Answers

C:

Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This targets mlflow tracking uri sends notebook runs to wrong workspace. An interactive MLflow process can log to whichever tracking server is configured; Azure workspace selection is not inferred from the notebook file's location. Verify the failure through: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Validate success with: The next test run appears only under the intended workspace with its parameters and model artifacts attached. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A data….

D:

Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. This is the most relevant evidence for mlflow tracking uri sends notebook runs to wrong workspace. An interactive MLflow process can log to whichever tracking server is configured; Azure workspace selection is not inferred from the notebook file's location. The matching controlled remediation is: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A data….

Incorrect Answers

A:

Add the vetted package to a versioned Azure ML environment and submit the notebook's training logic as a reproducible job. This is associated with notebook experiment installs packages only in interactive kernel, not the essential evidence-and-fix pair for mlflow tracking uri sends notebook runs to wrong workspace. First examine: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Then correct: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.

B:

Examine sweep primary_metric, goal direction, logged metric names, candidate ranking and the held-out evaluation calculation. This is associated with hyperparameter sweep minimizes the wrong objective, not the essential evidence-and-fix pair for mlflow tracking uri sends notebook runs to wrong workspace. First examine: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Then correct: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.

E:

Add suitable data quality and schema drift signals with thresholds for missingness alongside distribution drift. This is associated with missing feature values escape input drift checks, not the essential evidence-and-fix pair for mlflow tracking uri sends notebook runs to wrong workspace. First examine: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Then correct: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.

Question 762

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is trained across four GPU workers but all workers ingest the same unsharded dataset in each epoch, wasting resources and biasing effective training statistics. The resolution must preserve quality gates, documented artifacts and rollback options. What measured outcome validates the solution while preserving the stated constraints?

  1. Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported.
  2. The next test run appears only under the intended workspace with its parameters and model artifacts attached.
  3. Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.
  4. Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.

Explanation

Correct Answer

D:

Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition. Data-parallel training must coordinate sampling and gradient aggregation; launching multiple processes does not automatically shard training data. a direct corrective action is to configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….

Incorrect Answers

A:

Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported. That addresses a different configuration issue rather than the main requirement. Verify instead: Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.

B:

The next test run appears only under the intended workspace with its parameters and model artifacts attached. That addresses a different configuration issue rather than the main requirement. Verify instead: Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.

C:

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: Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.

Question 763

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A credit model's offline validation looks excellent because feature retrieval joins include transactions occurring after the intended historical prediction timestamp. The resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.
  2. Register a supported MLflow model with validated flavor, explicit input signature, pinned dependencies and a successful clean-environment load test.
  3. Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.
  4. Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.

Explanation

Correct Answer

D:

Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version. This targets online feature retrieval pulls values from after prediction time. Feature retrieval contracts must prevent future information from leaking into historical training and evaluation data. Verify the failure through: Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification. Validate success with: Historical inference replay uses only features available before prediction time and realistic performance survives evaluation.

Incorrect Answers

A:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This could address endpoint deployment health probe fails before model initialization, but it does not solve the specified online feature retrieval pulls values from after prediction time failure. The matching remediation is: Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.

B:

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 online feature retrieval pulls values from after prediction time failure. The matching remediation is: Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.

C:

Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This could address responsible ai evaluation omits demographic cohort slices, but it does not solve the specified online feature retrieval pulls values from after prediction time failure. The matching remediation is: Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.

Question 764

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A new Azure ML endpoint deployment is created for a new model but traffic is mistakenly set to 100% immediately, exposing all users before canary evaluation. The operator must safeguard training reproducibility and serving continuity. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds.
  2. Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.
  3. Move the approved bulk workload to a managed batch endpoint or batch inference job while preserving online capacity for interactive calls.
  4. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

Explanation

Correct Answer

B:

Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates. This targets canary rollout sends all traffic to unvalidated candidate. Managed online endpoints can route traffic among deployments; safe releases require explicit percentages and stop criteria. Verify the failure through: Inspect online endpoint traffic weights, deployment versions, request tracing, rollout approval and available prior stable deployment. Validate success with: Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail.

Incorrect Answers

A:

Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds. This could address data drift monitor uses wrong reference season, but it does not solve the specified canary rollout sends all traffic to unvalidated candidate failure. The matching remediation is: Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.

C:

Move the approved bulk workload to a managed batch endpoint or batch inference job while preserving online capacity for interactive calls. This could address overnight bulk scoring saturates interactive online endpoint, but it does not solve the specified canary rollout sends all traffic to unvalidated candidate failure. The matching remediation is: Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.

D:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This could address endpoint deployment health probe fails before model initialization, but it does not solve the specified canary rollout sends all traffic to unvalidated candidate failure. The matching remediation is: Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.

Question 765

As an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot repeats its complete policy corpus in every prompt, increasing token costs and latency, although only a few retrieved paragraphs are relevant to each answer. The workflow must produce measurable quality, safety and performance evidence. What measured outcome validates the solution while preserving the stated constraints?

  1. The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components.
  2. Average tokens per successful request falls while groundedness and task success remain within accepted limits.
  3. A canary regression is visible independently of stable baseline traffic before expanding rollout.
  4. The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query.

Explanation

Correct Answer

B:

Average tokens per successful request falls while groundedness and task success remain within accepted limits. Context volume affects token cost and latency; sending unnecessary text on every request is not equivalent to more reliable grounding. a direct corrective action is to use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot….

Incorrect Answers

A:

The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components. That addresses a different configuration issue rather than the main requirement. Verify instead: Average tokens per successful request falls while groundedness and task success remain within accepted limits. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot….

C:

A canary regression is visible independently of stable baseline traffic before expanding rollout. That addresses a different configuration issue rather than the main requirement. Verify instead: Average tokens per successful request falls while groundedness and task success remain within accepted limits.

D:

The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query. That addresses a different configuration issue rather than the main requirement. Verify instead: Average tokens per successful request falls while groundedness and task success remain within accepted limits.

Question 766

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 TWO complementary choices identify the issue and correct it? Select TWO.

  1. Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail.
  2. Revoke the exposed key, use managed identity or approved secure Key Vault secret references, and scrub sensitive release configuration from ongoing builds.
  3. Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.
  4. Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials.
  5. Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.

Explanation

Correct Answers

A:

Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. This is the most relevant evidence for foundry administrator role granted to consumer application. Application inference rights should be separated from platform administration; granting project owner privileges expands the impact of a compromised app. The matching controlled remediation is: 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,….

E:

Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This targets foundry administrator role granted to consumer application. Application inference rights should be separated from platform administration; granting project owner privileges expands the impact of a compromised app. Verify the failure through: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. Validate success with: The front end scores authorized requests but cannot create, delete or reconfigure model deployments. This matters here because a web front end that only calls an approved LLM deployment is assigned Foundry resource management privileges,….

Incorrect Answers

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 administrator role granted to consumer application. First examine: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. Then correct: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.

C:

Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. This is associated with foundry bicep rollout omits model deployment dependencies, not the essential evidence-and-fix pair for foundry administrator role granted to consumer application. First examine: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. Then correct: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.

D:

Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials. This is associated with serverless model endpoint unavailable to chosen identity, not the essential evidence-and-fix pair for foundry administrator role granted to consumer application. First examine: Review application service principal, endpoint invocation needs, Foundry resource IAM scope and management operation audit trail. Then correct: Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.

Question 767

During a Microsoft Foundry generative AI deployment review, the following condition occurs: An API service rolls back prompt text after a deployment incident but leaves the incompatible new foundation-model version in place, so tool-call formatting errors persist. The deployment must retain governed identities, endpoint contracts and auditable release history. Which investigation best verifies the cause before changing production configuration?

  1. Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
  2. Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.
  3. Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
  4. Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses.

Explanation

Correct Answer

C:

Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This is the most relevant evidence for prompt contract rollback ignores associated model version. A generative application behavior depends on versioned combinations of model, prompts and tools, not any single text template. The matching controlled remediation is: Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.

Incorrect Answers

A:

Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. This would investigate multilingual model selection fails target-language quality rather than the documented prompt contract rollback ignores associated model version issue. The relevant investigation is: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.

B:

Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs. This would investigate foundry environment mixes development and production agent resources rather than the documented prompt contract rollback ignores associated model version issue. The relevant investigation is: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.

D:

Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. This would investigate vision input sent to text-only foundation model rather than the documented prompt contract rollback ignores associated model version issue. The relevant investigation is: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.

Question 768

During a regulated Azure ML workspace infrastructure review, the following condition occurs: An Azure ML pipeline consistently fails to read input blobs after a storage-account key rotation because its registered datastore uses the old key. The team must preserve approved access, model provenance and private network constraints. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.
  2. Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
  3. Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
  4. Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics.

Explanation

Correct Answer

A:

Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments. This is the most relevant evidence for datastore authentication relies on expiring account key. Datastores provide connection configuration but do not bypass storage authentication; credential rotation must be propagated or identity access designed correctly. The matching controlled remediation is: Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management. This matters here because an Azure ML pipeline consistently fails to read input blobs after a storage-account key rotation because its….

Incorrect Answers

B:

Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. This would investigate job identity lacks blob reader data-plane rights rather than the documented datastore authentication relies on expiring account key issue. The relevant investigation is: Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.

C:

Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. This would investigate workspace contributor role granted to untrusted automation rather than the documented datastore authentication relies on expiring account key issue. The relevant investigation is: Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.

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 datastore authentication relies on expiring account key issue. The relevant investigation is: Inspect the datastore authentication mode, storage key rotation event, job input failure, and available identity-based storage permission assignments.

Question 769

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A document-assistant project exists in Foundry but cannot infer because its configured model deployment name is from a different project and unavailable to the target identity. The deployment must retain governed identities, endpoint contracts and auditable release history. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization.
  2. Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
  3. Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.
  4. Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.
  5. Permit only the required documented tool and service destinations via supported private or managed-network egress controls.

Explanation

Correct Answers

A:

Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. This is the most relevant evidence for foundry project links to wrong deployed model resource. A project workspace and a model deployment are distinct resources; using a logical model name without the correct deployment binding is insufficient. The matching controlled remediation is: Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection. This matters here because a document-assistant project exists in Foundry but cannot infer because its configured model deployment name is from….

C:

Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection. This targets foundry project links to wrong deployed model resource. A project workspace and a model deployment are distinct resources; using a logical model name without the correct deployment binding is insufficient. Verify the failure through: Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. Validate success with: Test queries reach the intended deployed model with attributable project usage and without cross-project credential exposure. This matters here because a document-assistant project exists in Foundry but cannot infer because its configured model deployment name is from….

Incorrect Answers

B:

Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This is associated with provisioned model update exceeds regional capacity ceiling, not the essential evidence-and-fix pair for foundry project links to wrong deployed model resource. First examine: Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. Then correct: Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.

D:

Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This is associated with network allowlist exposes production model endpoint to test subnet, not the essential evidence-and-fix pair for foundry project links to wrong deployed model resource. First examine: Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. Then correct: Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.

E:

Permit only the required documented tool and service destinations via supported private or managed-network egress controls. This is associated with agent tool calls fail behind overbroad outbound block, not the essential evidence-and-fix pair for foundry project links to wrong deployed model resource. First examine: Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. Then correct: Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.

Question 770

During a Foundry generative AI quality and observability incident, the following condition occurs: An evaluation compares chatbot answers against an automatically rewritten query rather than the original user intent, rewarding responses that miss the real troubleshooting question. The fix must preserve evaluation validity and avoid unnecessary user-data collection. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence.
  2. Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.
  3. Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples.
  4. Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.

Explanation

Correct Answer

C:

Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. This is the most relevant evidence for relevance evaluator uses wrong intended user query. Query rewriting aids retrieval but should not silently redefine what the user's response needs to accomplish. The matching controlled remediation is: Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric. This matters here because an evaluation compares chatbot answers against an automatically rewritten query rather than the original user….

Incorrect Answers

A:

Examine supported language list, safety evaluation examples, category coverage, severity thresholds and live red-team evidence. This would investigate harmful content probe set excludes multilingual input rather than the documented relevance evaluator uses wrong intended user query issue. The relevant investigation is: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples.

B:

Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. This would investigate multi-turn agent evaluation uses isolated last message only rather than the documented relevance evaluator uses wrong intended user query issue. The relevant investigation is: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples.

D:

Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags. This would investigate token cost report omits embedding requests rather than the documented relevance evaluator uses wrong intended user query issue. The relevant investigation is: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples.

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