“After the IPS engine examines the traffic stream for a signature match, FortiGate scans packets for matches, in this order, for the application control profile:
1. Application and filter overrides ...”
“Because application overrides are applied first in the scan, these two applications are allowed and generate logs.”
“The priority in which application and filter overrides are placed takes precedence.”
Technical Deep Dive:
The correct answer is C. Application and Filter Overrides .
If you already set the P2P category to Block , but some peer-to-peer traffic is still being allowed, the first thing to check is whether there is an application override or filter override that matches that traffic before the category action is applied. FortiGate processes Application and Filter Overrides before Categories , so any matching override set to Allow or Monitor will effectively bypass the category block.
Why the others are wrong:
A only affects user-facing block-page behavior for HTTP/HTTPS applications, not whether P2P is blocked.
B is for enforcing expected services on expected ports and for blocking applications on non-default ports. It is not the first place to look when a category block is being bypassed.
D concerns web categorization, not application-control category enforcement.
Operationally, this is a classic troubleshooting sequence: first inspect the override table , then the category action , then logs under Application Control to see which signature and action actually matched.
