McAfee-Secured Website

Exam Code: AI-300

Exam Name: Operationalizing Machine Learning and Generative AI Solutions

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Machine Learning Operations Engineer Associate

100% Microsoft AI-300 Guaranteed Success With Testking Training Materials

Get Real AI-300 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

213 Questions & Answers with Testing Engine

"Operationalizing Machine Learning and Generative AI Solutions Exam", also known as AI-300 exam, is a Microsoft certification exam.

Pass your tests with the always up-to-date AI-300 Exam Engine. Your AI-300 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Microsoft AI-300 Practice Test 1

Question 1

A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. Which decision enforces the location requirement?

  1. Declare and verify the intended dependent Azure resources in the workspace deployment definition.
  2. Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute.
  3. Inventory and export required model, run, and governance records into retained storage.
  4. Set the workspace location to the approved European region before provisioning.

Explanation

Correct Answer

D:

The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies.

Incorrect Answers

A:

Declare and verify the intended dependent Azure resources in the workspace deployment definition. That operation would be relevant if: An MLOps team wants every new workspace to automatically connect to the correct Key Vault, Storage, and Application Insights dependencies. Its corresponding reason or verification is: Explicit dependency mapping prevents an accidentally created workspace from relying on unintended shared services or missing platform dependencies. However the problem in this question is: A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. The requirement instead calls for Set the workspace location to the approved European region before provisioning; the question-specific check is: The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies.

B:

Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute. A separate source case supports that approach when: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. The supporting rationale or observable result is: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending. This question describes a different issue: A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. Address it through Set the workspace location to the approved European region before provisioning, with the required justification or evidence: The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies.

C:

Inventory and export required model, run, and governance records into retained storage. This is useful for the distinct issue: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. The relevant technical rationale or evidence for that issue is: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute. Here the reported issue is: A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. The relevant response is: Set the workspace location to the approved European region before provisioning. The first result cannot verify this different correction: The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies.

Question 2

A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. What should the infrastructure owner prepare first?

  1. Use a stable workspace name and idempotent declared infrastructure configuration per environment.
  2. Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute.
  3. Create or select the intended resource group and pass its name into workspace provisioning.
  4. Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies.

Explanation

Correct Answer

C:

Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions.

Incorrect Answers

A:

The alternative, Use a stable workspace name and idempotent declared infrastructure configuration per environment, belongs to a different technical condition: A corporate script repeatedly creates duplicate Azure ML workspaces because each execution uses a random resource name. There the source-specific mechanism or proof is: Consistent resource identifiers allow repeat deployments to update the intended resource instead of proliferating unmanaged workspaces. The condition asked about here is: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. A suitable correction is Create or select the intended resource group and pass its name into workspace provisioning; the targeted justification or result is: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions.

B:

Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute. That operation would be relevant if: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. Its corresponding reason or verification is: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending. However the problem in this question is: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. The requirement instead calls for Create or select the intended resource group and pass its name into workspace provisioning; the question-specific check is: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions.

D:

Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies. A separate source case supports that approach when: A research workspace uses a shared storage account that a platform team will delete during cleanup. The supporting rationale or observable result is: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments. This question describes a different issue: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. Address it through Create or select the intended resource group and pass its name into workspace provisioning, with the required justification or evidence: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions.

Question 3

The organization requires customer-managed encryption keys for a new Azure Machine Learning workspace. The team plans to add key-management settings after deployment. Which approach meets this creation dependency?

  1. Create or select the intended resource group and pass its name into workspace provisioning.
  2. Configure the supported customer-managed key and Key Vault permissions during workspace creation.
  3. Inventory and export required model, run, and governance records into retained storage.
  4. Set the workspace location to the approved European region before provisioning.

Explanation

Correct Answer

B:

Encryption architecture must be planned at provisioning and requires a reachable key plus correct resource identity permissions.

Incorrect Answers

A:

Create or select the intended resource group and pass its name into workspace provisioning. It addresses another case: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. For that case, the distinguishing justification or acceptance check is: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions. The present case instead states: The organization requires customer-managed encryption keys for a new Azure Machine Learning workspace. The team plans to add key-management settings after deployment. It calls for Configure the supported customer-managed key and Key Vault permissions during workspace creation. Showing success for the other case would not establish: Encryption architecture must be planned at provisioning and requires a reachable key plus correct resource identity permissions.

C:

