In FortiOS 7.4.1 and FortiAnalyzer 7.4.1, the "Unhandled" status in logs typically signifies that the FortiGate encountered a security event but did not take any specific action to block or alter it. This usually occurs in the context of Intrusion Prevention System (IPS) logs.
IPS logs with action=pass: When the IPS engine inspects traffic and determines that it does not match any known attack signatures or violate any configured policies, it assigns the action "pass". Since no action is taken to block or modify this traffic, the status is logged as "Unhandled."
Let's look at why the other options are incorrect:
An AV log with action=quarantine: Antivirus (AV) logs with the action "quarantine" indicate that a file was detected as malicious and moved to quarantine. This is a definitive action, so the status wouldn't be "Unhandled."
A WebFilter log will action=dropped: WebFilter logs with the action "dropped" indicate that web traffic was blocked according to the configured web filtering policies. Again, this is a specific action taken, not an "Unhandled" event.
An AppControl log with action=blocked: Application Control logs with the action "blocked" mean that an application was denied access based on the defined application control rules. This is also a clear action, not "Unhandled."
Question 2
Exhibit.
What can you conclude about these search results? (Choose two.)
Options:
A.
They can be downloaded to a file.
B.
They are sortable by columns and customizable.
C.
They are not available for analysis in FortiView.
D.
They were searched by using text mode.
Answer:
A, D
Question 3
Exhibit.
What can you conclude from this output?
Options:
A.
There is not disk quota allocated to quarantining files.
B.
FGT_B is the Security Fabric root.
C.
The allocated disk quote to ADOM1 is 3 GB.
D.
Archive logs are using more space than analytic logs.