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 13

Question 120

While preparing a secure Foundry model or agent release, the following condition occurs: A legal-document summarizer routinely receives 110,000-token inputs, but the selected model deployment has an insufficient supported context window and rejects or truncates requests. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits.
  2. Compare real tokenized input sizes, selected model version limits, deployment configuration and representative failure logs.
  3. Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
  4. Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.
  5. Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.

Explanation

Correct Answers

B:

Compare real tokenized input sizes, selected model version limits, deployment configuration and representative failure logs. This is the most relevant evidence for foundation model selected without required context window. Model suitability depends on context limits and task capability, not just a broad 'generative model' label. The matching controlled remediation is: Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.

D:

Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements. This targets foundation model selected without required context window. Model suitability depends on context limits and task capability, not just a broad 'generative model' label. Verify the failure through: Compare real tokenized input sizes, selected model version limits, deployment configuration and representative failure logs. Validate success with: A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.

Incorrect Answers

A:

Right-size the supported provisioned capacity or apply controlled request pacing and overflow strategy within budget and region limits. This is associated with provisioned throughput capacity insufficient at peak traffic, not the essential evidence-and-fix pair for foundation model selected without required context window. First examine: Compare real tokenized input sizes, selected model version limits, deployment configuration and representative failure logs. Then correct: Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.

C:

Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This is associated with prompt contract rollback ignores associated model version, not the essential evidence-and-fix pair for foundation model selected without required context window. First examine: Compare real tokenized input sizes, selected model version limits, deployment configuration and representative failure logs. Then correct: Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.

E:

Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access. This is associated with foundry service principal credential rotated without updating pipeline, not the essential evidence-and-fix pair for foundation model selected without required context window. First examine: Compare real tokenized input sizes, selected model version limits, deployment configuration and representative failure logs. Then correct: Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.

Question 121

While preparing a secure Foundry model or agent release, the following condition occurs: A production foundation model deployment is reachable from all development subnets after network security rules are copied from a permissive sandbox environment. The remediation must meet enterprise access and reliability requirements without a broad bypass. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.
  2. Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces.
  3. Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
  4. Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.
  5. Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.

Explanation

Correct Answers

A:

Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This is the most relevant evidence for network allowlist exposes production model endpoint to test subnet. Network segmentation and API authorization are complementary; an allowed network path should still follow environment separation policies. The matching controlled remediation is: Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.

D:

Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions. This targets network allowlist exposes production model endpoint to test subnet. Network segmentation and API authorization are complementary; an allowed network path should still follow environment separation policies. Verify the failure through: Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. Validate success with: Approved production callers pass tests while an untrusted test subnet cannot invoke the protected endpoint.

Incorrect Answers

B:

Compare approved private endpoint status, private DNS zones and links, container VNet DNS answers, effective routes and model request traces. This is associated with foundry private endpoint dns resolves to public ip, not the essential evidence-and-fix pair for network allowlist exposes production model endpoint to test subnet. First examine: Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. Then correct: Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.

C:

Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This is associated with foundry administrator role granted to consumer application, not the essential evidence-and-fix pair for network allowlist exposes production model endpoint to test subnet. First examine: Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. Then correct: Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.

E:

Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion. This is associated with foundry deployment alias changes model behavior unexpectedly, not the essential evidence-and-fix pair for network allowlist exposes production model endpoint to test subnet. First examine: Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. Then correct: Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.

Question 122

While preparing a secure Foundry model or agent release, the following condition occurs: A project deployment script succeeds in creating resources but fails when attempting model deployment because the selected subscription's capacity quota is insufficient. The remediation must meet enterprise access and reliability requirements without a broad bypass. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
  2. Deploy the governed Foundry resource and project in a supported compliant region with an available model option.
  3. Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.
  4. Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity.

Explanation

Correct Answer

C:

Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment. This targets azure cli foundry setup assumes existing model quota. Resource provisioning and model capacity allocation are separate operations; successful project creation does not reserve throughput for every selected model. Verify the failure through: Examine model deployment quota for selected region/type, Azure CLI errors, requested capacity units and existing model allocations. Validate success with: A repeated script completes provisioning under known approved quota and surfaces capacity constraints before application release.

Incorrect Answers

A:

Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests. This could address interactive inference deployed on unsuitable batch-style compute, but it does not solve the specified azure cli foundry setup assumes existing model quota failure. The matching remediation is: Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.

B:

Deploy the governed Foundry resource and project in a supported compliant region with an available model option. This could address foundry project created in mismatched resource location, but it does not solve the specified azure cli foundry setup assumes existing model quota failure. The matching remediation is: Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.

D:

Implement the correct supported Foundry private networking and DNS integration for the inference endpoint before denying public connectivity. This could address foundry private endpoint dns resolves to public ip, but it does not solve the specified azure cli foundry setup assumes existing model quota failure. The matching remediation is: Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.

Question 123

During a regulated Azure ML workspace infrastructure review, the following condition occurs: An organization disables public access on Azure ML backing storage, but its private compute subnet cannot resolve the storage account private endpoint and training jobs time out. The team must preserve approved access, model provenance and private network constraints. Which TWO complementary choices identify the issue and correct it? Select TWO.

  1. Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
  2. Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.
  3. Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.
  4. Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.
  5. Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema.