The alternative, Inventory and export required model, run, and governance records into retained storage, belongs to a different technical condition: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. There the source-specific mechanism or proof is: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute. The condition asked about here is: The organization requires customer-managed encryption keys for a new Azure Machine Learning workspace. The team plans to add key-management settings after deployment. A suitable correction is Configure the supported customer-managed key and Key Vault permissions during workspace creation; the targeted justification or result is: Encryption architecture must be planned at provisioning and requires a reachable key plus correct resource identity permissions.

D:

Set the workspace location to the approved European region before provisioning. That operation would be relevant if: A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. Its corresponding reason or verification is: The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies. However the problem in this question is: The organization requires customer-managed encryption keys for a new Azure Machine Learning workspace. The team plans to add key-management settings after deployment. The requirement instead calls for Configure the supported customer-managed key and Key Vault permissions during workspace creation; the question-specific check is: Encryption architecture must be planned at provisioning and requires a reachable key plus correct resource identity permissions.

Question 4

One organization has a production release process and an experimental notebook process with different access and change controls. How should it separate their Azure ML workspace administration?

  1. Provision separate production and experimentation workspaces with distinct scoped policies.
  2. Deploy the workspace configuration from version-controlled infrastructure-as-code templates.
  3. Create or select the intended resource group and pass its name into workspace provisioning.
  4. Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute.

Explanation

Correct Answer

A:

Separate workspace boundaries permit independent RBAC, deployment approvals, monitoring, and resource governance without coupling exploratory jobs to production.

Incorrect Answers

B:

Deploy the workspace configuration from version-controlled infrastructure-as-code templates. This is useful for the distinct issue: Several workspaces require a centrally consistent policy for encryption, tagging, and access. Manual workspace creation keeps drifting. The relevant technical rationale or evidence for that issue is: Declared resource configuration enables peer review, consistency, and reproducible environments across teams instead of untracked portal changes. Here the reported issue is: One organization has a production release process and an experimental notebook process with different access and change controls. The relevant response is: Provision separate production and experimentation workspaces with distinct scoped policies. The first result cannot verify this different correction: Separate workspace boundaries permit independent RBAC, deployment approvals, monitoring, and resource governance without coupling exploratory jobs to production.

C:

Create or select the intended resource group and pass its name into workspace provisioning. It addresses another case: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. For that case, the distinguishing justification or acceptance check is: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions. The present case instead states: One organization has a production release process and an experimental notebook process with different access and change controls. It calls for Provision separate production and experimentation workspaces with distinct scoped policies. Showing success for the other case would not establish: Separate workspace boundaries permit independent RBAC, deployment approvals, monitoring, and resource governance without coupling exploratory jobs to production.

D:

The alternative, Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute, belongs to a different technical condition: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. There the source-specific mechanism or proof is: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending. The condition asked about here is: One organization has a production release process and an experimental notebook process with different access and change controls. A suitable correction is Provision separate production and experimentation workspaces with distinct scoped policies; the targeted justification or result is: Separate workspace boundaries permit independent RBAC, deployment approvals, monitoring, and resource governance without coupling exploratory jobs to production.

Question 5

A corporate script repeatedly creates duplicate Azure ML workspaces because each execution uses a random resource name. Which change supports reproducible infrastructure provisioning?

  1. Inventory and export required model, run, and governance records into retained storage.
  2. Set the workspace location to the approved European region before provisioning.
  3. Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies.
  4. Use a stable workspace name and idempotent declared infrastructure configuration per environment.

Explanation

Correct Answer

D:

Consistent resource identifiers allow repeat deployments to update the intended resource instead of proliferating unmanaged workspaces.

Incorrect Answers

A:

Inventory and export required model, run, and governance records into retained storage. A separate source case supports that approach when: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. The supporting rationale or observable result is: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute. This question describes a different issue: A corporate script repeatedly creates duplicate Azure ML workspaces because each execution uses a random resource name. Address it through Use a stable workspace name and idempotent declared infrastructure configuration per environment, with the required justification or evidence: Consistent resource identifiers allow repeat deployments to update the intended resource instead of proliferating unmanaged workspaces.

B:

Set the workspace location to the approved European region before provisioning. This is useful for the distinct issue: A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. The relevant technical rationale or evidence for that issue is: The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies. Here the reported issue is: A corporate script repeatedly creates duplicate Azure ML workspaces because each execution uses a random resource name. The relevant response is: Use a stable workspace name and idempotent declared infrastructure configuration per environment. The first result cannot verify this different correction: Consistent resource identifiers allow repeat deployments to update the intended resource instead of proliferating unmanaged workspaces.

C:

Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies. It addresses another case: A research workspace uses a shared storage account that a platform team will delete during cleanup. For that case, the distinguishing justification or acceptance check is: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments. The present case instead states: A corporate script repeatedly creates duplicate Azure ML workspaces because each execution uses a random resource name. It calls for Use a stable workspace name and idempotent declared infrastructure configuration per environment. Showing success for the other case would not establish: Consistent resource identifiers allow repeat deployments to update the intended resource instead of proliferating unmanaged workspaces.

Question 6

Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. What workspace governance approach helps?

  1. Create or select the intended resource group and pass its name into workspace provisioning.
  2. Inventory and export required model, run, and governance records into retained storage.
  3. Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute.
  4. Request the applicable regional VM-family quota or select available supported capacity.

Explanation

Correct Answer

C:

Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending.

Incorrect Answers

A:

Create or select the intended resource group and pass its name into workspace provisioning. That operation would be relevant if: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. Its corresponding reason or verification is: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions. However the problem in this question is: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. The requirement instead calls for Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute; the question-specific check is: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending.

B:

Inventory and export required model, run, and governance records into retained storage. A separate source case supports that approach when: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. The supporting rationale or observable result is: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute. This question describes a different issue: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. Address it through Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute, with the required justification or evidence: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending.

D:

Request the applicable regional VM-family quota or select available supported capacity. This is useful for the distinct issue: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. The relevant technical rationale or evidence for that issue is: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota. Here the reported issue is: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. The relevant response is: Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute. The first result cannot verify this different correction: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending.

Question 7

A research workspace uses a shared storage account that a platform team will delete during cleanup. What should a workspace owner assess before that deletion?

  1. Configure the supported customer-managed key and Key Vault permissions during workspace creation.
  2. Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies.
  3. Request the applicable regional VM-family quota or select available supported capacity.
  4. Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute.

Explanation

Correct Answer

B:

The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments.

Incorrect Answers

A:

The alternative, Configure the supported customer-managed key and Key Vault permissions during workspace creation, belongs to a different technical condition: The organization requires customer-managed encryption keys for a new Azure Machine Learning workspace. The team plans to add key-management settings after deployment. There the source-specific mechanism or proof is: Encryption architecture must be planned at provisioning and requires a reachable key plus correct resource identity permissions. The condition asked about here is: A research workspace uses a shared storage account that a platform team will delete during cleanup. A suitable correction is Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies; the targeted justification or result is: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments.

C:

Request the applicable regional VM-family quota or select available supported capacity. That operation would be relevant if: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. Its corresponding reason or verification is: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota. However the problem in this question is: A research workspace uses a shared storage account that a platform team will delete during cleanup. The requirement instead calls for Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies; the question-specific check is: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments.

D:

Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute. A separate source case supports that approach when: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. The supporting rationale or observable result is: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending. This question describes a different issue: A research workspace uses a shared storage account that a platform team will delete during cleanup. Address it through Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies, with the required justification or evidence: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments.

Question 8

A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. What should the team do instead of recreating the entire workspace?

  1. Request the applicable regional VM-family quota or select available supported capacity.
  2. Provision separate production and experimentation workspaces with distinct scoped policies.
  3. Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies.
  4. Set the workspace location to the approved European region before provisioning.

Explanation

Correct Answer

A:

Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota.

Incorrect Answers

B:

Provision separate production and experimentation workspaces with distinct scoped policies. It addresses another case: One organization has a production release process and an experimental notebook process with different access and change controls. For that case, the distinguishing justification or acceptance check is: Separate workspace boundaries permit independent RBAC, deployment approvals, monitoring, and resource governance without coupling exploratory jobs to production. The present case instead states: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. It calls for Request the applicable regional VM-family quota or select available supported capacity. Showing success for the other case would not establish: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota.

C:

The alternative, Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies, belongs to a different technical condition: A research workspace uses a shared storage account that a platform team will delete during cleanup. There the source-specific mechanism or proof is: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments. The condition asked about here is: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. A suitable correction is Request the applicable regional VM-family quota or select available supported capacity; the targeted justification or result is: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota.

D:

Set the workspace location to the approved European region before provisioning. That operation would be relevant if: A regulated training team must keep its new Azure Machine Learning workspace in an approved European Azure region. A provisioning template defaults to East US. Its corresponding reason or verification is: The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies. However the problem in this question is: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. The requirement instead calls for Request the applicable regional VM-family quota or select available supported capacity; the question-specific check is: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota.

