You plan to create an Azure Synapse Analytics dedicated SQL pool. You need to minimize the time it takes to identify queries that return confidential information as defined by the company's data…

Question

Exhibit

Options

• Asensitivity-classification labels applied to columns that contain confidential information
• Bresource tags for databases that contain confidential information
• Caudit logs sent to a Log Analytics workspace
• Ddynamic data masking for columns that contain confidential information

• A
  76% (25)
• B
  6% (2)
• D
  18% (6)

Explanation

A: You can classify columns manually, as an alternative or in addition to the recommendation- based classification: 1. Select Add classification in the top menu of the pane. 2. In the context window that opens, select the schema, table, and column that you want to classify, and the information type and sensitivity label. 3. Select Add classification at the bottom of the context window. C: An important aspect of the information-protection paradigm is the ability to monitor access to sensitive data. Azure SQL Auditing has been enhanced to include a new field in the audit log called data_sensitivity_information. This field logs the sensitivity classifications (labels) of the data that was returned by a query. Here's an example: https://docs.microsoft.com/en-us/azure/azure-sql/database/data-discovery-and-classification-

No community discussion yet for this question.