SnowPro Associate: Platform Question 68
Single answer● Notebook sessionsA data analyst is using a Snowflake Notebook to explore sales data and run Python cells against a small warehouse. After stepping away for a meeting, the analyst returns and sees that the notebook session is no longer active. They want to understand what happened and how notebook sessions behave so they can avoid confusion in the future. Which statement best describes Snowflake Notebook session behavior in this scenario?
- A
Notebook sessions are tied to compute resources and can end after inactivity, requiring the user to start or reconnect to a session before continuing.
- B
Notebook sessions remain active indefinitely until the notebook object is deleted, even if the user closes the browser or is inactive for hours.
- C
Notebook sessions are stored inside the virtual warehouse, so resizing or suspending the warehouse permanently deletes the notebook and its code cells.
- D
Notebook sessions automatically migrate to another user's session if they have access to the same notebook, allowing shared interactive state across users.
Show answer and explanation
Correct answer: A
Explanation
This question tests the distinction between a Snowflake Notebook as a saved object and a notebook session as a live interactive runtime. In practice, users commonly assume that if the notebook still exists, the session must also still be running. Snowflake separates persisted notebook content from the active execution environment. Session state can end due to inactivity or other lifecycle events, while the notebook and its saved cells remain available. For exam purposes, remember that compute resources support execution, but persisted notebook content is not destroyed simply because a warehouse suspends or a session ends. This aligns with Snowflake documentation and best practices around interactive workloads: understand the lifecycle of sessions, expect that active runtimes may need to be restarted, and distinguish saved artifacts from transient compute-backed state.
- A. Correct.
Correct. In Snowflake Notebooks, the interactive session is separate from the notebook object itself and depends on active compute. If the session becomes inactive or stops, the user may need to start or reconnect to a session to continue executing cells. This reflects how interactive development environments behave in Snowflake: notebook content is saved, but the live session is not guaranteed to persist indefinitely.
- B. Incorrect.
Incorrect. This confuses the persisted notebook object with the live notebook session. The notebook itself can be saved, but the interactive session does not stay active forever. Inactivity or session lifecycle events can cause the session to end.
- C. Incorrect.
Incorrect. A virtual warehouse provides compute for executing workloads, but suspending or resizing it does not permanently delete the notebook object or its saved code cells. The misconception is treating notebook storage as if it were embedded in warehouse compute rather than a persisted object managed separately from transient execution state.
- D. Incorrect.
Incorrect. Access to the same notebook does not mean users share one live interactive session state automatically. Notebook sessions are not handed off between users in that way. A user with access can open the notebook, but their interaction is not the same as inheriting another user's active runtime state.