Question 150
While validating a Snowflake workload, engineers observe: A Snowsight worksheet succeeds for an administrator but fails for a colleague because the colleague's selected role and warehouse differ. What is the principal technical cause in this scenario?
Explanation
Correct Answer
The described symptoms indicate that worksheet behavior depends on the active role, warehouse and session context. The appropriate resolution is: Have both users verify worksheet role, warehouse, database and schema before changing SQL. Confirm with: The colleague executes the intended query under the approved role and context.
Incorrect Answers
An interactive worksheet is not required to execute SQL through supported clients. “Run the script with an approved Snowflake command-line or driver connection” would address that alternative cause, not the condition in this question: worksheet behavior depends on the active role, warehouse and session context.
“Use the supported Snowflake CLI or other approved automation client with versioned commands” responds to this separate finding: manual browser execution is not an auditable repeatable deployment interface. This question instead needs “Have both users verify worksheet role, warehouse, database and schema before changing SQL”, so the alternative does not meet the stated condition.
The development workflow lacks an authoritative versioned repository for SQL artifacts. “Adopt supported Git-based source management and a reviewed deployment process for SQL definitions” applies to that separate problem. The observed case is a Snowsight worksheet succeeds for an administrator but fails for a colleague because the colleague's selected role and warehouse differ; choosing this alternative would address the wrong failure mode.