Question 110
Consider this Snowflake situation: A query produces unexpected results because the application implicitly switches roles during its login process. Which platform behavior BEST explains the appropriate solution?
Explanation
Correct Answer
The decisive Snowflake behavior is: Effective permissions depend on active role context, which can differ across sessions using the same user. It supports the response: Set the intended primary role and verify active secondary-role behavior for the session. Confirm it with this observable result: The same test query succeeds or fails according to the explicitly selected permitted role. Distinguish this mechanism from superficially related Snowflake features.
Incorrect Answers
The offered statement is true for this other mechanism: Unqualified Snowflake object names are resolved using current session namespace context. It does not explain the facts described here, which follow from: Effective permissions depend on active role context, which can differ across sessions using the same user.
This principle describes a separate cause: Snowflake separates virtual warehouse compute from database storage so independent workloads can access the same governed data. The reported condition is governed by: Effective permissions depend on active role context, which can differ across sessions using the same user. The two mechanisms should not be conflated.
Warehouses are billable compute resources that need not remain active between intermittent workloads. That explanation applies to a different technical failure. Here the controlling principle is: Effective permissions depend on active role context, which can differ across sessions using the same user.