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 36

Question 350

As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A retail demand model triggers constant drift alerts because its production Christmas data is compared only against a summer reference dataset without accounting for known seasonal regimes. The resolution must preserve quality gates, documented artifacts and rollback options. Which production-safe remediation should the engineer apply to this AI workflow?

  1. Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join.
  2. Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds.
  3. Allow the narrowly scoped supported compute-to-compute communication paths and correct the distributed training rendezvous configuration.
  4. Configure tail-latency and error-rate dashboards with capacity remedies appropriate to the measured bottleneck.

Explanation

Correct Answer

B:

Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds. This targets data drift monitor uses wrong reference season. Data drift measurement depends on a chosen reference distribution; a statistically different season is not automatically a harmful model change. Verify the failure through: Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. Validate success with: Normal seasonal variation stops generating false incidents and genuine distribution changes still cross documented alert criteria. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A retail demand….

Incorrect Answers

A:

Monitor available proxy signals immediately and compute labeled performance only after verified outcomes arrive through a governed join. This could address accuracy monitoring lacks delayed outcome labels, but it does not solve the specified data drift monitor uses wrong reference season failure. The matching remediation is: Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds.

C:

Allow the narrowly scoped supported compute-to-compute communication paths and correct the distributed training rendezvous configuration. This could address distributed job workers cannot communicate over required network path, but it does not solve the specified data drift monitor uses wrong reference season failure. The matching remediation is: Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds.

D:

Configure tail-latency and error-rate dashboards with capacity remedies appropriate to the measured bottleneck. This could address endpoint latency average conceals tail degradation, but it does not solve the specified data drift monitor uses wrong reference season failure. The matching remediation is: Configure a suitable seasonal baseline or context-aware drift monitor while retaining meaningful anomaly thresholds. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A retail demand….

Question 351

While deploying reproducible Azure Machine Learning infrastructure, 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 change must remain limited to authorized workspaces and avoid unreviewed production impact. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability.
  2. Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.
  3. Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
  4. Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.

Explanation

Correct Answer

A:

Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. This is the most relevant evidence for 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. The matching controlled 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 while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A distributed….

Incorrect Answers

B:

Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. This would investigate interactive compute instances remain running while unused rather than the documented compute cluster cannot allocate requested gpu quota issue. The relevant investigation is: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability.

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 compute cluster cannot allocate requested gpu quota issue. The relevant investigation is: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A distributed….

D:

Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations. This would investigate reusable component hardcodes workspace-specific asset path rather than the documented compute cluster cannot allocate requested gpu quota issue. The relevant investigation is: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability.

Question 352

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. Which targeted Azure AI operations change best addresses the documented problem?

  1. Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
  2. Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics.
  3. Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.
  4. Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

Explanation

Correct Answer

C:

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

A:

Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This could address few-shot prompt examples bias outputs toward one subgroup, but it does not solve the specified prompt includes untrusted retrieved instructions as system policy failure. The matching remediation is: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

B:

Evaluate both prompt variants against the same pinned model and representative dataset with controlled assignment and consistent metrics. This could address prompt a/b test uses different model versions in each arm, but it does not solve the specified prompt includes untrusted retrieved instructions as system policy failure. The matching 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….

D:

Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access. This could address foundry service principal credential rotated without updating pipeline, but it does not solve the specified prompt includes untrusted retrieved instructions as system policy failure. The matching remediation is: Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.

Question 353

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A GenAI application shares one Foundry project and keys between development and production, so test deployments can overwrite production agent configuration. The deployment must retain governed identities, endpoint contracts and auditable release history. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization.
  2. Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.
  3. Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.
  4. Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.

Explanation

Correct Answer

D:

Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs. This is the most relevant evidence for foundry environment mixes development and production agent resources. AI application environments need isolation across model deployment configuration, identity and release workflow, not just different branch names. The matching controlled remediation is: Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

Incorrect Answers

A:

Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization. This would investigate foundry project links to wrong deployed model resource rather than the documented foundry environment mixes development and production agent resources issue. The relevant investigation is: Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.

B:

Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load. This would investigate provisioned deployment pays for idle unused capacity rather than the documented foundry environment mixes development and production agent resources issue. The relevant investigation is: Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.

C:

Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces. This would investigate agent tool calls fail behind overbroad outbound block rather than the documented foundry environment mixes development and production agent resources issue. The relevant investigation is: Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.

Question 354

During a retrieval or model-customization performance review, the following condition occurs: An enterprise fine-tuned assistant passes its original launch test but performs poorly after new product codes appear, and no evaluation monitor samples the updated terminology. The change must keep citations, privacy and previously approved behavior intact. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together.
  2. Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.
  3. Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation.
  4. Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence.
  5. Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals.

