DP-700 · Question #87
You have a Fabric workspace that contains a warehouse named Warehouse1. Warehouse1 contains a table named Customer. Customer contains the following data (CustomerID, FirstName, LastName, Phone…
This question tests your ability to implement column-level security in Microsoft Fabric Warehouse using T-SQL GRANT statements to restrict access to specific columns of a table.
Question
Explanation
This question tests your ability to implement column-level security in Microsoft Fabric Warehouse using T-SQL GRANT statements to restrict access to specific columns of a table.
Approach. The correct approach is to use a GRANT SELECT statement that explicitly lists only the columns User1 is permitted to access, omitting the CreditCard column. The statement should follow the form: GRANT SELECT ON OBJECT::dbo.Customer (CustomerID, FirstName, LastName, Phone) TO [[email protected]]. By listing only the permitted columns in the GRANT, CreditCard is never included in the permission, so User1 cannot query it. Alternatively, you could GRANT SELECT at the table level and then issue a DENY SELECT ON dbo.Customer(CreditCard) TO [[email protected]], but the column-enumerated GRANT is the cleaner, single-statement solution Microsoft expects here.
Concept tested. Column-Level Security (CLS) in Microsoft Fabric Warehouse via T-SQL GRANT/DENY - specifically granting SELECT permission on a subset of columns in a table to an Entra user, thereby preventing access to sensitive columns (CreditCard) without denying access to the table entirely.
Reference. Microsoft Learn – Microsoft Fabric: Column-level security in Fabric data warehousing (https://learn.microsoft.com/en-us/fabric/data-warehouse/column-level-security)
Topics
Community Discussion
No community discussion yet for this question.