Question 1
An engineer is about to deploy an Azure Machine Learning workspace for a regulated training project. The Azure CLI is still signed in to a different subscription from an earlier task. The approved subscription and resource group have been provided. What should the engineer do before provisioning?
Explanation
Correct Answer
The CLI uses subscription and resource-group scope to select the deployment target. Selecting that context before creation and confirming the returned ARM ID directly prevents deployment to the previous subscription.
Incorrect Answers
A workspace name is not an Azure subscription selector. Renaming the workspace would leave the Azure CLI signed in to the wrong subscription, risking creation under an unauthorized billing and access boundary.
A workspace-level data-scientist role governs operations in a workspace; it does not change the subscription chosen for a new resource deployment. The wrong-subscription failure is a CLI scope problem.
This deliberately provisions in an unapproved subscription and introduces a separate, potentially limited migration process. The requirement is to deploy correctly the first time using the approved scope.