Microsoft AI-300 Practice Test 85
Question 840
During a retrieval or model-customization performance review, the following condition occurs: An operations chatbot answers 'I cannot find it' to precise internal procedure questions because its vector search similarity threshold was raised above scores returned by the relevant documents. The change must keep citations, privacy and previously approved behavior intact. What measured outcome validates the solution while preserving the stated constraints?
- Candidate rankings remain robust on previously unseen held-out queries and the acceptance test cannot be tuned after results are disclosed.
- Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely.
- Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase.
- The model improves typical coverage while retaining or improving measured accuracy for rare high-impact cases.
Explanation
Correct Answer
C:Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase. Vector similarity thresholds control recall and precision; a threshold chosen without validation can suppress even the best available evidence. a direct corrective action is to calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise. This matters here because an operations chatbot answers 'I cannot find it' to precise internal procedure questions because its vector search….
Incorrect Answers
A:Candidate rankings remain robust on previously unseen held-out queries and the acceptance test cannot be tuned after results are disclosed. That addresses a different configuration issue rather than the main requirement. Verify instead: Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase. This matters here because an operations chatbot answers 'I cannot find it' to precise internal procedure questions because its vector search….
B:Representative domain queries retrieve relevant passages with aligned embedding provenance and the old index can be rolled back safely. That addresses a different configuration issue rather than the main requirement. Verify instead: Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase.
D:The model improves typical coverage while retaining or improving measured accuracy for rare high-impact cases. That addresses a different configuration issue rather than the main requirement. Verify instead: Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase.
Question 841
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A feature-engineering change is merged directly to the main branch without running schema and leakage tests, and the next scheduled model training uses incompatible features. The team must preserve approved access, model provenance and private network constraints. Which acceptance test shows the AI operations defect is corrected?
- The approved branch deploys using short-lived federated tokens, and old client secrets can be revoked without breaking releases.
- Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access.
- The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution.
- A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence.
Explanation
Correct Answer
D:A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. a direct corrective action is to require protected pull requests and automated component tests before changes to production training code are merged. This matters here because a feature-engineering change is merged directly to the main branch without running schema and leakage tests, and the….
Incorrect Answers
A:The approved branch deploys using short-lived federated tokens, and old client secrets can be revoked without breaking releases. That addresses a different configuration issue rather than the main requirement. Verify instead: A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence. This matters here because a feature-engineering change is merged directly to the main branch without running schema and leakage tests, and the….
B:Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access. That addresses a different configuration issue rather than the main requirement. Verify instead: A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence.
C:The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution. That addresses a different configuration issue rather than the main requirement. Verify instead: A breaking feature change is rejected before deployment and approved commits are tied to passed evaluation evidence.
Question 842
During a Foundry generative AI quality and observability incident, the following condition occurs: A tool-enabled finance agent passes harmful-text screening but executes instructions inside a hostile retrieved web page because its safety suite contains no prompt-injection or tool-misuse cases. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison.
- Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
- Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
- Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
- Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations.
Explanation
Correct Answers
B:Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. This is the most relevant evidence for content safety evaluation omits prompt injection tests. Harmful-content detection alone does not test whether an agent obeys malicious instructions inserted into lower-trust retrieved material. The matching controlled remediation is: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution. This matters here because a tool-enabled finance agent passes harmful-text screening but executes instructions inside a hostile retrieved web….
D:Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution. This targets content safety evaluation omits prompt injection tests. Harmful-content detection alone does not test whether an agent obeys malicious instructions inserted into lower-trust retrieved material. Verify the failure through: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Validate success with: An adversarial document cannot cause unapproved transactions while authorized research questions still succeed. This matters here because a tool-enabled finance agent passes harmful-text screening but executes instructions inside a hostile retrieved web….
Incorrect Answers
A:Version the custom evaluator and recalibrate on a fixed reference set before using its scores for cross-version comparison. This is associated with custom evaluator silently changes its scoring rubric, not the essential evidence-and-fix pair for content safety evaluation omits prompt injection tests. First examine: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Then correct: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
C: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 content safety evaluation omits prompt injection tests. First examine: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Then correct: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
E:Examine evaluation records, chat history serialization, tool traces, single-turn versus multi-turn settings and representative failure conversations. This is associated with multi-turn agent evaluation uses isolated last message only, not the essential evidence-and-fix pair for content safety evaluation omits prompt injection tests. First examine: Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. Then correct: Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
Question 843
While preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot produces less useful answers for one customer cohort because all examples in its template come from a narrow set of customer situations. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which TWO complementary choices identify the issue and correct it? Select TWO.
- Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution.
- Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
- Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes.
- Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review.
- Validate quota in a preflight deployment stage and reduce or obtain approved capacity before creating the intended deployment.
Explanation
Correct Answers
A:Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. This is the most relevant evidence for few-shot prompt examples bias outputs toward one subgroup. Prompt variants can embed unrepresentative examples that change behavior; dataset diversity must be checked as carefully as model quality. The matching controlled remediation is: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot….
B:Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This targets few-shot prompt examples bias outputs toward one subgroup. Prompt variants can embed unrepresentative examples that change behavior; dataset diversity must be checked as carefully as model quality. Verify the failure through: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. Validate success with: Quality improves on relevant cohorts without exposing personal information or degrading approved common-case answers. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot….
Incorrect Answers
C:Compare experiment assignments, model deployment versions, test inputs, sample size, evaluator configuration and prompt hashes. This is associated with prompt a/b test uses different model versions in each arm, not the essential evidence-and-fix pair for few-shot prompt examples bias outputs toward one subgroup. First examine: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. Then correct: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot….
D:Remove direct identifiers from ongoing prompt examples, rotate affected credentials if necessary and use sanitized synthetic cases under review. This is associated with prompt repository references secret customer examples, not the essential evidence-and-fix pair for few-shot prompt examples bias outputs toward one subgroup. First examine: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. Then correct: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A loan-support chatbot….
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 few-shot prompt examples bias outputs toward one subgroup. First examine: Examine prompt example coverage, cohort-specific evaluation metrics, response error patterns and real query distribution. Then correct: Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
Question 844
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region, but a release pipeline attempts the new deployment before checking quota. The deployment must retain governed identities, endpoint contracts and auditable release history. Which targeted Azure AI operations change best addresses the documented problem?
- Replace broad management roles with the minimum supported inference access permission and remove redundant elevated grants.
- Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.
- Move the low-volume prototype to an appropriate supported consumption-based deployment or reduce provisioned capacity after review.
- Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
Explanation
Correct Answer
D:Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This targets provisioned model update exceeds regional capacity ceiling. Model capacity is region and deployment-type dependent; version upgrades cannot assume unused PTUs are available on demand. Verify the failure through: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. Validate success with: The model version upgrade completes without an outage or unauthorized cross-region processing. This matters here because a planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region,….
Incorrect Answers
A: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 provisioned model update exceeds regional capacity ceiling failure. The matching remediation is: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
B:Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements. This could address foundation model selected without required context window, but it does not solve the specified provisioned model update exceeds regional capacity ceiling failure. The matching remediation is: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This matters here because a planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region,….
C: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 provisioned model update exceeds regional capacity ceiling failure. The matching remediation is: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
Question 845
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A new Azure ML endpoint deployment is created for a new model but traffic is mistakenly set to 100% immediately, exposing all users before canary evaluation. The operator must safeguard training reproducibility and serving continuity. Which acceptance test shows the AI operations defect is corrected?
- Deployment reaches healthy readiness and handles a representative test request without restart loops.
- Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition.
- Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption.
- Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail.
Explanation
Correct Answer
D:Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail. Managed online endpoints can route traffic among deployments; safe releases require explicit percentages and stop criteria. a direct corrective action is to apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A new Azure ML….
Incorrect Answers
A:Deployment reaches healthy readiness and handles a representative test request without restart loops. That addresses a different configuration issue rather than the main requirement. Verify instead: Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A new Azure ML….
B:Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition. That addresses a different configuration issue rather than the main requirement. Verify instead: Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail.
C:Valid payloads return the correct prediction shape and malformed requests return documented validation errors rather than silent feature corruption. That addresses a different configuration issue rather than the main requirement. Verify instead: Canary traffic follows the approved fraction and rollback to the old deployment is possible when health thresholds fail. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A new Azure ML….
Question 846
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is rolled back to old weights but its scoring container still uses the new incompatible environment, so production errors continue after rollback. The resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?
- Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
- Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.
- Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.
- Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests.
Explanation
Correct Answer
A:Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This targets rollback cannot recover a previous environment version. A deployment's behavior depends on the whole inference package; changing model weights alone cannot undo incompatible runtime changes. Verify the failure through: Compare candidate and previous deployment model version, environment digest, scoring code, endpoint configuration and historical release manifest. Validate success with: A representative rollback test restores known-good predictions and endpoint health within the recovery target.
Incorrect Answers
B:Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This could address responsible ai evaluation omits demographic cohort slices, but it does not solve the specified rollback cannot recover a previous environment version failure. The matching remediation is: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
C:Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates. This could address canary rollout sends all traffic to unvalidated candidate, but it does not solve the specified rollback cannot recover a previous environment version failure. The matching remediation is: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
D:Align the published endpoint contract and client payload mapping, then deploy the reviewed scoring code and test representative requests. This could address endpoint scoring script expects wrong json schema, but it does not solve the specified rollback cannot recover a previous environment version failure. The matching remediation is: Restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights.
Question 847
During a retrieval or model-customization performance review, the following condition occurs: An operations chatbot answers 'I cannot find it' to precise internal procedure questions because its vector search similarity threshold was raised above scores returned by the relevant documents. The change must keep citations, privacy and previously approved behavior intact. What approved correction resolves the failure without modifying unrelated healthy services?
- Use an appropriate hybrid keyword-plus-vector search strategy with evaluated fusion and optional semantic reranking.
- Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
- Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures.
- Evaluate both retrievers with relevance, factual support and business outcomes under stable randomized cohorts and explicit guardrails.
Explanation
Correct Answer
B:Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise. This targets rag similarity threshold filters all relevant evidence. Vector similarity thresholds control recall and precision; a threshold chosen without validation can suppress even the best available evidence. Verify the failure through: Inspect top-k search scores, threshold, query normalization, relevant passages and test question recall. Validate success with: Previously missed procedure passages are retrieved and grounded answer quality improves without a large irrelevant context increase.
Incorrect Answers
A: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 similarity threshold filters all relevant evidence failure. The matching remediation is: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
C:Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This could address fine-tune production endpoint references deleted training artifact, but it does not solve the specified rag similarity threshold filters all relevant evidence failure. The matching remediation is: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
D: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 rag similarity threshold filters all relevant evidence failure. The matching remediation is: Calibrate retrieval threshold and ranking settings using labeled queries to admit relevant context without overwhelming the model with noise.
Question 848
While preparing a secure Foundry model or agent release, the following condition occurs: A planned model upgrade cannot allocate the required extra provisioned throughput units in its compliance region, but a release pipeline attempts the new deployment before checking quota. The remediation must meet enterprise access and reliability requirements without a broad bypass. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
- Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces.
- Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle.
- Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load.
Explanation
Correct Answer
A:Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. This is the most relevant evidence for provisioned model update exceeds regional capacity ceiling. Model capacity is region and deployment-type dependent; version upgrades cannot assume unused PTUs are available on demand. The matching controlled remediation is: Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A planned model upgrade….
Incorrect Answers
B:Inspect agent tool definitions, outbound allow rules, service endpoints, private links and network-denied traces. This would investigate agent tool calls fail behind overbroad outbound block rather than the documented provisioned model update exceeds regional capacity ceiling issue. The relevant investigation is: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A planned model upgrade….
C:Compare prompt commit hashes, foundation model version, tool JSON schema, serving configuration and prior approved release bundle. This would investigate prompt contract rollback ignores associated model version rather than the documented provisioned model update exceeds regional capacity ceiling issue. The relevant investigation is: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
D:Examine billed PTU hours, token utilization, workload predictability, available pay-as-you-go endpoints and expected launch load. This would investigate provisioned deployment pays for idle unused capacity rather than the documented provisioned model update exceeds regional capacity ceiling issue. The relevant investigation is: Verify region-specific model capacity, PTU quota, requested deployment units, existing reservations and allowed scaling alternatives.
Question 849
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 production-safe remediation should the engineer apply to this AI workflow?
- Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training.
- Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
- Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.
- Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
Explanation
Correct Answer
D:Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature. This targets autologging excludes required model artifact. Metrics and model artifacts are separately tracked by MLflow, so useful loss curves do not imply a registered loadable model exists. Verify the failure through: Check mlflow.autolog arguments, run artifact listing, model flavor metadata, configured output path and registration job logs. Validate success with: The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: An Azure ML….
Incorrect Answers
A:Configure a relevant supported primary metric and validation scheme for rare positive events and compare operating thresholds after training. This could address automl primary metric does not match rare-event goal, but it does not solve the specified autologging excludes required model artifact failure. The matching remediation is: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
B:Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate. This could address retired model kept active as discoverable deployment candidate, but it does not solve the specified autologging excludes required model artifact failure. The matching remediation is: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
C:Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds. This could address run comparison uses incompatible validation populations, but it does not solve the specified autologging excludes required model artifact failure. The matching remediation is: Enable supported model artifact logging or explicitly log a serializable MLflow model with its dependencies and signature.
Question 850
While deploying reproducible Azure Machine Learning infrastructure, 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 change must remain limited to authorized workspaces and avoid unreviewed production impact. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file.
- Check the component's registry name and version, target workspace identity, registry read permissions and referenced environment dependencies.
- Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.
- Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability.
Explanation
Correct Answer
C:Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports. This is the most relevant evidence for 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. The matching controlled remediation is: Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
Incorrect Answers
A:Examine the workspace linked-resource IDs, Key Vault tenant and RBAC permissions, secret retrieval errors and the IaC parameter file. This would investigate workspace dependencies point to unrelated secrets vault rather than the documented interactive compute instances remain running while unused issue. The relevant investigation is: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.
B: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 interactive compute instances remain running while unused issue. The relevant investigation is: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.
D:Inspect compute cluster requested SKU, max nodes, available family quota, current utilization, node provisioning events and region availability. This would investigate compute cluster cannot allocate requested gpu quota rather than the documented interactive compute instances remain running while unused issue. The relevant investigation is: Compare compute-instance schedules, last interactive activity, active notebook kernels, managed identity dependencies and cost reports.