exam questions

Exam DP-203 All Questions

View all questions & answers for the DP-203 exam

Exam DP-203 topic 3 question 38 discussion

Actual exam question from Microsoft's DP-203
Question #: 38
Topic #: 3
[All DP-203 Questions]

HOTSPOT
-

You have an Azure Synapse Analytics dedicated SQL pool that hosts a database named DB1.

You need to ensure that DB1 meets the following security requirements:

• When credit card numbers show in applications, only the last four digits must be visible.
• Tax numbers must be visible only to specific users.

What should you use for each requirement? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer:

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
haythemsi
Highly Voted 1 year, 10 months ago
Correct
upvoted 11 times
...
kim32
Highly Voted 1 year, 10 months ago
It should be Row Level security not column since limited for some users
upvoted 10 times
Matt2000
1 year, 7 months ago
yes. that is what row-level security is designed for.
upvoted 1 times
...
francocalvo
1 year, 10 months ago
I think the answer is correct. Imagine a team where all have access to the table, but just one person needs access to the tax numbers, you can use column-level to disable access for all the other people except the one that needs it
upvoted 19 times
...
...
9370d83
Most Recent 1 week, 1 day ago
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
upvoted 1 times
...
7082935
7 months, 2 weeks ago
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.
upvoted 2 times
...
Persius92
11 months, 2 weeks ago
Correct awnser With Row level security, will remove rows and we don't want that, we just want hide the column, so currect awnser
upvoted 1 times
...
MohamedBI12
1 year ago
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
upvoted 1 times
...
kkk5566
1 year, 6 months ago
masking ,row Level
upvoted 1 times
kkk5566
1 year, 6 months ago
should be Column-level security
upvoted 6 times
...
...
eternalamit5
1 year, 7 months ago
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.
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago