A data scientist has been running an Amazon SageMaker notebook instance for a few weeks. During this time, a new version of Jupyter Notebook was released along with additional software updates. The…

Question

Options

• ACall the CreateNotebookInstanceLifecycleConfig API operation
• BCreate a new SageMaker notebook instance and mount the Amazon Elastic Block Store (Amazon
• CStop and then restart the SageMaker notebook instance
• DCall the UpdateNotebookInstanceLifecycleConfig API operation

• A
  3% (1)
• B
  3% (1)
• C
  87% (34)
• D
  8% (3)

Explanation

Amazon SageMaker applies the latest platform updates - including Jupyter Notebook upgrades and security patches - to a notebook instance when it starts up. A notebook instance that has been running continuously for weeks will not automatically apply updates that were released after it was last started. The correct and simplest way to apply the latest SageMaker-managed updates is to stop the instance and then restart it: upon restart, SageMaker automatically provisions the instance with the most current software stack. Option A (CreateNotebookInstanceLifecycleConfig) creates a new lifecycle config but does not by itself update an existing running instance. Option B (creating a new instance and mounting the EBS volume) is unnecessary complexity. Option D (UpdateNotebookInstanceLifecycleConfig) modifies a lifecycle configuration, not the instance software version. Stopping and restarting (option C) is the official, supported mechanism for applying SageMaker platform updates to an existing notebook instance.

No community discussion yet for this question.