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?
Explanation
Correct Answer
The workspace resource location is selected at creation; tagging an East US deployment cannot relocate its services or data dependencies.
Incorrect Answers
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.
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.
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.