Refer to the exhibit, which shows a partial web filter profile configuration.

Which action will FortiGate take if a user attempts to access www.dropbox.com, which is categorized as File Sharing and Storage?
Refer to the exhibit, which shows a partial web filter profile configuration.
Which action will FortiGate take if a user attempts to access www.dropbox.com, which is categorized as File Sharing and Storage?
The FortiGate web filter processes the URL filter first, followed by the FortiGuard category-based filter. In this scenario, the URL filter allows access to *.dropbox.com, which means the connection is passed to the next filtering step. The FortiGuard category-based filter then checks the URL and finds that it falls under the File Sharing and Storage category, which is set to block. Consequently, FortiGate will block the connection based on the FortiGuard category-based filter configuration.
Order of operation is: 1. URL filter 2. FortiGuard Web Filtering 3. Web content filter 4. Web script filter 5. Antivirus scanning
URL filter is 'allow' not 'exempt' so it will be block on step 2: FortiGuard Category. Correct answer is A
Coorect! If with "allow" action the next step is to check FortiGuard category. If the category action is "block" the connection is blocked. Correct answer is A
https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632
A is actually correct. My bad
A is actually correct. My bad
Coorect! If with "allow" action the next step is to check FortiGuard category. If the category action is "block" the connection is blocked. Correct answer is A
I aqree!!
So, I didn’t find this is the training material, however it’s specified on Fortinet.com, correct answer is A. When FortiGate performs a web filter check, it will first check the static URL filter list (if applied to the profile) and based on the action, will then perform the FortiGuard category check. 'Action' descriptions in Static URL see bellow: - 'Block' -> destination is blocked and session dropped, no further category check is needed. - 'Allow' -> destination is allowed from the static URL list, FortiGate proceeds with checking the category to decide further action. - 'Exempt' -> destination is exempted from further inspection and traffic is allowed. - https://community.fortinet.com/t5/FortiGate/Technical-Tip-Difference-between-action-Allow-and-Exempt-in/ta-p/231334
A is actually correct
Since URL filter allow (unlike exempt) will still check the category, the session will be blocked and content filter won't work.
The URL filter is set to 'allow' so the FortiGate proceeds to category filter which is set to 'deny', making FortiGate drop the packet. 'Exempt' would have skipped the other steps and allowed the packet.
I've simulated configuration. It is being blocked because of category block. The answer is 100% A.
My bad, the action is 'allow' and not 'exempt' so the URL will be blocked by Category filter
Correct answer is A https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632
A) Because URL Filter is allow and not "exempt" which will make the operation go to fortiguard filter which is block, but if it was "exempt" in URL filter then answer is D.
URL filter is 'allow' not 'exempt' so it will be block on step 2: FortiGuard Category.
Answer A is correct. Reason: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Difference-between-action-Allow-and-Exempt-in/ta-p/231334 In the URL Filter (which is checked FIRST) dropbox.com is ONLY allowed which prompts Fortigate to check fruther in the UTM (next ist FortiGuard Web Filtering which BLOCKS file sharing). In Order for D to be correct, the URL Filter would need to set dropbox.com on "exempt" (which leads the fortigate to stop checking and allow the traffic at once).
The correct answer is A. Explanation: https://community.fortinet.com/t5/FortiGate/Technical-Note-List-of-web-filtering-steps-and-their-order-of/ta-p/197439?cmd=displayKC&docType=kc&externalId=11158 Web filters are applied in this specific order: 1 URL Filter 2 FortiGuard Web Filter (also called Category Block) 3 Content Filter (Web Content Filter) 4 Script Filter (filters for Java applets, ActiveX controls and cookies, CLI config only) 5 Antivirus scanning The URL filter list is processed in order from top to bottom. An exempt match stops all further checking including AV scanning. An allow match exits the URL filter list and checks the other web filters. In this case, the action in the URL Filter is "allow" therefore the FortiGate checks the other web filters. In this case, the next web filter is the FortiGuard Category Based Filter, which in this case is set to block. Therefore traffic is blocked based on the FortiGuard Category Based Filter.
URL filter is check first and action is ALLOW the URL is exempted from all further inspection.
"During Web filtering inspection, FortiGate first check the static URL filter list" - Study Guide, page 351.
I tested this settings on our Fortigate. The behavior was the same, like is written in this article: https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632 So the correct answer is A
Same as LiliRose
https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632
A is correct With an allow action on the static URL filter, it will still continue checking the other filters. In order to prevent this you will need to use exempt, which will stop further checks and allows the site.
Tested in the lab with the same example. (A)
A is correct
A it's OK
A 100%
A - the best way to verify the solution is just simulate it on the Lab
Correct Answer is A. URL filter in "allow" the next check is Category, if category is block, the connection is blocked. To allow the connection, the correct answer is "Exempt"
if it was exempt instead of allow on URL filter, it would not be blocked.
Web Filtering inspection is performed in the following order: 1 - URL filter 2 - FortiGuard Web Filter (FortiGuard Category Based Filter) 3 - Web Content Filter 4 - Advanced Filter Options In this case: URL Filter - allow. But in the second step, the blocks by the Category Based Filter.
A - action allow on local wf do not bypass fortiguard wF
Correct answer is 100% A. Check Study Guide p350 During web Filtering Inspection, Fortigates first check the Static Url Filter list, then the fortiguard categories, and then the content filter list. So even if the static url is allowing the site, it will be blocked and dropped by the fortiguard categories action.
A is indeed correct
D is correct - Web Filter operations order - Static URL Filter is first NSE 7 Study Guide page 351
A is correct.
A, because its A
Enterprise_Firewall_7.0_Study_Guide-Online.pdf p 351 url filter -> FortiGuard Web Filter -> Web Content Filter -> Advanced Filter Options Allow -> Block
Sorry A, mistyping
Tested on LAB. As KLAPEK says "URL filter is 'allow' not 'exempt' so it will be block on step 2: FortiGuard Category. "
A is the correct answer
A is correct
A 100%
100% A is correct
Correct answer: A
D is correct - 'Allow' -> destination is allowed from the static URL list, FortiGate proceeds with checking the category to decide further action.
URL filter goes First
I agree with tururu1496.
action allow, not exempt in URL list
A: Allow The traffic is passed to the remaining FortiGuard web filters, web content filters, web script filters, antivirus proxy operations, and DLP proxy operations. If the URL does not appear in the URL list, the traffic is permitted.
A the order is URL filter 2. FortiGuard Web Filtering 3. Web content filter 4. Web script filter 5. Antivirus scanning But to be allowed without matching any other critiria it should be exempt and not allowed
Order of operation is: 1. URL filter 2. FortiGuard Web Filtering 3. Web content filter 4. Web script filter 5. Antivirus scanning URL filter = ALLOW continues to evaluate the next steps, incl. Web Filtering. If it is required to Allow access to a site regardless of the category, then use "Exempt". https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632
Answer - A - - 'Allow' -> destination is allowed from the static URL list, FortiGate proceeds with checking the category to decide further action. - 'Exempt' -> destination is exempted from further inspection and traffic is allowed.
C, because blocked by content filter (exempt)
Exempt The traffic is allowed to bypass the remaining FortiGuard web filters, web content filters, web script filters, antivirus scanning, and DLP proxy operations. Block The FortiGate denies or blocks attempts to access any URL that matches the URL pattern. A replacement message is displayed. Allow The traffic is passed to the remaining FortiGuard web filters, web content filters, web script filters, antivirus proxy operations, and DLP proxy operations. If the URL does not appear in the URL list, the traffic is permitted. Monitor The traffic is processed the same way as the Allow action. For the Monitor action, a log message is generated each time a matching traffic pattern is established.
D is the correct answer following the order based on which FGT decide
My bad, the action is 'allow' and not 'exempt' so the URL will be blocked by Category filter
https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632
fortigate does it in order Static URL -> FortiGuard – > Content -> Advanced
D is correct
I would say it's D as per the study material, I don't see the exempt option mentioned in the theory or lab guide
In a real exam question there should be mentioned that dropbox.com is in the category file sharing and storage
Yes it is mentioned, overlooked it...
Static URL Filter will executed first
D is correct
D - 100%
The url filter is the first consider and is a example of the use of this.
The answer is D. Testedin my on environment.
D - 100%
A, see: https://docs.fortinet.com/document/fortigate/6.2.15/cookbook/615462/url-filter
A is correct. if both FortiGuard category based filter and Static URL filter are used, if it is required to Allow access to a site regardless of the category, then use "Exempt"
D, es correcta
D Enterprise_Firewall_7.0_Study_Guide-Online.pdf page 351
From the Study Guide, it appears that D was the correct answer - but after reading this article, A is actually correct: https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-Static-URL-filter-actions-explained/ta-p/206632
The correct Answer is D base on the Enterprise_Firewall_7.0_Study_Guide-Online.pdf page 351
URL filter is set to 'allow' which will permit it and move on to Fortiguard which is set to block. Web Content never gets used. If URL filter were set to 'exempt' it would be allowed.
I've been testing this settings in LAB enviroment and the results is a blocked connection.