Answer is C
https://azure.microsoft.com/en-ca/updates/column-level-security-is-now-supported-in-azure-sql-data-warehouse/
You can use CLS to manage user access to specific columns in your tables in a simpler manner, without having to redesign your data warehouse. CLS eliminates the need to maintain access restriction logic away from the data in another application or introduce views for filtering out sensitive columns for a subset of users.
C. Azure SQL Data Warehouse now supports column-level security (CLS), an additional capability for managing sensitive data in the cloud.
You can use CLS to manage user access to specific columns in your tables in a simpler manner, without having to redesign your data warehouse. CLS eliminates the need to maintain access restriction logic away from the data in another application or introduce views for filtering out sensitive columns for a subset of users.
To help secure your data, simply define a security policy on your table columns with the standard GRANT T-SQL statement.
Option C, column-level security, allows you to control access to specific columns within a table based on user permissions. This means you can restrict access to sensitive customer contact information, such as phone numbers, only to authorized users or roles within the organization. By implementing column-level security, you can ensure that business analysts are limited in their access to customer contact information, preventing them from viewing or analyzing the phone numbers, which are not analytically relevant in this case.
Answer is 100% C. The only way you can prevent users from seeing sensitive information is either through partial masking (partially visible) or complete blocking by using column level security.
The answer is D.
Between C and D, D can "minimize the number of different Azure services needed to achieve the business goals." But C needs to distribute role to the user, that is more complicated to apply.
It's C because of this requirement : "Limit the business analysts' access to customer contact information, such as phone numbers, because this type of data is not analytically relevant."
You don't secure data with sensitivity labels. They can only be used to identify who has accessed sensitive data. So it has to be column level security. There should really have been a Data Masking option here instead of column level security.
This section is not available anymore. Please use the main Exam Page.DP-203 Exam Questions
Log in to ExamTopics
Sign in:
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.
echerish
Highly Voted 2 years, 8 months agoFredNo
Highly Voted 2 years, 5 months agoimatheushenrique
Most Recent 1 month, 2 weeks agokkk5566
8 months agovctrhugo
10 months, 2 weeks agoXiltroX
1 year, 5 months agoanks84
1 year, 7 months agoyyyhhh
1 year, 8 months agoDeeksha1234
1 year, 8 months agodmgArtyco
1 year, 8 months agoRemedios79
1 year, 10 months agoDavico93
1 year, 10 months agoArunava05
1 year, 11 months agoAlCubeHead
2 years agocoulio
2 years, 3 months agoRemedios79
1 year, 10 months agoPallaviPatel
2 years, 3 months agoRaghu108
2 years, 3 months ago