Question 9

Several workspaces require a centrally consistent policy for encryption, tagging, and access. Manual workspace creation keeps drifting. What repeatable provisioning method should govern them?

  1. Request the applicable regional VM-family quota or select available supported capacity.
  2. Declare and verify the intended dependent Azure resources in the workspace deployment definition.
  3. Create or select the intended resource group and pass its name into workspace provisioning.
  4. Deploy the workspace configuration from version-controlled infrastructure-as-code templates.

Explanation

Correct Answer

D:

Declared resource configuration enables peer review, consistency, and reproducible environments across teams instead of untracked portal changes.

Incorrect Answers

A:

Request the applicable regional VM-family quota or select available supported capacity. This is useful for the distinct issue: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. The relevant technical rationale or evidence for that issue is: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota. Here the reported issue is: Several workspaces require a centrally consistent policy for encryption, tagging, and access. Manual workspace creation keeps drifting. The relevant response is: Deploy the workspace configuration from version-controlled infrastructure-as-code templates. The first result cannot verify this different correction: Declared resource configuration enables peer review, consistency, and reproducible environments across teams instead of untracked portal changes.

B:

Declare and verify the intended dependent Azure resources in the workspace deployment definition. It addresses another case: An MLOps team wants every new workspace to automatically connect to the correct Key Vault, Storage, and Application Insights dependencies. For that case, the distinguishing justification or acceptance check is: Explicit dependency mapping prevents an accidentally created workspace from relying on unintended shared services or missing platform dependencies. The present case instead states: Several workspaces require a centrally consistent policy for encryption, tagging, and access. Manual workspace creation keeps drifting. It calls for Deploy the workspace configuration from version-controlled infrastructure-as-code templates. Showing success for the other case would not establish: Declared resource configuration enables peer review, consistency, and reproducible environments across teams instead of untracked portal changes.

C:

The alternative, Create or select the intended resource group and pass its name into workspace provisioning, belongs to a different technical condition: A deployment pipeline fails because its target resource group does not exist, although the Azure subscription is accessible. There the source-specific mechanism or proof is: Workspaces belong to Azure resource groups; selecting an existing or created group resolves this prerequisite without granting extra model permissions. The condition asked about here is: Several workspaces require a centrally consistent policy for encryption, tagging, and access. Manual workspace creation keeps drifting. A suitable correction is Deploy the workspace configuration from version-controlled infrastructure-as-code templates; the targeted justification or result is: Declared resource configuration enables peer review, consistency, and reproducible environments across teams instead of untracked portal changes.

Question 10

A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. What should precede deletion?

  1. Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies.
  2. Request the applicable regional VM-family quota or select available supported capacity.
  3. Inventory and export required model, run, and governance records into retained storage.
  4. Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute.

Explanation

Correct Answer

C:

Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute.

Incorrect Answers

A:

Identify the workspace's dependent storage and other linked services, then protect or replace required dependencies. This is useful for the distinct issue: A research workspace uses a shared storage account that a platform team will delete during cleanup. The relevant technical rationale or evidence for that issue is: The workspace depends on linked Azure resources for artifacts and operations; deleting storage without migration can break active experiments. Here the reported issue is: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. The relevant response is: Inventory and export required model, run, and governance records into retained storage. The first result cannot verify this different correction: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute.

B:

Request the applicable regional VM-family quota or select available supported capacity. It addresses another case: A workspace administrator cannot create new experiments because the requested region has insufficient VM quota. For that case, the distinguishing justification or acceptance check is: Compute quota is regional and distinct from workspace metadata; blindly recreating the workspace does not increase available compute quota. The present case instead states: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. It calls for Inventory and export required model, run, and governance records into retained storage. Showing success for the other case would not establish: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute.

D:

The alternative, Apply meaningful resource tags and scoped cost allocation to the departments' workspaces and compute, belongs to a different technical condition: Two departments need separate chargeback reports for Azure ML training compute. They currently run all jobs in one workspace with no cost attribution. There the source-specific mechanism or proof is: Resource organization and cost tags support accountable consumption tracking; changing training code alone does not attribute Azure spending. The condition asked about here is: A workspace must be retired, but its model versions and audit artifacts are still needed for an open investigation. A suitable correction is Inventory and export required model, run, and governance records into retained storage; the targeted justification or result is: Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute.

Operationalizing Machine Learning and Generative AI Solutions (AI-300) Practice Tests