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?
Explanation
Correct Answer
Deletion can remove the workspace's accessible artifacts; preserving evidence is a data-retention decision separate from stopping compute.
Incorrect Answers
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.
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.
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.