Question 350
For a global logistics company, the original problem was: A security review finds a shared role with direct access to raw customer names even though applications need only a masked view. What observation confirms success?
Explanation
Correct Answer
The consumer role queries its approved interface but cannot read the raw customer table directly. This validates the relevant action: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns. The underlying Snowflake behavior is: Least privilege is enforced at object and policy boundaries, not by naming tables as sensitive.
Incorrect Answers
The affected identity cannot read the restricted view through any remaining authorized role chain. This evidence tests a DIFFERENT situation: A data steward revokes a user's role but their previous worksheet continues to query an authorized view under a different active role. The correction required in this case is: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.
Two test roles see only their permitted country rows while a governed admin test gets its required scope. This evidence tests a DIFFERENT situation: A regional sales analyst can read rows for every country despite having permission only for their own region. The correction required in this case is: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.
Authorized corporate connections succeed while an unapproved test source is rejected. This evidence tests a DIFFERENT situation: A company wants to restrict SQL console sign-in to trusted corporate networks but users can log in from unmanaged locations. The correction required in this case is: Separate raw-data owner privileges from consumer permissions and expose policy-protected views or columns.