Explanation

Correct Answers

C:

Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This targets aml private workspace storage access fails from compute. Private endpoints require correct name resolution and route reachability; disabling public access without these dependencies can strand model training workloads. Verify the failure through: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. Validate success with: Training compute downloads required datasets over private endpoints while public storage access remains disabled.

D:

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

Incorrect Answers

A:

Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules. This is associated with oidc subject filter trusts unreviewed pull-request branches, not the essential evidence-and-fix pair for aml private workspace storage access fails from compute. First examine: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. Then correct: Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.

B:

Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This is associated with iac workflow lacks repeatable infrastructure validation, not the essential evidence-and-fix pair for aml private workspace storage access fails from compute. First examine: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. Then correct: Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.

E:

Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema. This is associated with pipeline component output type mismatches consumer, not the essential evidence-and-fix pair for aml private workspace storage access fails from compute. First examine: Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. Then correct: Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.

Question 124

During a regulated Azure ML workspace infrastructure review, the following condition occurs: A GitHub federated identity credential accepts tokens from any branch, allowing an unreviewed pull request to reach Azure Machine Learning production resources. The team must preserve approved access, model provenance and private network constraints. Which observable postchange result proves the intended remediation succeeded?

  1. Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry.
  2. Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test.
  3. Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access.
  4. Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review.

Explanation

Correct Answer

B:

Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test. Federated authentication remains vulnerable to overbroad trust claims if token subject matching does not reflect deployment governance. a direct corrective action is to restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.

Incorrect Answers

A:

Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry. That addresses a different configuration issue rather than the main requirement. Verify instead: Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test.

C:

Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access. That addresses a different configuration issue rather than the main requirement. Verify instead: Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test.

D:

Invalid or overbroad infrastructure changes fail validation and intended workspace updates deploy reproducibly after review. That addresses a different configuration issue rather than the main requirement. Verify instead: Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test.

Question 125

During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A managed online deployment repeatedly restarts because its startup script throws a missing-file exception before the liveness probe can succeed. The operator must safeguard training reproducibility and serving continuity. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.

  1. Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.
  2. Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results.
  3. Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.
  4. Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.
  5. Inspect request volume, concurrency, endpoint latency graphs, job timing and batch-friendly data path availability.

Explanation

Correct Answers

B:

Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. This is the most relevant evidence for endpoint deployment health probe fails before model initialization. Successful model registration does not guarantee scoring container initialization; startup dependencies must be validated in deployed environment. The matching controlled remediation is: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

D:

Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This targets endpoint deployment health probe fails before model initialization. Successful model registration does not guarantee scoring container initialization; startup dependencies must be validated in deployed environment. Verify the failure through: Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. Validate success with: Deployment reaches healthy readiness and handles a representative test request without restart loops.

Incorrect Answers

A:

Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This is associated with automated ml experiment uses leakage feature, not the essential evidence-and-fix pair for endpoint deployment health probe fails before model initialization. First examine: Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. Then correct: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

C:

Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates. This is associated with canary rollout sends all traffic to unvalidated candidate, not the essential evidence-and-fix pair for endpoint deployment health probe fails before model initialization. First examine: Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. Then correct: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

E:

Inspect request volume, concurrency, endpoint latency graphs, job timing and batch-friendly data path availability. This is associated with overnight bulk scoring saturates interactive online endpoint, not the essential evidence-and-fix pair for endpoint deployment health probe fails before model initialization. First examine: Review deployment container logs, init() traceback, model mount path, environment image and readiness/liveness probe results. Then correct: Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.

Question 126

During a regulated Azure ML workspace infrastructure review, the following condition occurs: An Azure ML training job authenticates with a managed identity but fails to download input data because it has workspace rights without Storage Blob Data Reader on the data container. The team must preserve approved access, model provenance and private network constraints. Select TWO: the strongest initial evidence and the aligned controlled correction.

  1. Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.
  2. Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity.
  3. Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records.
  4. Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration.
  5. Grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace.

Explanation

Correct Answers

A:

Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access. This targets job identity lacks blob reader data-plane rights. Workspace RBAC and Azure Storage data-plane roles are distinct; successful workspace authentication does not authorize every blob read. Verify the failure through: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. Validate success with: The job reads the required training blobs and cannot write or list unrelated protected containers.

C:

Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. This is the most relevant evidence for job identity lacks blob reader data-plane rights. Workspace RBAC and Azure Storage data-plane roles are distinct; successful workspace authentication does not authorize every blob read. The matching controlled remediation is: Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.

Incorrect Answers

B:

Inspect the workload principal, Azure ML workspace role assignment, subscription inheritance, required model-write actions and audit activity. This is associated with workspace contributor role granted to untrusted automation, not the essential evidence-and-fix pair for job identity lacks blob reader data-plane rights. First examine: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. Then correct: Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.

D:

Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration. This is associated with workspace dependencies point to unrelated secrets vault, not the essential evidence-and-fix pair for job identity lacks blob reader data-plane rights. First examine: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. Then correct: Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.

