DP-600 · Question #141
You have a Fabric warehouse named Warehouse1 that contains a table named Table1. Table1 contains customer data. You need to implement row-level security (RLS) for Table1. The solution must ensure…
The correct answer is D. FUNCTION E. SECURITY POLICY. Implementing RLS in SQL (including Fabric Warehouse) requires two objects: (D) an inline table-valued FUNCTION that acts as the security predicate - it evaluates each row and returns rows the current user is allowed to see, typically by comparing a column to USER_NAME() or a…
Question
You have a Fabric warehouse named Warehouse1 that contains a table named Table1. Table1 contains customer data. You need to implement row-level security (RLS) for Table1. The solution must ensure that users can see only their respective data. Which two objects should you create? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Options
- ADATABASE ROLE
- BSTORED PROCEDURE
- CCONSTRAINT
- DFUNCTION
- ESECURITY POLICY
How the community answered
(58 responses)- A3% (2)
- B7% (4)
- C2% (1)
- D88% (51)
Explanation
Implementing RLS in SQL (including Fabric Warehouse) requires two objects: (D) an inline table-valued FUNCTION that acts as the security predicate - it evaluates each row and returns rows the current user is allowed to see, typically by comparing a column to USER_NAME() or a mapped value; and (E) a SECURITY POLICY that binds that function to the target table as a filter predicate. Together, these cause SQL Server/Fabric to automatically apply the row filter on every query. A DATABASE ROLE controls object-level permissions, not row-level filtering. STORED PROCEDURE and CONSTRAINT are not part of the RLS implementation pattern.
Topics
Community Discussion
No community discussion yet for this question.