Microsoft AI-300 Practice Test 18
Question 170
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A production deployment references a mutable latest model alias and picks up a candidate model that bypassed validation when another team registered a new version. The resolution must preserve quality gates, documented artifacts and rollback options. Which targeted Azure AI operations change best addresses the documented problem?
- Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
- Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.
- Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed.
- Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.
Explanation
Correct Answer
D:Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates. This targets model registry latest alias points to unapproved experiment. Mutable model aliases simplify discovery but are unsafe production identifiers when deployment reproducibility and review are required. Verify the failure through: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. Validate success with: Recreating a production deployment resolves the same approved model artifact until an authorized promotion changes the version. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A production….
Incorrect Answers
A:Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access. This could address mlflow tracking uri sends notebook runs to wrong workspace, but it does not solve the specified model registry latest alias points to unapproved experiment failure. The matching remediation is: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.
B:Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers. This could address model evaluation exposes sensitive examples in explainability report, but it does not solve the specified model registry latest alias points to unapproved experiment failure. The matching remediation is: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates.
C:Retain a governed archived or retrievable known-good model and its environment until release validation and rollback windows have passed. This could address incident rollback artifact was deleted instead of archived, but it does not solve the specified model registry latest alias points to unapproved experiment failure. The matching remediation is: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A production….
Question 171
As an AI operations team checks production agent evaluation evidence, the following condition occurs: A user-facing agent becomes slow after an LLM deployment change, but the team only records total response time and cannot tell retrieval delay from model generation delay. The workflow must produce measurable quality, safety and performance evidence. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.
- Add approved prompt-injection and tool-abuse evaluation cases with tool permission gates and block release on unsafe execution.
- Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results.
- Add token-aware throughput and queue metrics and apply capacity/pacing policies matching actual peak token demand.
- Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
- Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles.
Explanation
Correct Answers
D:Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change. This targets generation latency spike blamed on retrieval without breakdown. Latency budgets should separate agent orchestration, retrieval and generation; total duration alone cannot locate the bottleneck. Verify the failure through: Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. Validate success with: The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components.
E:Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. This is the most relevant evidence for generation latency spike blamed on retrieval without breakdown. Latency budgets should separate agent orchestration, retrieval and generation; total duration alone cannot locate the bottleneck. The matching controlled remediation is: Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
Incorrect Answers
A: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 generation latency spike blamed on retrieval without breakdown. First examine: Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. Then correct: Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
B:Examine continuous monitoring configuration, trace deployment IDs, sampling window, evaluator assignment and per-version quality results. This is associated with foundry continuous evaluation ignores production deployment version, not the essential evidence-and-fix pair for generation latency spike blamed on retrieval without breakdown. First examine: Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. Then correct: Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
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 generation latency spike blamed on retrieval without breakdown. First examine: Examine end-to-end request traces, retrieval timing, model time to first token, generation duration, request concurrency and percentiles. Then correct: Instrument stage-level latency and compare generation and retrieval spans before applying a targeted capacity or retrieval change.
Question 172
During a production Azure Machine Learning model lifecycle incident, 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 operator must safeguard training reproducibility and serving continuity. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.
- Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process.
- Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers.
- Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds.
- Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
- Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology.
Explanation
Correct Answers
A:Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. This is the most relevant evidence for 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. The matching controlled remediation is: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
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
B:Restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers. This is associated with model evaluation exposes sensitive examples in explainability report, not the essential evidence-and-fix pair for mlflow tracking uri sends notebook runs to wrong workspace. First examine: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Then correct: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
C:Evaluate candidate and baseline on the same governed holdout dataset using the same business-aligned metrics and thresholds. This is associated with run comparison uses incompatible validation populations, not the essential evidence-and-fix pair for mlflow tracking uri sends notebook runs to wrong workspace. First examine: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Then correct: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
E:Check pipeline YAML, component inputs and outputs, resource dependency graph and job execution chronology. This is associated with pipeline graph omits feature-build dependency, not the essential evidence-and-fix pair for mlflow tracking uri sends notebook runs to wrong workspace. First examine: Inspect active MLflow tracking URI, experiment ID, Azure credentials, studio run listing and configuration inherited by the notebook process. Then correct: Set the correct Azure Machine Learning MLflow tracking URI and experiment context before training and verify authenticated workspace access.
Question 173
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. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
- Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.
- Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events.
- Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance.
Explanation
Correct Answer
A:Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This is the most relevant evidence for notebook merge bypasses protected evaluation tests. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. The matching controlled remediation is: Require protected pull requests and automated component tests before changes to production training code are merged.
Incorrect Answers
B:Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. This would investigate aml private workspace storage access fails from compute rather than the documented notebook merge bypasses protected evaluation tests issue. The relevant investigation is: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
C:Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. This would investigate docker environment image cannot pull from private registry rather than the documented notebook merge bypasses protected evaluation tests issue. The relevant investigation is: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
D:Review federated credential issuer, audience and subject, GitHub environment protection rules, branch patterns and run provenance. This would investigate oidc subject filter trusts unreviewed pull-request branches rather than the documented notebook merge bypasses protected evaluation tests issue. The relevant investigation is: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
Question 174
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. What approved correction resolves the failure without modifying unrelated healthy services?
- Preflight capacity and schedule an approved upgrade with quota adjustment or temporary side-by-side resources that fit the region.
- Choose an appropriate available model and supported prompt chunking strategy that meets the workload's context and cost requirements.
- Pin an approved model/deployment version where supported and pass candidate upgrades through evaluation and controlled promotion.
- Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling.
Explanation
Correct Answer
A: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.
Incorrect Answers
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.
C: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 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.
D:Separate trusted instructions from quoted retrieved context and enforce restricted tool permissions and injection-resilient prompt handling. This could address prompt includes untrusted retrieved instructions as system policy, 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 175
During a production Azure Machine Learning model lifecycle incident, 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 operator must safeguard training reproducibility and serving continuity. Which targeted Azure AI operations change best addresses the documented problem?
- Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
- Apply a controlled small traffic allocation to the candidate, monitor quality and latency, then gradually increase only after passing gates.
- Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment.
- Write the model into the declared Azure ML job output path and track the versioned artifact used in registration.
Explanation
Correct Answer
A:Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs. This targets 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. Verify the failure through: Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata. Validate success with: A historical notebook rerun uses the recorded snapshot and yields traceable feature statistics.
Incorrect Answers
B: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 exploration notebook reads production data without reproducible snapshot failure. The matching remediation is: Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
C:Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment. This could address mlflow experiment logs omit run parameters, but it does not solve the specified exploration notebook reads production data without reproducible snapshot failure. The matching remediation is: Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
D:Write the model into the declared Azure ML job output path and track the versioned artifact used in registration. This could address training job does not persist output artifacts, but it does not solve the specified exploration notebook reads production data without reproducible snapshot failure. The matching remediation is: Capture a governed immutable dataset or versioned data asset and reference that exact version in notebook and scheduled jobs.
Question 176
While deploying reproducible Azure Machine Learning infrastructure, 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 change must remain limited to authorized workspaces and avoid unreviewed production impact. Which investigation best verifies the cause before changing production configuration?
- Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
- Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events.
- Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs.
- Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
Explanation
Correct Answer
D:Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This is the most relevant evidence for notebook merge bypasses protected evaluation tests. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. The matching controlled remediation is: Require protected pull requests and automated component tests before changes to production training code are merged. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A….
Incorrect Answers
A:Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. This would investigate bicep workspace declaration misses dependent private resources rather than the documented notebook merge bypasses protected evaluation tests issue. The relevant investigation is: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
B:Inspect container image registry URI and tag, Azure ML compute managed identity, ACR pull role, firewall path and worker startup events. This would investigate docker environment image cannot pull from private registry rather than the documented notebook merge bypasses protected evaluation tests issue. The relevant investigation is: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A….
C:Inspect storage private endpoint approvals, privatelink DNS A records, compute subnet DNS, routes and outbound access test logs. This would investigate aml private workspace storage access fails from compute rather than the documented notebook merge bypasses protected evaluation tests issue. The relevant investigation is: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A….
Question 177
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A withdrawn credit-risk model is marked deprecated in a wiki but remains exposed as an active registry version and continues to be selected by automated deployment tools. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO: the strongest initial evidence and the aligned controlled correction.
- Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals.
- Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training.
- Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
- Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version.
- Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining.
Explanation
Correct Answers
A:Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. This is the most relevant evidence for retired model kept active as discoverable deployment candidate. Model lifecycle management must reflect state in the model registry and deployment references, not just informal documentation. The matching controlled remediation is: Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
C:Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate. This targets retired model kept active as discoverable deployment candidate. Model lifecycle management must reflect state in the model registry and deployment references, not just informal documentation. Verify the failure through: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. Validate success with: New deployment workflows cannot select the retired version while required historic audit artifacts remain available.
Incorrect Answers
B:Inspect registered model metadata, online feature lookup mapping, feature timestamps, key names and schema contract from training. This is associated with feature retrieval specification missing from registered model, not the essential evidence-and-fix pair for retired model kept active as discoverable deployment candidate. First examine: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. Then correct: Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
D:Implement point-in-time correct feature retrieval and package its temporal lookup logic with the registered model version. This is associated with online feature retrieval pulls values from after prediction time, not the essential evidence-and-fix pair for retired model kept active as discoverable deployment candidate. First examine: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. Then correct: Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
E:Add a minimum data-volume gate and justified threshold/confirmation window before invoking retraining. This is associated with retraining alarm triggers on insufficient sample volume, not the essential evidence-and-fix pair for retired model kept active as discoverable deployment candidate. First examine: Inspect registry model lifecycle status, alias assignments, endpoint references, deployment logs and retirement approvals. Then correct: Archive or retire the version through a governed registry lifecycle and remove it from production deployment aliases after dependents migrate.
Question 178
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. Which acceptance test shows the AI operations defect is corrected?
- The pipeline resolves component dependencies and the training step reads the expected typed asset without implicit file guessing.
- A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible.
- The job consumes the intended dataset version and staging files are not silently mixed into production runs.
- Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.
Explanation
Correct Answer
D:Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments. Compute instances and managed compute clusters have different operating models; idle instance cost is not eliminated by an unrelated model deployment setting. a direct corrective action is to apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
Incorrect Answers
A:The pipeline resolves component dependencies and the training step reads the expected typed asset without implicit file guessing. That addresses a different configuration issue rather than the main requirement. Verify instead: Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.
B:A scoped job retrieves only the approved secret and unrelated project secrets remain inaccessible. That addresses a different configuration issue rather than the main requirement. Verify instead: Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.
C:The job consumes the intended dataset version and staging files are not silently mixed into production runs. That addresses a different configuration issue rather than the main requirement. Verify instead: Idle costs fall outside approved usage windows and users can resume the instances for sanctioned experiments.
Question 179
While preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application releases its Foundry project and calls a model name before that model deployment is created, causing intermittent first-run errors. 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.
- Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions.
- Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline.
- Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes.
- Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
- Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations.
Explanation
Correct Answers
D:Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This targets foundry bicep rollout omits model deployment dependencies. Infrastructure-as-code can provision the platform consistently only when dependencies and deployment readiness are managed explicitly. Verify the failure through: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. Validate success with: Repeatable IaC releases create the expected project and model deployment before starting inference smoke tests. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application….
E:Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. This is the most relevant evidence for foundry bicep rollout omits model deployment dependencies. Infrastructure-as-code can provision the platform consistently only when dependencies and deployment readiness are managed explicitly. The matching controlled remediation is: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration. This matters here because while preparing a secure Foundry model or agent release, the following condition occurs: A GenAI application….
Incorrect Answers
A:Apply least-privilege subnet and identity restrictions to production model access and remove inherited broad sandbox exemptions. This is associated with network allowlist exposes production model endpoint to test subnet, not the essential evidence-and-fix pair for foundry bicep rollout omits model deployment dependencies. First examine: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. Then correct: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
B:Design and test balanced representative prompt examples under fairness and privacy constraints, retaining a versioned evaluation baseline. This is associated with few-shot prompt examples bias outputs toward one subgroup, not the essential evidence-and-fix pair for foundry bicep rollout omits model deployment dependencies. First examine: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. Then correct: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
C:Inspect Foundry project and resource regions, model deployment regional availability, enterprise residency constraints and API error codes. This is associated with foundry project created in mismatched resource location, not the essential evidence-and-fix pair for foundry bicep rollout omits model deployment dependencies. First examine: Inspect Bicep template resource references, model deployment name outputs, CI step dependencies and Azure deployment operations. Then correct: Define the model and project deployment lifecycle dependencies and verify provisioning completion before dependent app configuration.
Question 180
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 TWO complementary choices identify the issue and correct it? Select TWO.
- Require protected pull requests and automated component tests before changes to production training code are merged.
- Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history.
- Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
- Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals.
- Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
Explanation
Correct Answers
A:Require protected pull requests and automated component tests before changes to production training code are merged. This targets notebook merge bypasses protected evaluation tests. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. Verify the failure through: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Validate success with: 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:Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. This is the most relevant evidence for notebook merge bypasses protected evaluation tests. Git repositories need enforced review and CI checks; simply storing a notebook in source control does not prevent defective changes. The matching controlled remediation is: 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
C:Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This is associated with datastore uri selects the incorrect storage container, not the essential evidence-and-fix pair for notebook merge bypasses protected evaluation tests. First examine: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Then correct: Require protected pull requests and automated component tests before changes to production training code are merged.
D:Inspect GitHub workflow jobs, Bicep build/what-if steps, test deployment history, parameter values and release approvals. This is associated with iac workflow lacks repeatable infrastructure validation, not the essential evidence-and-fix pair for notebook merge bypasses protected evaluation tests. First examine: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Then correct: Require protected pull requests and automated component tests before changes to production training code are merged.
E:Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This is associated with aml managed network blocks model registry egress, not the essential evidence-and-fix pair for notebook merge bypasses protected evaluation tests. First examine: Inspect Git branch protection, pull-request review requirements, test workflow triggers, dataset schema checks and recent commit history. Then correct: Require protected pull requests and automated component tests before changes to production training code are merged.