Exam DP-203 topic 3 question 24 discussion

By discard, is C, you can create a symetric key to encript a data, for example one column, and then use this data as feature of the model https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/encrypt-a-column-of-data?view=sql-server-ver15 The other options that not meet the requeriments: - TDE encript data, but decrypt when you query https://docs.microsoft.com/en-us/azure/azure-sql/database/transparent-data-encryption-tde-overview?tabs=azure-portal - RLS is for row restriction, not meet the requeriment - Azure AD pass-through is for authentication

C. Column-level encryption

C. Column-level encryption Explanation: The given requirement is to enable users to utilize credit card data for model features but to not have access to the actual credit card numbers. Column-level encryption serves this purpose best as it allows for specific columns (in this case, the credit card number column) to be encrypted, while still enabling operations on the data. A. Transparent Data Encryption (TDE): This encrypts the physical files of the database, but not specific columns. It doesn't fit the requirement here. B. Row-level security (RLS): This restricts data access at the row level based on certain filters. It doesn't offer column-specific security, and thus isn't the best choice here. D. Azure Active Directory (Azure AD) pass-through authentication: This is an authentication method, not an encryption method. It would not be applicable for protecting specific data within the database.

Looks like the column level encryption is still in preview. https://azure.microsoft.com/en-us/updates/columnlevel-encryption-for-azure-synapse-analytics/

IS column level encryption supported on Dedicated SQL Pools? The question is relate to Dedicated Pool?

correct