DP-203 · Question #238
You are designing database for an Azure Synapse Analytics dedicated SQL pool to support workloads for detecting ecommerce transaction fraud. Data will be combined from multiple ecommerce sites and…
The correct answer is C. column-level encryption. Use Always Encrypted to secure the required columns. You can configure Always Encrypted for individual database columns containing your sensitive data. Always Encrypted is a feature designed to protect sensitive data, such as credit card numbers or national identification…
Question
You are designing database for an Azure Synapse Analytics dedicated SQL pool to support workloads for detecting ecommerce transaction fraud. Data will be combined from multiple ecommerce sites and can include sensitive financial information such as credit card numbers. You need to recommend a solution that meets the following requirements:
- Users must be able to identify potentially fraudulent transactions.
- Users must be able to use credit cards as a potential feature in
models.
- Users must NOT be able to access the actual credit card numbers.
What should you include in the recommendation?
Options
- ATransparent Data Encryption (TDE)
- Brow-level security (RLS)
- Ccolumn-level encryption
- DAzure Active Directory (Azure AD) pass-through authentication
How the community answered
(48 responses)- A4% (2)
- B8% (4)
- C85% (41)
- D2% (1)
Explanation
Use Always Encrypted to secure the required columns. You can configure Always Encrypted for individual database columns containing your sensitive data. Always Encrypted is a feature designed to protect sensitive data, such as credit card numbers or national identification numbers (for example, U.S. social security numbers), stored in Azure SQL Database or SQL Server https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-
Topics
Community Discussion
No community discussion yet for this question.