Explanation

Correct Answers

B:

Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This targets fine-tune evaluation lacks drift checks for new customer terminology. Fine-tuned models can become stale as input distribution shifts; continuous quality monitoring is needed beyond deployment-day accuracy. Verify the failure through: Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. Validate success with: Previously unseen product queries are monitored and subsequent vetted versions meet current quality targets without erasing old task competence.

D:

Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. This is the most relevant evidence for fine-tune evaluation lacks drift checks for new customer terminology. Fine-tuned models can become stale as input distribution shifts; continuous quality monitoring is needed beyond deployment-day accuracy. The matching controlled remediation is: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.

Incorrect Answers

A:

Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together. This is associated with rag retrieval chunks truncate critical policy exception, not the essential evidence-and-fix pair for fine-tune evaluation lacks drift checks for new customer terminology. First examine: Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. Then correct: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.

C:

Use a governed retrieval-augmented grounding path for volatile factual content and reserve fine-tuning for stable behavior or output-format adaptation. This is associated with fine-tuning task selected when retrieval would better handle changing facts, not the essential evidence-and-fix pair for fine-tune evaluation lacks drift checks for new customer terminology. First examine: Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. Then correct: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.

E:

Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals. This is associated with synthetic training examples copy private customer identifiers, not the essential evidence-and-fix pair for fine-tune evaluation lacks drift checks for new customer terminology. First examine: Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. Then correct: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.

Question 355

As an AI operations team checks production agent evaluation evidence, the following condition occurs: An enterprise support agent appears successful on isolated questions but fails follow-up conversations because the test dataset discards prior chat turns and tool context. The workflow must produce measurable quality, safety and performance evidence. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.
  2. Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.
  3. Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
  4. Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.

Explanation

Correct Answer

A:

Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections. This targets multi-turn agent evaluation uses isolated last message only. Multi-turn agents depend on conversation state; evaluating only the final prompt can miss context handling, memory and tool-use errors. Verify the failure through: Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. Validate success with: The evaluation reveals and measures failures that depend on follow-up context and the selected agent version improves those cases.

Incorrect Answers

B:

Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence. This could address debug traces leak secrets and retrieved personal records, but it does not solve the specified multi-turn agent evaluation uses isolated last message only failure. The matching remediation is: Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.

C:

Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution. This could address content safety evaluation omits prompt injection tests, but it does not solve the specified multi-turn agent evaluation uses isolated last message only failure. The matching remediation is: Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.

D:

Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric. This could address relevance evaluator uses wrong intended user query, but it does not solve the specified multi-turn agent evaluation uses isolated last message only failure. The matching remediation is: Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.

Question 356

During a retrieval or model-customization performance review, the following condition occurs: An enterprise fine-tuned assistant passes its original launch test but performs poorly after new product codes appear, and no evaluation monitor samples the updated terminology. The change must keep citations, privacy and previously approved behavior intact. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Expand representative domain pairs and negatives, apply appropriate embedding model adaptation and retain a separate general-language retrieval evaluation.
  2. Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release.
  3. Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.
  4. Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.

Explanation

Correct Answer

C:

Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This targets fine-tune evaluation lacks drift checks for new customer terminology. Fine-tuned models can become stale as input distribution shifts; continuous quality monitoring is needed beyond deployment-day accuracy. Verify the failure through: Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. Validate success with: Previously unseen product queries are monitored and subsequent vetted versions meet current quality targets without erasing old task competence. This matters here because an enterprise fine-tuned assistant passes its original launch test but performs poorly after new product codes….

Incorrect Answers

A:

Expand representative domain pairs and negatives, apply appropriate embedding model adaptation and retain a separate general-language retrieval evaluation. This could address specialized embedding adaptation overfits small terminology set, but it does not solve the specified fine-tune evaluation lacks drift checks for new customer terminology failure. The matching remediation is: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This matters here because an enterprise fine-tuned assistant passes its original launch test but performs poorly after new product codes….

B:

Halt promotion, review training data and fine-tuning choices, and require safety regression gates on the customized candidate before release. This could address fine-tuned model loses safety boundary after customization, but it does not solve the specified fine-tune evaluation lacks drift checks for new customer terminology failure. The matching remediation is: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This matters here because an enterprise fine-tuned assistant passes its original launch test but performs poorly after new product codes….

D:

Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This could address fine-tune production endpoint references deleted training artifact, but it does not solve the specified fine-tune evaluation lacks drift checks for new customer terminology failure. The matching remediation is: Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.

Question 357

