Microsoft Certified: Fabric Analytics Engineer AssociatePlan and implement data analytics solutions (10-15%)Medium
A company is designing a new data analytics solution in Microsoft Fabric. They want to ensure that sensitive customer information, such as social security numbers and credit card details, is protected while still allowing analysts to work with other non-sensitive customer data. The solution must provide granular access control based on user roles. Which security feature should be implemented?
- AWorkspace-Level Security
- BRow-Level Security (RLS)
- CObject-Level Security (OLS)
- DColumn-Level Security (CLS)
Show answer & explanationAnswer & explanation
Correct answer: D. Column-Level Security (CLS)
Column-Level Security (CLS) allows you to restrict access to specific columns in a table based on the user's role or permissions. This is ideal for protecting sensitive data fields while allowing access to other data in the same table.
Why the other options are wrong
- A. Workspace-Level Security controls access to an entire Fabric workspace, which is too broad and does not provide granular control over specific columns within data items.
- B. Row-Level Security (RLS) restricts access to rows in a table, not specific columns, which would not hide sensitive columns from view.
- C. Object-Level Security (OLS) restricts access to entire database objects (like tables or views), not individual columns within an object.
Column-Level Security (CLS)
A security feature that restricts access to specific columns in a table based on the user's execution context or group membership.
- Protects sensitive data fields within a table.
- Allows different users to see different subsets of columns.
- Implemented at the database or data model level.
Memory trick: Columns are like secret compartments in a data drawer.