What are the three conflict resolution rules in the Threat Prevention Policy Layers?

This incorrectly substitutes 'conflict on action' and 'conflict on scope' for the address-based and settings-based categories - Threat Prevention conflict resolution does not define an 'action' conflict category.

This includes 'conflict on scope' rather than 'conflict on address' - the correct address-related conflict resolution rule is scoped to specific addresses, not a generic scope category, and 'conflict on settings' appears correctly but the other two entries do not match the defined rules.

When multiple Threat Prevention profiles apply to overlapping traffic, Check Point resolves the conflict via three specific mechanisms: conflict on settings (which profile's protection configuration takes precedence), conflict on address (how overlapping source or destination scopes are reconciled), and conflict on exception (how exception rules from competing profiles are merged or prioritized). Together these three rules ensure deterministic enforcement when profiles overlap.

This incorrectly names 'conflict on action' and 'conflict on destination' as conflict resolution rules - neither is defined in Check Point Threat Prevention conflict resolution; destination-specific logic is covered under 'conflict on address.'