Question 970
The service team faces this requirement: DLP matches ordinary invoice numbers as credit cards because a rule uses overly weak evidence. Which change is appropriate without granting unrelated privileges?
Explanation
Correct Answer
Tune policy use of the sensitive information type to a defensible confidence or evidence threshold. The case concerns adjust confidence for a built-in sensitive type: DLP matches ordinary invoice numbers as credit cards because a rule uses overly weak evidence. Sensitive type precision requires balancing detection evidence with false-negative impact. This answers the first configuration or remediation decision because it addresses the explicit constraint. A controlled acceptance test should show: actual protected data still matches while ordinary invoice fixtures are excluded. It addresses the direct requirement rather than a neighboring configuration.
Incorrect Answers
Sensitive information type design should encode meaningful evidence beyond superficial character similarity. The records needed for this specific case concern: Review match evidence, supported confidence levels, and representative valid and invalid samples.
Content explorer inventories classified content; it is not the same as a history of all user labeling actions. The current corrective requirement is: Tune policy use of the sensitive information type to a defensible confidence or evidence threshold.
Automated classification depends on the quality of classifiers and supported content locations. The appropriate acceptance check is: Actual protected data still matches while ordinary invoice fixtures are excluded.