Exam DP-203 topic 3 question 38 discussion

Correct

It should be Row Level security not column since limited for some users

Tax Numbers (Row-Level Security): Use Row-Level Security (RLS) to restrict access to tax numbers based on user roles or group membership. You can define a security policy with a predicate function to filter rows based on the user's identity or role. For example: sql CREATE SECURITY POLICY TaxNumberPolicy ADD FILTER PREDICATE xxxx

The question describes fields named credit card and tax, which hints that this is a purchase type of record, so the "Tax" value would likely be a single column. The assumption would dictate that column level security should be used here.

Correct awnser With Row level security, will remove rows and we don't want that, we just want hide the column, so currect awnser

Row level security Column level security primarily controls access to specific columns within a table. It restricts users' ability to read or write data in certain columns based on their permissions. However, it does not control which rows of data users can access. For the requirement that tax numbers must be visible only to specific users, it's not about restricting access to a specific column (as would be the case with column level security). Instead, it's about controlling access to certain rows of data based on specific criteria, such as user roles or permissions. Row level security allows you to restrict access to rows of data based on conditions defined in security policies

masking ,row Level

It should be Column-level security as it ensures those specific users can access only certain columns of a table. Whereas, RLS can help you to create a group membership or execution context in order to control not just columns in a database table, but actually, the rows.