Question 400
An emergency change is proposed for: A financial company finds that outbound DLP events are logged but not blocked although its policy requires prevention. Which caution is most important for this specific change?
Explanation
Correct Answer
The most relevant caution is that observing a DLP detection in a log is not the same as enforcing an upload block. The case concerns a financial company finds that outbound DLP events are logged but not blocked although its policy requires prevention. The safer path is to compare the data pattern match confidence and currently configured Monitor or Block action and then, after verification, to apply the authorized blocking response to verified high-confidence DLP detections. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
DNS filtering by itself cannot guarantee prevention of every destination accessed without a lookup. The check concerns DNS filtering by itself cannot guarantee prevention of every destination accessed without a lookup, not confirming that observing a DLP detection in a log is not the same as enforcing an upload block.
Enabling web filtering without selecting a block action for the category may not enforce the restriction. This assesses enabling web filtering without selecting a block action for the category may not enforce the restriction; it does not determine the reported condition—a financial company finds that outbound DLP events are logged but not blocked although its policy requires prevention.
Allowing SaaS traffic should not be mistaken for authorizing every payload carried by the application. The case-specific requirement is confirming that observing a DLP detection in a log is not the same as enforcing an upload block, which that option does not establish.