Question 430
For an e-commerce operations team, the original problem was: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. What observation confirms success?
Explanation
Correct Answer
The affected identity cannot read the restricted view through any remaining authorized role chain. This validates the relevant action: Inspect all effective role grants and session role context, then revoke the unintended privilege path. The underlying Snowflake behavior is: An effective entitlement may arrive through multiple direct or inherited roles.
Incorrect Answers
The consumer role queries its approved interface but cannot read the raw customer table directly. This evidence tests a DIFFERENT situation: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. The correction required in this case is: Inspect all effective role grants and session role context, then revoke the unintended privilege path.
Test queries enforce required column protections and disallow unapproved data export paths. This evidence tests a DIFFERENT situation: An analyst creates an external function that exports restricted data even though its normal table queries are masked. The correction required in this case is: Inspect all effective role grants and session role context, then revoke the unintended privilege path.
Representative project queries appear with traceable tags, allowing a reasoned chargeback allocation. This evidence tests a DIFFERENT situation: A finance report groups all usage by account and cannot assign cost to engineering projects sharing a warehouse. The correction required in this case is: Inspect all effective role grants and session role context, then revoke the unintended privilege path.