Azure SQL Database: Implementing Data Masking for Targets_ID Field | Exam DP-203 Practice Question | Microsoft

Implementing Data Masking for Targets_ID Field in Azure SQL Database | Exam DP-203 Practice Question

Question

You work as an expert consultant for Advanced Azure Learning where the IT team is working on an Azure SQL database titled AAL_Targets which has a table titledTargets_2021

In the table, there is a field Targets_ID having type varchar(22)

Required: The team is to implement masking for the Targets_ID field as given below: • Setting the initial 3 prefix characters as "exposed" • Setting the final 3 suffix characters as "exposed" • Setting the rest of the characters as "masked" The IT team is planning to use data masking with a credit card function mask.

As an expert, you need to tell if the given solution meets the requirements and achieves the goal.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

Correct Answer: B

The below figure described the various masking functions with their masking logic:

As can be seen from the above image, utilizing data masking with a credit card function mask won't be successful.

To accomplish the requirements, AAL needs to use Custom Text data masking, which will expose the first and last characters as mentioned and add a custom padding string in the middle.

Reference:

To know more about dynamic data masking, please visit the below-given link:

As per the given requirements, the following masking rules need to be applied to the Targets_ID field:

  • The initial 3 prefix characters should be exposed.
  • The final 3 suffix characters should be exposed.
  • The remaining characters should be masked.

The IT team is planning to use a credit card function mask to achieve this.

A credit card function mask is a built-in data masking function in Azure SQL Database that replaces all but the last four digits of a credit card number with "X" characters. This function is not suitable for the given requirements because it only masks a specific type of data (credit card numbers) and does not allow for custom masking rules to be applied.

Therefore, the given solution does not meet the requirements and does not achieve the goal of masking the Targets_ID field according to the specified rules. The IT team will need to use a custom masking function or solution to achieve the desired result.