Azure ML Studio Terminal Jupyter Kernel Configuration
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure Machine Learning workspace. You connect to a terminal session from the Notebooks page in Azure Machine Learning studio. You plan to add a new Jupyter kernel that will be accessible from the same terminal session. You need to perform the task that must be completed before you can add the new kernel. Solution: Create a compute instance. Does the solution meet the goal?
Community Votes
73% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question assesses whether candidates understand that you cannot add a kernel in a terminal session unless the terminal session itself (and its backing compute instance) is already provisioned.
This question tests the understanding of Azure Machine Learning compute resources, specifically the relationship between compute instances and terminal sessions. The community consensus is that a compute instance must already exist to provide the underlying infrastructure for any terminal session or Jupyter kernel.
Candidates often choose 'Yes' because they assume creating a compute instance is part of the immediate configuration steps for a kernel, failing to realize the prerequisite nature of the compute instance for the existing terminal session.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.