While optimizing a production RAG or fine-tuned model service, 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 resulting model must meet held-out quality and security criteria. 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. Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
  4. Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set.

Explanation

Correct Answer

C:

Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model. This targets embedding model replaced without reindexing stored vectors. Embedding vectors from different model spaces are not generally interchangeable even when their dimension counts happen to match. Verify the failure through: Compare query and index embedding model versions, vector dimensions, index schema, retrieval score distributions and migration logs. Validate success with: Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely.

Incorrect Answers

A:

Tune chunk size and overlap with structure-aware splitting so qualifying rules and exceptions remain retrievable together. This could address rag retrieval chunks truncate critical policy exception, but it does not solve the specified embedding model replaced without reindexing stored vectors failure. The matching remediation is: Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.

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 embedding model replaced without reindexing stored vectors failure. The matching remediation is: Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.

D:

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 embedding model replaced without reindexing stored vectors failure. The matching remediation is: Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.

Question 358

During a Microsoft Foundry generative AI deployment review, the following condition occurs: An enterprise disables public network access to Foundry but its container app still resolves the model service hostname to a public endpoint, resulting in failed inference calls. The deployment must retain governed identities, endpoint contracts and auditable release history. Which diagnostic evidence most directly distinguishes the described AI operations failure?

  1. Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.
  2. Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.
  3. Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests.
  4. Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.

Explanation

Correct Answer

D:

Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. This is the most relevant evidence for foundry private endpoint dns resolves to public ip. Private network security requires both endpoint approval and correct DNS resolution; a private endpoint creation event does not change every client's name resolution. The matching controlled remediation is: Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

Incorrect Answers

A:

Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes. This would investigate prompt a/b test uses different model versions in each arm rather than the documented foundry private endpoint dns resolves to public ip issue. The relevant investigation is: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.

B:

Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions. This would investigate foundry service principal credential rotated without updating pipeline rather than the documented foundry private endpoint dns resolves to public ip issue. The relevant investigation is: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.

C:

Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests. This would investigate agent runtime managed identity cannot read retrieval data rather than the documented foundry private endpoint dns resolves to public ip issue. The relevant investigation is: Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.

Question 359

During a Microsoft Foundry generative AI deployment review, the following condition occurs: A Foundry agent starts but cannot reach its required authorized Azure AI Search and storage tools because a managed-network policy blocks all outbound dependencies. The deployment must retain governed identities, endpoint contracts and auditable release history. What should the engineer examine first to confirm the specific AI-300 workload issue?

  1. Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests.
  2. Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
  3. Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.
  4. Inspect Foundry project and deployment inventory, pipeline environment variables, identities, API endpoints and change audit logs.

Explanation

Correct Answer

C:

Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces. This is the most relevant evidence for agent tool calls fail behind overbroad outbound block. Agent orchestration involves downstream tool connections; constraining model inference alone does not account for all network dependencies. The matching controlled remediation is: Permit only the required documented tool and service destinations via supported private or managed-network egress controls. This matters here because a Foundry agent starts but cannot reach its required authorized Azure AI Search and storage tools because a….

Incorrect Answers

A:

Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests. This would investigate agent runtime managed identity cannot read retrieval data rather than the documented agent tool calls fail behind overbroad outbound block issue. The relevant investigation is: Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.

B:

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 agent tool calls fail behind overbroad outbound block issue. The relevant investigation is: Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.

D:

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 agent tool calls fail behind overbroad outbound block issue. The relevant investigation is: Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces. This matters here because a Foundry agent starts but cannot reach its required authorized Azure AI Search and storage tools because a….

Question 360

While preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application shares one Foundry project and keys between development and production, so test deployments can overwrite production agent configuration. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which observable postchange result proves the intended remediation succeeded?

  1. The reviewed deployment succeeds without reusable secrets in committed files and old credentials no longer authorize calls.
  2. A test prompt or model deployment change affects only the development environment until an approved promotion occurs.
  3. Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
  4. The managed identity invokes the approved endpoint and a revoked developer key is no longer needed for production inference.

Explanation

Correct Answer

B:

A test prompt or model deployment change affects only the development environment until an approved promotion occurs. AI application environments need isolation across model deployment configuration, identity and release workflow, not just different branch names. a direct corrective action is to separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.

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: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

C:

Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied. That addresses a different configuration issue rather than the main requirement. Verify instead: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

D:

The managed identity invokes the approved endpoint and a revoked developer key is no longer needed for production inference. That addresses a different configuration issue rather than the main requirement. Verify instead: A test prompt or model deployment change affects only the development environment until an approved promotion occurs.

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