Microsoft AI-300 Practice Test 74
Question 730
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A Python scoring pipeline passes locally but fails on managed compute after a dependency release changes a library API because its Azure ML environment specifies unbounded package versions. The team must preserve approved access, model provenance and private network constraints. Which observable postchange result proves the intended remediation succeeded?
- A reviewed release can deploy production resources, but an unreviewed branch workflow cannot obtain production deployment rights.
- The same versioned component runs against authorized data in two workspaces without editing its source implementation.
- Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry.
- The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution.
Explanation
Correct Answer
D:The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution. Azure ML environment assets package execution dependencies; reproducibility requires explicit versions rather than assuming the newest package is compatible. a direct corrective action is to publish a versioned Azure ML environment with vetted pinned packages and reproduce the build on the target compute before deployment. This matters here because a Python scoring pipeline passes locally but fails on managed compute after a dependency release changes a library….
Incorrect Answers
A:A reviewed release can deploy production resources, but an unreviewed branch workflow cannot obtain production deployment rights. That addresses a different configuration issue rather than the main requirement. Verify instead: The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution.
B:The same versioned component runs against authorized data in two workspaces without editing its source implementation. That addresses a different configuration issue rather than the main requirement. Verify instead: The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution.
C:Authorized workspaces run the shared component while unauthorized subscriptions remain blocked from the registry. That addresses a different configuration issue rather than the main requirement. Verify instead: The job runs with a traceable environment digest and no surprise dependency upgrade on repeated execution. This matters here because a Python scoring pipeline passes locally but fails on managed compute after a dependency release changes a library….
Question 731
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A responsible AI dashboard is shared widely with raw personal records and explanations containing identifiers rather than access-controlled aggregate findings. The operator must safeguard training reproducibility and serving continuity. What measured outcome validates the solution while preserving the stated constraints?
- A poor candidate is retained for review without reaching production, and qualifying candidates progress through controlled canary rollout.
- Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.
- Historical inference replay uses only features available before prediction time and realistic performance survives evaluation.
- Offline validation and online scoring use equivalent feature definitions and identical customer keys without silent missing-value substitution.
Explanation
Correct Answer
B:Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers. Responsible AI review includes protecting personal data in explanatory artifacts, not only calculating model performance metrics. a direct corrective action is to restrict access, redact or aggregate sensitive examples and publish a privacy-reviewed evaluation artifact for authorized reviewers. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A responsible….
Incorrect Answers
A:A poor candidate is retained for review without reaching production, and qualifying candidates progress through controlled canary rollout. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.
C:Historical inference replay uses only features available before prediction time and realistic performance survives evaluation. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A responsible….
D:Offline validation and online scoring use equivalent feature definitions and identical customer keys without silent missing-value substitution. That addresses a different configuration issue rather than the main requirement. Verify instead: Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.
Question 732
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 measured outcome validates the solution while preserving the stated constraints?
- Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers.
- A representative rollback test restores known-good predictions and endpoint health within the recovery target.
- A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.
- Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
Explanation
Correct Answer
B:A representative rollback test restores known-good predictions and endpoint health within the recovery target. A deployment's behavior depends on the whole inference package; changing model weights alone cannot undo incompatible runtime changes. a direct corrective action is to restore the complete previously approved deployment package, including model, environment and scoring code, rather than only changing weights. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….
Incorrect Answers
A:Authorized auditors can assess model behavior while unauthorized team members cannot recover individual identifiers. That addresses a different configuration issue rather than the main requirement. Verify instead: A representative rollback test restores known-good predictions and endpoint health within the recovery target.
C:A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. That addresses a different configuration issue rather than the main requirement. Verify instead: A representative rollback test restores known-good predictions and endpoint health within the recovery target. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….
D:Overnight processing completes within its processing window and interactive endpoint latency remains within SLA. That addresses a different configuration issue rather than the main requirement. Verify instead: A representative rollback test restores known-good predictions and endpoint health within the recovery target.
Question 733
During a production Azure Machine Learning model lifecycle incident, 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 operator must safeguard training reproducibility and serving continuity. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Examine cohort labels, fairness metrics, stratified error rates, consent constraints and model evaluation dataset representativeness.
- Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
- Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
- Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings.
Explanation
Correct Answer
B:Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events. This is the most relevant evidence for 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. The matching controlled remediation is: Pin production deployments to an immutable reviewed model version and promote newer versions only after explicit approval gates. This matters here because during a production Azure Machine Learning model lifecycle incident, the following condition occurs: A production….
Incorrect Answers
A: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 model registry latest alias points to unapproved experiment issue. The relevant investigation is: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
C:Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This would investigate run comparison uses incompatible validation populations rather than the documented model registry latest alias points to unapproved experiment issue. The relevant investigation is: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
D:Inspect evaluation artifact content, privacy classification, report permissions, explanation samples and downstream dashboard export settings. This would investigate model evaluation exposes sensitive examples in explainability report rather than the documented model registry latest alias points to unapproved experiment issue. The relevant investigation is: Inspect model version IDs, labels/aliases, approval evidence, endpoint deployment configuration and registry audit events.
Question 734
During a regulated Azure ML workspace infrastructure review, the following condition occurs: An Azure ML pipeline consistently fails to read input blobs after a storage-account key rotation because its registered datastore uses the old key. The team must preserve approved access, model provenance and private network constraints. What measured outcome validates the solution while preserving the stated constraints?
- A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files.
- Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources.
- The job reads the required training blobs and cannot write or list unrelated protected containers.
- The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement.
Explanation
Correct Answer
A:A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files. Datastores provide connection configuration but do not bypass storage authentication; credential rotation must be propagated or identity access designed correctly. a direct corrective action is to replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management. This matters here because an Azure ML pipeline consistently fails to read input blobs after a storage-account key rotation because its….
Incorrect Answers
B:Production resources appear only in the authorized scope and rerunning the script does not create duplicate sandbox resources. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files.
C:The job reads the required training blobs and cannot write or list unrelated protected containers. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files.
D:The training job acquires nodes inside documented quota and starts without creating unapproved capacity or dropping the distributed requirement. That addresses a different configuration issue rather than the main requirement. Verify instead: A rerun reads the expected immutable input without hard-coded expired keys in notebooks or repository files.
Question 735
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 observable postchange result proves the intended remediation succeeded?
- A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
- A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.
- Quality improves on relevant cohorts without exposing personal information or degrading approved common-case answers.
- Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact.
Explanation
Correct Answer
B:A realistic image invoice yields extracted required details without unsupported request content or invented visual observations. Model capability and endpoint payload contracts determine which modalities can be processed; a text-only deployment cannot reliably infer pixels. a direct corrective action is to select an approved multimodal model or add a supported image-to-text preprocessing service before the text generation step.
Incorrect Answers
A:A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. That addresses a different configuration issue rather than the main requirement. Verify instead: A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.
C:Quality improves on relevant cohorts without exposing personal information or degrading approved common-case answers. That addresses a different configuration issue rather than the main requirement. Verify instead: A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.
D:Representative chat queries receive valid answers within the approved latency target without waiting for a batch output artifact. That addresses a different configuration issue rather than the main requirement. Verify instead: A realistic image invoice yields extracted required details without unsupported request content or invented visual observations.
Question 736
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A nightly 15-million-row customer scoring task is sent as individual requests to a production real-time endpoint, degrading its daytime customer traffic. The operator must safeguard training reproducibility and serving continuity. Which acceptance test shows the AI operations defect is corrected?
- A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs.
- The winning child run has the best intended validation metric among eligible candidates and is reevaluated on unseen holdout data.
- A representative rollback test restores known-good predictions and endpoint health within the recovery target.
- Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
Explanation
Correct Answer
D:Overnight processing completes within its processing window and interactive endpoint latency remains within SLA. Batch scoring and synchronous online inference serve different workload shapes and should not contend for capacity unnecessarily. a direct corrective action is to move the approved bulk workload to a managed batch endpoint or batch inference job while preserving online capacity for interactive calls.
Incorrect Answers
A:A controlled API load test meets latency and correctness targets without requiring clients to poll batch jobs. That addresses a different configuration issue rather than the main requirement. Verify instead: Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
B:The winning child run has the best intended validation metric among eligible candidates and is reevaluated on unseen holdout data. That addresses a different configuration issue rather than the main requirement. Verify instead: Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
C:A representative rollback test restores known-good predictions and endpoint health within the recovery target. That addresses a different configuration issue rather than the main requirement. Verify instead: Overnight processing completes within its processing window and interactive endpoint latency remains within SLA.
Question 737
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A tabular classification pipeline expects named columns but a newly registered MLTable asset points to CSV files with a different header and type inference rules. The team must preserve approved access, model provenance and private network constraints. 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.
- Replaying a prior run uses identical input version and produces traceable comparison metrics before a new snapshot is promoted.
- Automated model registration succeeds while the principal cannot change unrelated networks, secrets or subscriptions.
- A validation job loads the intended features with the declared schema and rejects incompatible input files.
Explanation
Correct Answer
D:A validation job loads the intended features with the declared schema and rejects incompatible input files. An Azure ML data asset describes dataset structure and access; registration success does not prove its schema matches a consuming model. a direct corrective action is to rebuild or correct the versioned MLTable asset transformation so the expected columns and types are supplied to downstream training. This matters here because a tabular classification pipeline expects named columns but a newly registered MLTable asset points to CSV files….
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: A validation job loads the intended features with the declared schema and rejects incompatible input files. This matters here because a tabular classification pipeline expects named columns but a newly registered MLTable asset points to CSV files….
B:Replaying a prior run uses identical input version and produces traceable comparison metrics before a new snapshot is promoted. That addresses a different configuration issue rather than the main requirement. Verify instead: A validation job loads the intended features with the declared schema and rejects incompatible input files.
C:Automated model registration succeeds while the principal cannot change unrelated networks, secrets or subscriptions. That addresses a different configuration issue rather than the main requirement. Verify instead: A validation job loads the intended features with the declared schema and rejects incompatible input files.
Question 738
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is trained across four GPU workers but all workers ingest the same unsharded dataset in each epoch, wasting resources and biasing effective training statistics. The resolution must preserve quality gates, documented artifacts and rollback options. What approved correction resolves the failure without modifying unrelated healthy services?
- Allow the narrowly scoped supported compute-to-compute communication paths and correct the distributed training rendezvous configuration.
- Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time.
- Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
- Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity.
Explanation
Correct Answer
C:Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation. This targets distributed training uses one shard for every worker. Data-parallel training must coordinate sampling and gradient aggregation; launching multiple processes does not automatically shard training data. Verify the failure through: Review distributed sampler configuration, global and local ranks, dataset partition checks, epoch seeding and examples processed per worker. Validate success with: Workers process the intended distinct data shards and aggregated training metrics match the complete dataset definition. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A model is….
Incorrect Answers
A:Allow the narrowly scoped supported compute-to-compute communication paths and correct the distributed training rendezvous configuration. This could address distributed job workers cannot communicate over required network path, but it does not solve the specified distributed training uses one shard for every worker failure. The matching remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
B:Package and version the approved feature retrieval specification with the model and enforce the same mapping at serving time. This could address feature retrieval specification missing from registered model, but it does not solve the specified distributed training uses one shard for every worker failure. The matching remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
D:Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity. This could address sweep concurrency overwhelms scarce gpu quota, but it does not solve the specified distributed training uses one shard for every worker failure. The matching remediation is: Configure the framework's appropriate distributed data sampler and synchronize epoch handling and metrics aggregation.
Question 739
During a regulated Azure ML workspace infrastructure review, the following condition occurs: A release workflow deploys Azure ML resources using a long-lived service-principal secret stored in GitHub, violating a keyless identity standard and complicating rotation. The team must preserve approved access, model provenance and private network constraints. Which TWO complementary choices identify the issue and correct it? Select TWO.
- Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
- Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions.
- Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation.
- Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances.
- Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order.
Explanation
Correct Answers
A:Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow. This targets github action uses persistent azure client secret. GitHub Actions OpenID Connect can exchange scoped workflow identity for Azure access; persistent secrets are unnecessary when federation is correctly configured. Verify the failure through: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Validate success with: The approved branch deploys using short-lived federated tokens, and old client secrets can be revoked without breaking releases.
B:Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. This is the most relevant evidence for github action uses persistent azure client secret. GitHub Actions OpenID Connect can exchange scoped workflow identity for Azure access; persistent secrets are unnecessary when federation is correctly configured. The matching controlled remediation is: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
Incorrect Answers
C:Link the correct private DNS zone and approved storage private endpoint to the managed network path before enforcing storage isolation. This is associated with aml private workspace storage access fails from compute, not the essential evidence-and-fix pair for github action uses persistent azure client secret. First examine: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Then correct: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
D:Apply supported automatic shutdown and business-hour schedules after confirming no required interactive or scheduled process depends on the instances. This is associated with interactive compute instances remain running while unused, not the essential evidence-and-fix pair for github action uses persistent azure client secret. First examine: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Then correct: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
E:Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. This is associated with bicep workspace declaration misses dependent private resources, not the essential evidence-and-fix pair for github action uses persistent azure client secret. First examine: Inspect GitHub Actions Azure login configuration, identity trust federated credentials, repository secret usage, token audience and workflow permissions. Then correct: Configure GitHub OIDC federated identity with a scoped Azure service principal and replace the long-lived secret in the deployment workflow.
Question 740
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new managed-network isolated Azure ML workspace can train local models but fails to pull an approved model package from a registry because outbound access was not allowlisted. The change must remain limited to authorized workspaces and avoid unreviewed production impact. What approved correction resolves the failure without modifying unrelated healthy services?
- Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate.
- Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
- Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema.
- Bind every training job and model registration to a reviewed Git commit SHA and immutable environment/data version in the workflow.
Explanation
Correct Answer
B:Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This targets aml managed network blocks model registry egress. Workspace network isolation controls package and asset connectivity in addition to private inbound access; approved egress must be explicit. Verify the failure through: Examine workspace managed network isolation mode, outbound rules, registry destination, DNS and job network diagnostics. Validate success with: Authorized registry models load in the isolated environment and unrelated external destinations remain blocked. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new….
Incorrect Answers
A:Gate production deployment behind approved GitHub environment protection, protected refs and status checks while keeping test deployments separate. This could address github deployment pipeline omits secure environment approvals, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A new….
C:Align the component output with the declared downstream input type or introduce a supported data conversion step with versioned schema. This could address pipeline component output type mismatches consumer, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.
D:Bind every training job and model registration to a reviewed Git commit SHA and immutable environment/data version in the workflow. This could address production training script commit cannot be traced, but it does not solve the specified aml managed network blocks model registry egress failure. The matching remediation is: Configure the supported least-privilege outbound access to the approved registry without enabling unrestricted internet egress.