Microsoft AI-300 Practice Test 79
Question 780
While preparing a secure Foundry model or agent release, the following condition occurs: An API service rolls back prompt text after a deployment incident but leaves the incompatible new foundation-model version in place, so tool-call formatting errors persist. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses.
- Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities.
- Inspect input/output token volume, peak concurrent requests, provisioned throughput allocation, throttling codes and deployment latency percentiles.
- Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
Explanation
Correct Answer
D:Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This is the most relevant evidence for prompt contract rollback ignores associated model version. A generative application behavior depends on versioned combinations of model, prompts and tools, not any single text template. The matching controlled remediation is: Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An API service rolls back….
Incorrect Answers
A:Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. This would investigate vision input sent to text-only foundation model rather than the documented prompt contract rollback ignores associated model version issue. The relevant investigation is: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: An API service rolls back….
B:Audit Foundry network ACLs, private endpoint connections, VNet peerings, firewall rules and effective caller identities. This would investigate network allowlist exposes production model endpoint to test subnet rather than the documented prompt contract rollback ignores associated model version issue. The relevant investigation is: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
C:Inspect input/output token volume, peak concurrent requests, provisioned throughput allocation, throttling codes and deployment latency percentiles. This would investigate provisioned throughput capacity insufficient at peak traffic rather than the documented prompt contract rollback ignores associated model version issue. The relevant investigation is: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
Question 781
While optimizing a production RAG or fine-tuned model service, the following condition occurs: An enterprise assistant's new retrieval strategy raises link clicks but adds hallucinated recommendations, while the experiment reports only engagement as the success metric. The resulting model must meet held-out quality and security criteria. What approved correction resolves the failure without modifying unrelated healthy services?
- Refresh a governed evaluation set with recent terminology and trigger controlled retraining only after measuring sustained quality regression.
- Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection.
- Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking.
- Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
Explanation
Correct Answer
D:Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails. This targets rag a/b experiment judges only click-through not factuality. Interaction metrics do not establish answer accuracy; retrieval optimization needs labels and safety/quality measurements. Verify the failure through: Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents. Validate success with: The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation. This matters here because while optimizing a production RAG or fine-tuned model service, the following condition occurs: An enterprise….
Incorrect Answers
A: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 rag a/b experiment judges only click-through not factuality failure. The matching remediation is: Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
B:Filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This could address hybrid retrieval double-counts outdated documents, but it does not solve the specified rag a/b experiment judges only click-through not factuality failure. The matching remediation is: Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
C:Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking. This could address pure vector search misses exact regulatory clause codes, but it does not solve the specified rag a/b experiment judges only click-through not factuality failure. The matching remediation is: Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
Question 782
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A notebook computes features from a mutable SQL export every time it runs, but the submitted model job cannot reproduce yesterday's feature distribution. The resolution must preserve quality gates, documented artifacts and rollback options. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Review AutoML featurization, data collection timestamps, target leakage candidates, split strategy and training-versus-production feature availability.
- Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs.
- Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata.
- Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook.
Explanation
Correct Answer
C:Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata. This is the most relevant evidence for exploration notebook reads production data without reproducible snapshot. Notebook experimentation is flexible but reliable model comparison requires stable, recorded data inputs rather than live mutable queries. The matching controlled remediation is: Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A notebook….
Incorrect Answers
A:Review AutoML featurization, data collection timestamps, target leakage candidates, split strategy and training-versus-production feature availability. This would investigate automated ml experiment uses leakage feature rather than the documented exploration notebook reads production data without reproducible snapshot issue. The relevant investigation is: Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata.
B:Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. This would investigate autologging excludes required model artifact rather than the documented exploration notebook reads production data without reproducible snapshot issue. The relevant investigation is: Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A notebook….
D:Examine model registry history, artifact retention rules, endpoint references, promotion record and rollback runbook. This would investigate incident rollback artifact was deleted instead of archived rather than the documented exploration notebook reads production data without reproducible snapshot issue. The relevant investigation is: Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata.
Question 783
During a retrieval or model-customization performance review, the following condition occurs: An enterprise assistant's new retrieval strategy raises link clicks but adds hallucinated recommendations, while the experiment reports only engagement as the success metric. The change must keep citations, privacy and previously approved behavior intact. Which investigation best verifies the cause before changing production configuration?
- Examine question-set provenance, tuning history, held-out set separation, document version and evaluator configuration.
- Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence.
- Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.
- Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents.
Explanation
Correct Answer
D:Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents. This is the most relevant evidence for rag a/b experiment judges only click-through not factuality. Interaction metrics do not establish answer accuracy; retrieval optimization needs labels and safety/quality measurements. The matching controlled remediation is: Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails. This matters here because an enterprise assistant's new retrieval strategy raises link clicks but adds hallucinated recommendations, while the….
Incorrect Answers
A:Examine question-set provenance, tuning history, held-out set separation, document version and evaluator configuration. This would investigate offline rag evaluator leaks training questions into test set rather than the documented rag a/b experiment judges only click-through not factuality issue. The relevant investigation is: Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents.
B:Review live prompt distribution, new product identifier coverage, task quality metrics, fine-tuned model version and evaluation refresh cadence. This would investigate fine-tune evaluation lacks drift checks for new customer terminology rather than the documented rag a/b experiment judges only click-through not factuality issue. The relevant investigation is: Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents.
C:Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata. This would investigate hybrid retrieval double-counts outdated documents rather than the documented rag a/b experiment judges only click-through not factuality issue. The relevant investigation is: Review A/B cohort assignment, groundedness samples, relevance labels, business success measures and unsupported-claim incidents. This matters here because an enterprise assistant's new retrieval strategy raises link clicks but adds hallucinated recommendations, while the….
Question 784
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A customer assistant must handle Turkish and Arabic queries, yet the chosen model is approved based only on English benchmark scores and performs poorly in the required languages. 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?
- Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
- Inspect workflow identity claims, login failure logs, secret references, federated identity options and target resource permissions.
- Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses.
- Inspect endpoint authentication modes, deployment authorization, production managed identity, assigned roles and failed token exchanges.
Explanation
Correct Answer
A:Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements. This is the most relevant evidence for multilingual model selection fails target-language quality. Model selection for a multilingual workload requires evaluation in the actual languages and use cases rather than generic model rankings. The matching controlled remediation is: Compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
Incorrect Answers
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 multilingual model selection fails target-language quality issue. The relevant investigation is: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
C:Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. This would investigate vision input sent to text-only foundation model rather than the documented multilingual model selection fails target-language quality issue. The relevant investigation is: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
D:Inspect endpoint authentication modes, deployment authorization, production managed identity, assigned roles and failed token exchanges. This would investigate serverless model endpoint unavailable to chosen identity rather than the documented multilingual model selection fails target-language quality issue. The relevant investigation is: Review language-specific acceptance tests, deployed model support, retrieval data language coverage, candidate evaluation results and safety requirements.
Question 785
During a Microsoft Foundry generative AI deployment review, 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 deployment must retain governed identities, endpoint contracts and auditable release history. Which targeted Azure AI operations change best addresses the documented problem?
- Migrate the workflow to supported managed or federated identity, or rotate the credential through approved secret management and verify minimal access.
- Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
- Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.
- Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
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. This matters here because a project deployment script succeeds in creating resources but fails when attempting model deployment because the….
Incorrect Answers
A: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 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: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 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:Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants. This could address foundry administrator role granted to consumer application, 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 786
During a Microsoft Foundry generative AI deployment review, the following condition occurs: An API service rolls back prompt text after a deployment incident but leaves the incompatible new foundation-model version in place, so tool-call formatting errors persist. The deployment must retain governed identities, endpoint contracts and auditable release history. Which targeted Azure AI operations change best addresses the documented problem?
- Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.
- Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
- Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.
- 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:Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow. This targets prompt contract rollback ignores associated model version. A generative application behavior depends on versioned combinations of model, prompts and tools, not any single text template. Verify the failure through: Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. Validate success with: The last stable response and tool-call contracts are recovered across representative transactions without rebuilding application data.
Incorrect Answers
A:Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion. This could address foundry deployment alias changes model behavior unexpectedly, but it does not solve the specified prompt contract rollback ignores associated model version failure. The matching remediation is: Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.
B:Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This could address provisioned model update exceeds regional capacity ceiling, but it does not solve the specified prompt contract rollback ignores associated model version failure. The matching remediation is: Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.
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 contract rollback ignores associated model version failure. The matching remediation is: Restore the complete compatible model, prompt and tool schema release manifest and retest its evaluated workflow.
Question 787
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A Python training script writes its trained pickle file only to an ephemeral worker directory, so the Azure ML submitted command job ends successfully but the model registration stage finds no artifact. The operator must safeguard training reproducibility and serving continuity. Which investigation best verifies the cause before changing production configuration?
- Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input.
- Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics.
- Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
- Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage.
Explanation
Correct Answer
A:Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input. This is the most relevant evidence for training job does not persist output artifacts. Managed job workers may be ephemeral; outputs must be explicitly persisted through Azure ML declared artifacts rather than private local filesystem paths. The matching controlled remediation is: Write the model into the declared Azure ML job output path and track the versioned artifact used in registration. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A Python….
Incorrect Answers
B:Review training and validation learning curves, selection rule, dataset splits and registered model candidate metrics. This would investigate new candidate chosen from training instead of validation results rather than the documented training job does not persist output artifacts issue. The relevant investigation is: Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A Python….
C:Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This would investigate retired model kept active as discoverable deployment candidate rather than the documented training job does not persist output artifacts issue. The relevant investigation is: Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input.
D:Inspect component reuse settings, input asset version, code and environment fingerprints, effective parameters and cached job lineage. This would investigate pipeline cache reuses stale transform artifact rather than the documented training job does not persist output artifacts issue. The relevant investigation is: Review job output mappings, script save path, managed output directories, job artifacts and downstream register-component input.
Question 788
As an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot repeats its complete policy corpus in every prompt, increasing token costs and latency, although only a few retrieved paragraphs are relevant to each answer. The workflow must produce measurable quality, safety and performance evidence. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.
- Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
- Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
- Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples.
- Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
- Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads.
Explanation
Correct Answers
A:Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. This is the most relevant evidence for prompt truncation strategy increases generated-token spend. Context volume affects token cost and latency; sending unnecessary text on every request is not equivalent to more reliable grounding. The matching controlled remediation is: Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot….
C:Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples. This targets prompt truncation strategy increases generated-token spend. Context volume affects token cost and latency; sending unnecessary text on every request is not equivalent to more reliable grounding. Verify the failure through: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. Validate success with: Average tokens per successful request falls while groundedness and task success remain within accepted limits. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot….
Incorrect Answers
B:Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand. This is associated with genai throughput report mixes responses and tokens, not the essential evidence-and-fix pair for prompt truncation strategy increases generated-token spend. First examine: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. Then correct: Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples.
D:Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution. This is associated with content safety evaluation omits prompt injection tests, not the essential evidence-and-fix pair for prompt truncation strategy increases generated-token spend. First examine: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. Then correct: Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples.
E:Examine trace field filters, application secret handling, workspace RBAC, log retention and representative captured payloads. This is associated with debug traces leak secrets and retrieved personal records, not the essential evidence-and-fix pair for prompt truncation strategy increases generated-token spend. First examine: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics. Then correct: Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples. This matters here because as an AI operations team checks production agent evaluation evidence, the following condition occurs: A support bot….
Question 789
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new Azure ML workspace starts but managed training cannot retrieve approved secrets because deployment references a Key Vault belonging to an unrelated project. The change must remain limited to authorized workspaces and avoid unreviewed production impact. What measured outcome validates the solution while preserving the stated constraints?
- The production team creates and reads workspace assets under the correct policy scope while sandbox users cannot administer production resources.
- A validation job loads the intended features with the declared schema and rejects incompatible input files.
- A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible.
- The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement.
Explanation
Correct Answer
C:A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible. A workspace can exist while supporting Key Vault, storage or monitoring dependencies are incorrectly associated; successful resource creation alone is not end-to-end readiness. a direct corrective action is to link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new Azure ML….
Incorrect Answers
A:The production team creates and reads workspace assets under the correct policy scope while sandbox users cannot administer production resources. That addresses a different configuration issue rather than the main requirement. Verify instead: A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new Azure ML….
B:A validation job loads the intended features with the declared schema and rejects incompatible input files. That addresses a different configuration issue rather than the main requirement. Verify instead: A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible.
D:The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement. That addresses a different configuration issue rather than the main requirement. Verify instead: A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible.
Question 790
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 production-safe remediation should the engineer apply to this AI workflow?
- Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
- Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.
- Deploy the governed Foundry resource and project in a supported compliant region with an available model option.
- Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
Explanation
Correct Answer
A:Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests. This targets interactive inference deployed on unsuitable batch-style compute. Generative chat workloads ordinarily require online serving semantics; scheduled batch compute cannot satisfy an interactive response deadline. Verify the failure through: Check application response SLA, workload concurrency, chosen Foundry model endpoint type and current request queuing behavior. Validate success with: Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A chat assistant must….
Incorrect Answers
B:Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion. This could address foundry deployment alias changes model behavior unexpectedly, but it does not solve the specified interactive inference deployed on unsuitable batch-style compute failure. The matching remediation is: Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
C: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 interactive inference deployed on unsuitable batch-style compute failure. The matching remediation is: Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.
D:Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step. This could address vision input sent to text-only foundation model, but it does not solve the specified interactive inference deployed on unsuitable batch-style compute failure. The matching remediation is: Deploy an available supported online/serverless or managed model endpoint sized for synchronous conversational requests.