Microsoft AI-300 Practice Test 25
Question 240
While preparing a secure Foundry model or agent release, the following condition occurs: A chat assistant must return low-latency answers but the team selects an offline batch inference architecture that produces responses only after a scheduled job completes. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which acceptance test shows the AI operations defect is corrected?
- Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
- The last stable response and tool-call contracts are recovered across representative transactions without rebuilding application data.
- A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
- Test queries reach the intended deployed model with attributable project usage and without cross-project credential exposure.
Explanation
Correct Answer
A:Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact. Generative chat workloads ordinarily require online serving semantics; scheduled batch compute cannot satisfy an interactive response deadline. a direct corrective action is to deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
Incorrect Answers
B:The last stable response and tool-call contracts are recovered across representative transactions without rebuilding application data. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
C:A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
D:Test queries reach the intended deployed model with attributable project usage and without cross-project credential exposure. That addresses a different configuration issue rather than the main requirement. Verify instead: Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
Question 241
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A new managed-network isolated Azure ML workspace can train local models but fails to pull an approved model package from a registry because outbound access was not allowlisted. The team must preserve approved access, model provenance and private network constraints. Which targeted Azure AI operations change best addresses the documented problem?
- Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
- Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
- Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
- Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.
Explanation
Correct Answer
B:Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This targets aml managed network blocks model registry egress. Workspace network isolation controls package and asset connectivity in addition to private inbound access; approved egress must be explicit. Verify the failure through: Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics. Validate success with: Authorized registry models load in the isolated environment and unrelated external destinations remain blocked.
Incorrect Answers
A:Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate. This could address github deployment pipeline omits secure environment approvals, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
C:Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant. This could address workspace contributor role granted to untrusted automation, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
D:Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This could address aml private workspace storage access fails from compute, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
Question 242
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. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
- Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates.
- Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.
- Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance.
- Bind every training job and model registration to a reviewed Git commit SHA and immutable environment/data version in the workflow.
Explanation
Correct Answers
A:Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules. This targets oidc subject filter trusts unreviewed pull-request branches. Federated authentication remains vulnerable to overbroad trust claims if token subject matching does not reflect deployment governance. Verify the failure through: Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. Validate success with: Only authorized protected workflows obtain production Azure tokens while unreviewed pull requests fail the access test.
D:Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. This is the most relevant evidence for oidc subject filter trusts unreviewed pull-request branches. Federated authentication remains vulnerable to overbroad trust claims if token subject matching does not reflect deployment governance. The matching controlled remediation is: Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
Incorrect Answers
B:Pin the pipeline input to an approved versioned data asset and advance versions through controlled evaluation gates. This is associated with versionless dataset reference breaks reproducibility, not the essential evidence-and-fix pair for oidc subject filter trusts unreviewed pull-request branches. First examine: Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. Then correct: Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
C:Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This is associated with github action uses persistent azure client secret, not the essential evidence-and-fix pair for oidc subject filter trusts unreviewed pull-request branches. First examine: Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. Then correct: Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
E:Bind every training job and model registration to a reviewed Git commit SHA and immutable environment/data version in the workflow. This is associated with production training script commit cannot be traced, not the essential evidence-and-fix pair for oidc subject filter trusts unreviewed pull-request branches. First examine: Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. Then correct: Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
Question 243
During a retrieval or model-customization performance review, the following condition occurs: An agent's fine-tuning corpus is expanded with thousands of synthetic easy examples, making real rare technical failures a small fraction of training and reducing performance on those cases. The change must keep citations, privacy and previously approved behavior intact. Which production-safe remediation should the engineer apply to this AI workflow?
- Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set.
- Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.
- Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
- Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.
Explanation
Correct Answer
A:Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set. This targets synthetic data overwhelms minority real-world edge cases. Synthetic data increases quantity but can distort the target distribution and crowd out the cases most important for deployment risk. Verify the failure through: Compare synthetic-to-real sampling weights, rare-class coverage, holdout error breakdown and generated example diversity. Validate success with: The model improves typical coverage while retaining or improving measured accuracy for rare high-impact cases.
Incorrect Answers
B:Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content. This could address synthetic training examples copy private customer identifiers, but it does not solve the specified synthetic data overwhelms minority real-world edge cases failure. The matching remediation is: Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set.
C:Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails. This could address rag a/b experiment judges only click-through not factuality, but it does not solve the specified synthetic data overwhelms minority real-world edge cases failure. The matching remediation is: Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set.
D:Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression. This could address fine-tune evaluation lacks drift checks for new customer terminology, but it does not solve the specified synthetic data overwhelms minority real-world edge cases failure. The matching remediation is: Rebalance curated synthetic and real cases to preserve rare operational scenarios and evaluate on an untouched real-world edge-case set.
Question 244
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML training pipeline logs losses successfully but fails its packaging stage because MLflow autologging was configured with model logging disabled and no manual model artifact was saved. The operator must safeguard training reproducibility and serving continuity. Which acceptance test shows the AI operations defect is corrected?
- A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.
- All workers join one process group and finish a representative multi-node training step without broad public inbound exposure.
- Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable.
- The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path.
Explanation
Correct Answer
D:The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path. Metrics and model artifacts are separately tracked by MLflow, so useful loss curves do not imply a registered loadable model exists. a direct corrective action is to enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
Incorrect Answers
A:A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. That addresses a different configuration issue rather than the main requirement. Verify instead: The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path.
B:All workers join one process group and finish a representative multi-node training step without broad public inbound exposure. That addresses a different configuration issue rather than the main requirement. Verify instead: The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path.
C:Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable. That addresses a different configuration issue rather than the main requirement. Verify instead: The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path.
Question 245
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A Python scoring pipeline passes locally but fails on managed compute after a dependency release changes a library API because its Azure ML environment specifies unbounded package versions. The team must preserve approved access, model provenance and private network constraints. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema.
- Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance.
- Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback.
- Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
- Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
Explanation
Correct Answers
C:Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. This is the most relevant evidence for training environment lacks pinned package versions. Azure ML environment assets package execution dependencies; reproducibility requires explicit versions rather than assuming the newest package is compatible. The matching controlled remediation is: Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
E:Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment. This targets training environment lacks pinned package versions. Azure ML environment assets package execution dependencies; reproducibility requires explicit versions rather than assuming the newest package is compatible. Verify the failure through: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. Validate success with: The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution.
Incorrect Answers
A: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 training environment lacks pinned package versions. First examine: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. Then correct: Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
B:Inspect the data asset version resolution, pipeline input expression, snapshot timestamps, storage content hashes and previous run provenance. This is associated with versionless dataset reference breaks reproducibility, not the essential evidence-and-fix pair for training environment lacks pinned package versions. First examine: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. Then correct: Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
D:Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow. This is associated with github action uses persistent azure client secret, not the essential evidence-and-fix pair for training environment lacks pinned package versions. First examine: Compare environment image digest, Conda or pip dependencies, Docker build logs, locally resolved versions and job import traceback. Then correct: Publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment.
Question 246
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A global customer-support agent project is provisioned in a region that does not offer the selected foundation model deployment type, preventing its evaluation pipeline from starting. The deployment must retain governed identities, endpoint contracts and auditable release history. What measured outcome validates the solution while preserving the stated constraints?
- The front end scores authorized requests but cannot create, delete or reconfigure model deployments.
- Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
- Every production prompt version resolves to a reviewed commit and a failed change can be rolled back without copying an unknown portal draft.
- The project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback.
Explanation
Correct Answer
D:The project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback. A Foundry project depends on its parent resource location and model/service availability; creating a project does not guarantee every model is deployable there. a direct corrective action is to deploy the governed Foundry resource and project in a supported compliant region with an available model option.
Incorrect Answers
A:The front end scores authorized requests but cannot create, delete or reconfigure model deployments. That addresses a different configuration issue rather than the main requirement. Verify instead: The project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback.
B: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 project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback.
C: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 project invokes the approved model endpoint and meets required data-residency policy without an unapproved region fallback.
Question 247
During a retrieval or model-customization performance review, the following condition occurs: A domain RAG service changes the query embedding model but keeps document vectors created by a different model, producing irrelevant similarity matches. The change must keep citations, privacy and previously approved behavior intact. Which TWO complementary choices identify the issue and correct it? Select TWO.
- Compare query and index embedding model versions, vector dimensions, index schema, retrieval score distributions and migration logs.
- Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall.
- Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
- Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content.
- Expand representative domain pairs and negatives, apply appropriate embedding model adaptation and retain a separate general-language retrieval evaluation.
Explanation
Correct Answers
A:Compare query and index embedding model versions, vector dimensions, index schema, retrieval score distributions and migration logs. This is the most relevant evidence for 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. The matching controlled 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. This matters here because a domain RAG service changes the query embedding model but keeps document vectors created by a different model,….
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. This matters here because a domain RAG service changes the query embedding model but keeps document vectors created by a different model,….
Incorrect Answers
B:Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. This is associated with rag similarity threshold filters all relevant evidence, not the essential evidence-and-fix pair for embedding model replaced without reindexing stored vectors. First examine: Compare query and index embedding model versions, vector dimensions, index schema, retrieval score distributions and migration logs. Then correct: Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
D:Generate sanitized synthetic patterns from approved nonidentifying templates and screen outputs for memorized or copied private content. This is associated with synthetic training examples copy private customer identifiers, not the essential evidence-and-fix pair for embedding model replaced without reindexing stored vectors. First examine: Compare query and index embedding model versions, vector dimensions, index schema, retrieval score distributions and migration logs. Then correct: Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
E:Expand representative domain pairs and negatives, apply appropriate embedding model adaptation and retain a separate general-language retrieval evaluation. This is associated with specialized embedding adaptation overfits small terminology set, not the essential evidence-and-fix pair for embedding model replaced without reindexing stored vectors. First examine: Compare query and index embedding model versions, vector dimensions, index schema, retrieval score distributions and migration logs. Then correct: Re-embed and reindex the document corpus with a compatible versioned embedding model, or keep query embeddings pinned to the existing index model.
Question 248
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A pipeline component is published for reuse but includes a hard-coded workspace datastore URI, causing executions in a second workspace to read an unavailable path. The team must preserve approved access, model provenance and private network constraints. Which investigation best verifies the cause before changing production configuration?
- Check the component's registry name and version, target workspace identity, registry read permissions and referenced environment dependencies.
- Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest.
- Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error.
- Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.
Explanation
Correct Answer
D:Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations. This is the most relevant evidence for reusable component hardcodes workspace-specific asset path. Portable Azure ML components describe computation and typed interfaces rather than assuming a single workspace's storage layout. The matching controlled remediation is: Replace embedded workspace-specific paths with parameterized, typed data inputs and bind them explicitly in each consuming pipeline.
Incorrect Answers
A:Check the component's registry name and version, target workspace identity, registry read permissions and referenced environment dependencies. This would investigate registry model asset not available to second workspace rather than the documented reusable component hardcodes workspace-specific asset path issue. The relevant investigation is: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.
B:Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest. This would investigate azure ml workspace deployed in the wrong subscription rather than the documented reusable component hardcodes workspace-specific asset path issue. The relevant investigation is: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.
C:Compare both component input/output interface schemas, YAML bindings, produced artifacts and the specific Azure ML pipeline validation error. This would investigate pipeline component output type mismatches consumer rather than the documented reusable component hardcodes workspace-specific asset path issue. The relevant investigation is: Inspect component YAML for workspace IDs, hard-coded URIs, parameter definitions and actual target workspace data asset registrations.
Question 249
While preparing a secure Foundry model or agent release, 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 remediation must meet enterprise access and reliability requirements without a broad bypass. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.
- Compare project connection configuration, model deployment resource ID, endpoint URL, deployment name and invocation authorization.
- Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
- Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events.
- Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.
- Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.
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.
D: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.
Incorrect Answers
B:Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This is associated with few-shot prompt examples bias outputs toward one subgroup, not the essential evidence-and-fix pair for 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.
C:Inspect IaC parameter history, deployment logs, credential usage, Key Vault references and access audit events. This is associated with foundry infrastructure parameters embed a secret in source repository, 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:Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment. This is associated with azure cli foundry setup assumes existing model quota, 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 250
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A Foundry agent invokes its LLM successfully but receives access denied when querying an Azure AI Search index because the assigned managed identity lacks search data reader rights. The deployment must retain governed identities, endpoint contracts and auditable release history. What approved correction resolves the failure without modifying unrelated healthy services?
- Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection.
- Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.
- Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates.
- Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
Explanation
Correct Answer
B:Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration. This targets agent runtime managed identity cannot read retrieval data. Foundry model access and Azure AI Search data-plane authorization are separate permission boundaries for a retrieval-augmented agent. Verify the failure through: Inspect runtime managed identity, search service RBAC and index permissions, connector authentication, audit failures and client requests. Validate success with: Authorized agent queries retrieve permitted indexed chunks while direct access to unrelated indexes remains denied.
Incorrect Answers
A:Bind the application to the reviewed compatible model deployment in the correct Foundry project/resource and validate the connection. This could address foundry project links to wrong deployed model resource, but it does not solve the specified agent runtime managed identity cannot read retrieval data failure. The matching remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.
C:Separate governed development and production environments with distinct project configuration, least-privilege credentials and deployment gates. This could address foundry environment mixes development and production agent resources, but it does not solve the specified agent runtime managed identity cannot read retrieval data failure. The matching remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.
D:Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion. This could address prompt variant comparison measures fluency not task success, but it does not solve the specified agent runtime managed identity cannot read retrieval data failure. The matching remediation is: Grant the narrowly scoped search data access role to the correct agent identity and use identity-based connection configuration.