Refer to the exhibit.

An administrator has configured an Application Overrides for the ABC.Com application signature and set the Action to Allow This application control profile is then applied to a firewall policy that is scanning all outbound traffic. Logging is enabled in the firewall policy. To test the configuration, the administrator accessed the ABC.Com web site several times.
Why are there no logs generated under security logs for ABC.Com?
In FortiOS 7.6 Application Control, security logs are generated primarily for actions such as Block or Monitor, not for Allow actions.
What is happening in the exhibit
An Application Override is configured for ABC.Com
Type: Application
Action: Allow
The application control profile is applied to a firewall policy
Logging is enabled on the firewall policy
Traffic to ABC.Com is successfully allowed
However, no security logs appear for ABC.Com.
Why no logs are generated
In FortiOS 7.6:
Application Control logs are written to Security Logs when:
An application is Blocked
An application is Monitored
When an application action is set to Allow:
The traffic is permitted silently
No application control security log is generated
Even if policy logging is enabled
This is expected and documented behavior.
To generate logs for allowed applications, the action must be set to Monitor, not Allow.
Why the other options are incorrect
A. ABC.Com is hitting the category Excessive-Bandwidth Incorrect. ABC.Com has a higher-priority explicit override (priority 1), so it is not evaluated against the Excessive-Bandwidth filter.
B. The ABC.Com Type is set as Application instead of Filter Incorrect. Application-type overrides are valid and commonly used; this does not suppress logging.
C. The ABC.Com must be configured as a web filter profile Incorrect. This traffic is being evaluated by Application Control, not Web Filter.
Which statement correctly describes NetAPI polling mode for the FSSO collector agent?
NetAPI: Polls temporary sessions created on the DC when a user logs on or logs off and calls the NetSessionEnum function on Windows. It's faster than the WinSec and WMI methods; however, it can miss some logon events if a DC is under heavy system load. This is because sessions can be quickly created and purged form RAM, before the agent has a chance to poll and notify FG.
You have configured an application control profile, set peer-to-peer traffic to Block under the Categories tab. and applied it to the firewall policy. However, your peer-to-peer traffic on known ports is passing through the FortiGate without being blocked.
What FortiGate settings should you check to resolve this issue?
When the Application sensor receives traffic on that port, the protocol decoder will try to determine if the received data matches the HTTPS traffic In this case it will not match because it is P2P traffic, so this will class as violation and blocked The protocol decoder also try to determine what type of traffic it is, and even if it could not figure out it is P2P traffic, it still count as a violation because even though it does not know what it is, it knows for fact it is not HTTPS
An administrator wanted to configure an IPS sensor to block traffic that triggers the signature set number of times during a specific time period. How can the administrator achieve the objective?
In FortiOS 7.6, if an administrator wants to block traffic only after an IPS signature is triggered a specific number of times within a defined time window, this must be done using IPS filters with rate-based settings.
Why option D is correct
IPS filters allow administrators to match signatures based on attributes such as:
Severity
Protocol
CVE
Signature ID
IPS filters support rate-based actions using:
rate-mode periodical
rate-count
rate-duration
With rate-mode periodical, FortiGate:
Counts how many times a signature is triggered
Within a defined time period
And applies the configured action (for example, block) once the threshold is exceeded
This directly matches the requirement:
''block traffic that triggers the signature set number of times during a specific time period.''
Why the other options are incorrect
A . IPS group signatures, set rate-mode 60 Group signatures do not provide the required per-period rate-based blocking logic.
B . IPS packet logging option Logging does not enforce blocking behavior.
C . IPS signatures, rate-mode periodical option Rate-based controls are applied via IPS filters, not directly on individual signature definitions.
Refer to the exhibits.


You have implemented the application sensor and the corresponding firewall policy as shown in the exhibits.
You cannot access any of the Google applications, but you are able to access www.fortinet.com.
Which two actions would you take to resolve the issue? (Choose two.)
From the exhibits:
The firewall policy has Application Control enabled and uses certificate-inspection for SSL inspection.
The application sensor has Application and Filter Overrides with the following order (priority):
Excessive-Bandwidth with action Block
Google (vendor filter) with action Monitor
In FortiOS, Application and Filter Overrides are evaluated by priority (top-down). The first matching override is applied. If traffic matches an earlier override with Block, it will be blocked even if a later override would Monitor/Allow it.
Why Google apps fail while www.fortinet.com works:
Many Google applications can be detected as (or can trigger) the Excessive-Bandwidth behavior/signature depending on the specific service and traffic pattern.
Because Excessive-Bandwidth (Block) is above Google (Monitor), Google-related traffic may match the first rule and be blocked before the Google override is evaluated.
Access to www.fortinet.com works because that traffic is not matching the Excessive-Bandwidth override.
Therefore, to resolve:
B . Move up Google in the Application and Filter Overrides section to set its priority higher
This ensures Google matches the Google override before any broader blocking override is applied.
Fanny
7 days agoLaquita
14 days agoElfrieda
21 days agoJenise
28 days agoLeota
1 month agoDarnell
1 month agoMicaela
2 months agoSusana
2 months agoSimona
2 months agoStevie
2 months ago