E:

Grant controlled registry consumption rights and use the fully qualified versioned registry asset reference in the target workspace. This is associated with registry model asset not available to second workspace, not the essential evidence-and-fix pair for job identity lacks blob reader data-plane rights. First examine: Check job identity selection, storage data-plane authorization, private endpoint reachability and storage diagnostic access-denied records. Then correct: Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.

Question 127

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

  1. Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
  2. Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata.
  3. Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker.
  4. Write the model into the declared Azure ML job output path and track the versioned artifact used in registration.
  5. Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining.

Explanation

Correct Answers

A:

Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation. This targets distributed training uses one shard for every worker. Data-parallel training must coordinate sampling and gradient aggregation; launching multiple processes does not automatically shard training data. Verify the failure through: Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. Validate success with: Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.

C:

Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. This is the most relevant evidence for distributed training uses one shard for every worker. Data-parallel training must coordinate sampling and gradient aggregation; launching multiple processes does not automatically shard training data. The matching controlled remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

Incorrect Answers

B:

Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata. This is associated with exploration notebook reads production data without reproducible snapshot, not the essential evidence-and-fix pair for distributed training uses one shard for every worker. First examine: Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. Then correct: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

D:

Write the model into the declared Azure ML job output path and track the versioned artifact used in registration. This is associated with training job does not persist output artifacts, not the essential evidence-and-fix pair for distributed training uses one shard for every worker. First examine: Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. Then correct: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

E:

Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining. This is associated with retraining alarm triggers on insufficient sample volume, not the essential evidence-and-fix pair for distributed training uses one shard for every worker. First examine: Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. Then correct: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.

Question 128

While preparing a secure Foundry model or agent release, the following condition occurs: An order-status assistant sometimes responds with prose rather than JSON because its system instructions never specify the required fields and output format expected by a downstream parser. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which acceptance test shows the AI operations defect is corrected?

  1. A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
  2. The comparison isolates prompt differences and produces reproducible evidence of quality and latency trade-offs.
  3. Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs.
  4. Prompt tests retain representative behavior without exposing customer identities in accessible Git history or future deployments.

Explanation

Correct Answer

C:

Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs. Prompts are part of an application interface; an implicit expectation that models always emit a parser-compatible object is unreliable. a direct corrective action is to define a versioned structured response instruction and supported JSON schema contract with parser-based validation.

Incorrect Answers

A:

A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs.

B:

The comparison isolates prompt differences and produces reproducible evidence of quality and latency trade-offs. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs.

D:

Prompt tests retain representative behavior without exposing customer identities in accessible Git history or future deployments. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs.

Question 129

While preparing a secure Foundry model or agent release, 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 remediation must meet enterprise access and reliability requirements without a broad bypass. Which observable postchange result proves the intended remediation succeeded?

  1. A repeated script completes provisioning under known approved quota and surfaces capacity constraints before application release.
  2. The front end scores authorized requests but cannot create, delete or reconfigure model deployments.
  3. Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
  4. Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs.

Explanation

Correct Answer

B:

The front end scores authorized requests but cannot create, delete or reconfigure model deployments. Application inference rights should be separated from platform administration; granting project owner privileges expands the impact of a compromised app. a direct corrective action is to replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.

Incorrect Answers

A:

A repeated script completes provisioning under known approved quota and surfaces capacity constraints before application release. That addresses a different configuration issue rather than the main requirement. Verify instead: The front end scores authorized requests but cannot create, delete or reconfigure model deployments.

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: The front end scores authorized requests but cannot create, delete or reconfigure model deployments.

D:

Representative order queries produce parseable permitted fields and reject or safely handle malformed outputs. That addresses a different configuration issue rather than the main requirement. Verify instead: The front end scores authorized requests but cannot create, delete or reconfigure model deployments.

Question 130

During a Foundry generative AI quality and observability incident, the following condition occurs: A Foundry agent returns an unhelpful answer after a search tool timeout but logs only the final generated text, hiding the actual failing service and request correlation. The fix must preserve evaluation validity and avoid unnecessary user-data collection. What approved correction resolves the failure without modifying unrelated healthy services?

  1. Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.
  2. Instrument cost attribution across generation and embedding services, cache reusable embeddings and alert on unplanned spend.
  3. Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run.
  4. Mask sensitive tokens and personal data, apply least-privilege log access and retain only necessary structured debugging evidence.

Explanation

Correct Answer

A:

Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers. This targets agent traces omit downstream tool failure reason. Multi-step AI agent troubleshooting needs per-tool traces, not just the final answer and an overall request status. Verify the failure through: Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs. Validate success with: An induced tool timeout is attributable to the exact trace span and remediation can target the failing 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 agent traces omit downstream tool failure reason failure. The matching remediation is: Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.

C:

Correct the test dataset mapping for query, context, response and reference fields and validate a sampled evaluation before the full run. This could address genai evaluation dataset lacks expected answer column mapping, but it does not solve the specified agent traces omit downstream tool failure reason failure. The matching remediation is: Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.

D:

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 agent traces omit downstream tool failure reason failure. The matching remediation is: Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.

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