Microsoft AI-300 Practice Test 9
Question 80
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. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags.
- Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
- Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results.
- Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.
Explanation
Correct Answer
B: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.
Incorrect Answers
A:Review usage logs for chat and embedding deployments, prompt/output token categories, query frequency, indexing cycles and resource billing tags. This would investigate token cost report omits embedding requests rather than the documented prompt truncation strategy increases generated-token spend issue. The relevant investigation is: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
C:Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results. This would investigate foundry continuous evaluation ignores production deployment version rather than the documented prompt truncation strategy increases generated-token spend issue. The relevant investigation is: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
D:Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. This would investigate multi-turn agent evaluation uses isolated last message only rather than the documented prompt truncation strategy increases generated-token spend issue. The relevant investigation is: Inspect prompt token composition, repeated static sections, retrieval result counts, cache opportunities and groundedness metrics.
Question 81
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A model-serving infrastructure workflow deploys directly to production on any commit because the GitHub Actions job lacks protected environment reviewers and branch controls. The team must preserve approved access, model provenance and private network constraints. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
- Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
- Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records.
- Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands.
- Recreate or provision the workspace in the approved subscription and region through the reviewed deployment pipeline, preserving authorized datasets separately.
Explanation
Correct Answers
B:Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate. This targets github deployment pipeline omits secure environment approvals. Automated CI/CD is not equivalent to authorized production promotion; environment and identity gates must restrict high-impact stages. Verify the failure through: Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. Validate success with: A reviewed release can deploy production resources, but an unreviewed branch workflow cannot obtain production deployment rights.
C:Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. This is the most relevant evidence for github deployment pipeline omits secure environment approvals. Automated CI/CD is not equivalent to authorized production promotion; environment and identity gates must restrict high-impact stages. The matching controlled remediation is: Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
Incorrect Answers
A:Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This is associated with notebook merge bypasses protected evaluation tests, not the essential evidence-and-fix pair for github deployment pipeline omits secure environment approvals. First examine: Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. Then correct: Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
D:Require explicit subscription and resource group targeting and preflight assertions before executing repeatable workspace deployment commands. This is associated with azure cli deployment silently targets sandbox defaults, not the essential evidence-and-fix pair for github deployment pipeline omits secure environment approvals. First examine: Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. Then correct: Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
E:Recreate or provision the workspace in the approved subscription and region through the reviewed deployment pipeline, preserving authorized datasets separately. This is associated with azure ml workspace deployed in the wrong subscription, not the essential evidence-and-fix pair for github deployment pipeline omits secure environment approvals. First examine: Inspect workflow trigger, environment configuration, protected branch policies, required reviewers and current deployment audit records. Then correct: Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
Question 82
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A data scientist runs a local notebook intending to log results to a governed Azure ML workspace, but the MLflow tracking URI still points to an earlier sandbox workspace. The resolution must preserve quality gates, documented artifacts and rollback options. Which production-safe remediation should the engineer apply to this AI workflow?
- Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold.
- Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment.
- Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features.
- Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
Explanation
Correct Answer
D:Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This targets mlflow tracking uri sends notebook runs to wrong workspace. An interactive MLflow process can log to whichever tracking server is configured; Azure workspace selection is not inferred from the notebook file's location. Verify the failure through: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Validate success with: The next test run appears only under the intended workspace with its parameters and model artifacts attached.
Incorrect Answers
A:Use a documented holdout or cross-validation-based model selection procedure and require a production-relevant promotion threshold. This could address new candidate chosen from training instead of validation results, but it does not solve the specified mlflow tracking uri sends notebook runs to wrong workspace failure. The matching remediation is: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
B:Fix the image or artifact mount path and ensure init() loads the registered model before promoting the deployment. This could address endpoint deployment health probe fails before model initialization, but it does not solve the specified mlflow tracking uri sends notebook runs to wrong workspace failure. The matching remediation is: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
C:Remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This could address automated ml experiment uses leakage feature, but it does not solve the specified mlflow tracking uri sends notebook runs to wrong workspace failure. The matching remediation is: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
Question 83
As an AI operations team checks production agent evaluation evidence, 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 workflow must produce measurable quality, safety and performance evidence. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Inspect tokens per request, input/output token ratios, concurrency, throttling status and model deployment quota.
- Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles.
- Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs.
- Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records.
Explanation
Correct Answer
C:Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs. This is the most relevant evidence for 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. The matching controlled remediation is: Enable scoped distributed tracing for agent and tool steps with error tags and privacy-safe identifiers.
Incorrect Answers
A:Inspect tokens per request, input/output token ratios, concurrency, throttling status and model deployment quota. This would investigate genai throughput report mixes responses and tokens rather than the documented agent traces omit downstream tool failure reason issue. The relevant investigation is: Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs.
B:Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. This would investigate generation latency spike blamed on retrieval without breakdown rather than the documented agent traces omit downstream tool failure reason issue. The relevant investigation is: Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs.
D:Inspect evaluation workflow outputs, release conditions, metric thresholds, CI job failure behavior and promotion records. This would investigate evaluation workflow fails to block degraded agent deployment rather than the documented agent traces omit downstream tool failure reason issue. The relevant investigation is: Inspect agent instrumentation, OpenTelemetry trace propagation, tool span durations, error attributes and correlated resource logs.
Question 84
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A repeated model-training command yields unpredictably different evaluation results because its random seed and dataset split are not fixed or logged across Azure ML runs. The operator must safeguard training reproducibility and serving continuity. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.
- Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata.
- Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
- Inspect class prevalence, AutoML primary metric, confusion matrix, recall and precision of candidate runs and business error costs.
Explanation
Correct Answer
C:Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes. This is the most relevant evidence for training script ignores reproducible seed and input contract. ML model reproducibility depends on data, environment and randomness control; a single identical command string does not fix every stochastic dependency. The matching controlled remediation is: Implement feasible deterministic seeding and record input data split and environment versions for each run with acknowledged nondeterministic GPU constraints.
Incorrect Answers
A:Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training. This would investigate feature retrieval specification missing from registered model rather than the documented training script ignores reproducible seed and input contract issue. The relevant investigation is: Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
B:Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata. This would investigate exploration notebook reads production data without reproducible snapshot rather than the documented training script ignores reproducible seed and input contract issue. The relevant investigation is: Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
D:Inspect class prevalence, AutoML primary metric, confusion matrix, recall and precision of candidate runs and business error costs. This would investigate automl primary metric does not match rare-event goal rather than the documented training script ignores reproducible seed and input contract issue. The relevant investigation is: Inspect Python RNG seeding, framework deterministic settings, dataset split creation, logged run parameters and artifact hashes.
Question 85
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A credit model's offline validation looks excellent because feature retrieval joins include transactions occurring after the intended historical prediction timestamp. The operator must safeguard training reproducibility and serving continuity. Which investigation best verifies the cause before changing production configuration?
- Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback.
- Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification.
- Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process.
- Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness.
Explanation
Correct Answer
B:Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification. This is the most relevant evidence for online feature retrieval pulls values from after prediction time. Feature retrieval contracts must prevent future information from leaking into historical training and evaluation data. The matching controlled remediation is: Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A credit….
Incorrect Answers
A:Inspect MLflow model directory, MLmodel flavors, inferred signature, environment requirements and endpoint container startup traceback. This would investigate mlflow registry artifact cannot load on serving target rather than the documented online feature retrieval pulls values from after prediction time issue. The relevant investigation is: Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A credit….
C:Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. This would investigate mlflow tracking uri sends notebook runs to wrong workspace rather than the documented online feature retrieval pulls values from after prediction time issue. The relevant investigation is: Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification.
D:Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness. This would investigate responsible ai evaluation omits demographic cohort slices rather than the documented online feature retrieval pulls values from after prediction time issue. The relevant investigation is: Inspect point-in-time feature joins, feature update timestamps, event time, training label time and registered retrieval specification.
Question 86
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A research group leaves dedicated Azure ML compute instances running overnight although the instances are idle and only used during scheduled notebook sessions. The team must preserve approved access, model provenance and private network constraints. What approved correction resolves the failure without modifying unrelated healthy services?
- Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
- Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
- Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
- Require protected pull requests and automated component tests before changes to production training code are merged.
Explanation
Correct Answer
A:Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances. This targets interactive compute instances remain running while unused. Compute instances and managed compute clusters have different operating models; idle instance cost is not eliminated by an unrelated model deployment setting. Verify the failure through: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. Validate success with: Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.
Incorrect Answers
B:Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This could address compute cluster cannot allocate requested gpu quota, but it does not solve the specified interactive compute instances remain running while unused failure. The matching remediation is: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
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 interactive compute instances remain running while unused failure. The matching remediation is: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
D:Require protected pull requests and automated component tests before changes to production training code are merged. This could address notebook merge bypasses protected evaluation tests, but it does not solve the specified interactive compute instances remain running while unused failure. The matching remediation is: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
Question 87
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training job reads a similarly named blob container containing last quarter's features because its Azure ML datastore URI targets the staging location rather than the approved production store. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
- Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum.
- Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest.
- Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
- Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
Explanation
Correct Answers
B:Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. This is the most relevant evidence for datastore uri selects the incorrect storage container. A datastore connection and data asset version identify where training inputs come from; paths must be validated independently from authentication success. The matching controlled remediation is: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training job….
E:Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This targets datastore uri selects the incorrect storage container. A datastore connection and data asset version identify where training inputs come from; paths must be validated independently from authentication success. Verify the failure through: Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. Validate success with: The job consumes the intended dataset version and staging files are not silently mixed into production runs. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training job….
Incorrect Answers
A:Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This is associated with compute cluster cannot allocate requested gpu quota, not the essential evidence-and-fix pair for datastore uri selects the incorrect storage container. First examine: Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. Then correct: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training job….
C:Compare the workspace resource ID, subscription tenant, management group policy assignments, linked resources and team deployment manifest. This is associated with azure ml workspace deployed in the wrong subscription, not the essential evidence-and-fix pair for datastore uri selects the incorrect storage container. First examine: Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. Then correct: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
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 datastore uri selects the incorrect storage container. First examine: Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. Then correct: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
Question 88
During a retrieval or model-customization performance review, the following condition occurs: A RAG search index blends keyword and vector results but weights retired versions of a procedure equally with current publications, so old policy text appears first. The change must keep citations, privacy and previously approved behavior intact. Which acceptance test shows the AI operations defect is corrected?
- Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users.
- The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation.
- Evaluation questions about eligibility include the correct exception and still return concise supported citations.
- Previously unseen product queries are monitored and subsequent vetted versions meet current quality targets without erasing old task competence.
Explanation
Correct Answer
A:Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users. Hybrid scoring does not inherently enforce document freshness or authoritative version; metadata filtering is a separate ranking control. a direct corrective action is to filter or downrank superseded records before hybrid retrieval and use governed version metadata for source selection. This matters here because a RAG search index blends keyword and vector results but weights retired versions of a procedure equally with….
Incorrect Answers
B:The selected retrieval strategy meets groundedness and task-success gates rather than optimizing click-through in isolation. That addresses a different configuration issue rather than the main requirement. Verify instead: Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users.
C:Evaluation questions about eligibility include the correct exception and still return concise supported citations. That addresses a different configuration issue rather than the main requirement. Verify instead: Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users.
D:Previously unseen product queries are monitored and subsequent vetted versions meet current quality targets without erasing old task competence. That addresses a different configuration issue rather than the main requirement. Verify instead: Current authoritative procedures rank ahead of retired versions for evaluated test queries while archival retrieval remains available to approved users. This matters here because a RAG search index blends keyword and vector results but weights retired versions of a procedure equally with….
Question 89
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A distributed deep-learning job remains queued because the Azure ML compute cluster requests more regional GPU-family vCPU quota than the subscription currently has. The change must remain limited to authorized workspaces and avoid unreviewed production impact. What approved correction resolves the failure without modifying unrelated healthy services?
- Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
- Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration.
- Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
- Scope an approved least-privilege Azure ML role to the intended resource group or workspace and remove the broad inherited Contributor grant.
Explanation
Correct Answer
C:Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This targets compute cluster cannot allocate requested gpu quota. Azure ML computes draw from Azure regional VM family quota; declaring a cluster does not reserve unlimited GPU instances. Verify the failure through: Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. Validate success with: The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement.
Incorrect Answers
A:Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This could address aml managed network blocks model registry egress, but it does not solve the specified compute cluster cannot allocate requested gpu quota failure. The matching remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
B:Link the authorized Key Vault or repair supported access to the intended secret store through the correct workspace deployment configuration. This could address workspace dependencies point to unrelated secrets vault, but it does not solve the specified compute cluster cannot allocate requested gpu quota failure. The matching remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
D: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 compute cluster cannot allocate requested gpu quota failure. The matching remediation is: Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
Question 90
During a Microsoft Foundry generative AI deployment review, the following condition occurs: An expense processing agent needs to interpret invoice images but the deployed text-only model endpoint cannot accept image content in its request schema. The deployment must retain governed identities, endpoint contracts and auditable release history. Which targeted Azure AI operations change best addresses the documented problem?
- Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.
- Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials.
- Compare candidate prompts using task-specific relevance and groundedness metrics alongside fluency before promotion.
- Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
Explanation
Correct Answer
D:Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step. This targets vision input sent to text-only foundation model. Model capability and endpoint payload contracts determine which modalities can be processed; a text-only deployment cannot reliably infer pixels. Verify the failure through: Inspect deployed model modalities, model card capabilities, payload content types, supported API version and failed inference responses. Validate success with: A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.
Incorrect Answers
A:Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review. This could address provisioned deployment pays for idle unused capacity, but it does not solve the specified vision input sent to text-only foundation model failure. The matching remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
B:Configure the supported identity-based inference grant and connection details for the production workload without sharing personal credentials. This could address serverless model endpoint unavailable to chosen identity, but it does not solve the specified vision input sent to text-only foundation model failure. The matching remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
C: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 vision input sent to text-only foundation model failure. The matching remediation is: Select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.