New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet FCP_FGT_AD-7.6 Exam - Topic 4 Question 5 Discussion

Actual exam question for Fortinet's FCP_FGT_AD-7.6 exam
Question #: 5
Topic #: 4
[All FCP_FGT_AD-7.6 Questions]

You have created a web filter profile named restrict_media-profile with a daily category usage quota.

When you are adding the profile to the firewall policy, the restrict_media-profile is not listed in the available web profile drop down.

What could be the reason?

Show Suggested Answer Hide Answer
Suggested Answer: B

Web filter profiles with category usage quotas require the firewall policy to be in proxy-based (deep) inspection mode; if the inspection mode does not match this requirement, the profile will not appear in the drop-down list.


Contribute your Thoughts:

0/2000 characters
Jeffrey
2 months ago
D? Really? That sounds a bit far-fetched.
upvoted 0 times
...
Tiara
2 months ago
C could be the issue too, I've seen that happen.
upvoted 0 times
...
Tula
3 months ago
Wait, is it really that complicated?
upvoted 0 times
...
Ronny
3 months ago
I think B makes more sense here.
upvoted 0 times
...
Casie
3 months ago
A is definitely a possibility.
upvoted 0 times
...
Marshall
3 months ago
I doubt the naming convention would restrict it, but I guess it's possible. I would focus more on the inspection mode or if it's already referenced.
upvoted 0 times
...
Elliot
4 months ago
I practiced a question similar to this, and I think the inspection mode being set incorrectly could definitely be the issue. So, option A might be it.
upvoted 0 times
...
Marget
4 months ago
I'm not entirely sure, but I think if the profile is already in use, it could explain why it’s not showing up. That makes me lean towards option C.
upvoted 0 times
...
Kerry
4 months ago
I remember something about inspection modes affecting profile visibility, so maybe option B is the right choice?
upvoted 0 times
...
Lashaunda
4 months ago
Hmm, I'm a bit confused. Could it be that the firewall policy is in no-inspection mode instead of deep-inspection? That might be why the web filter profile isn't showing up. I'll need to verify the inspection mode settings.
upvoted 0 times
...
Eladia
4 months ago
Ah, I think I know what the problem could be. The web filter profile might already be referenced in another firewall policy, which would prevent it from being listed in the dropdown. I'll make sure to check that.
upvoted 0 times
...
Justa
4 months ago
Okay, let's see here. The question mentions a daily category usage quota, so I'm guessing the inspection mode in the firewall policy might not be matching the web filter profile feature set. I'll have to double-check that.
upvoted 0 times
...
Lynette
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the details about the web filter profile and firewall policy settings to figure out what could be causing the issue.
upvoted 0 times
...
Amber
6 months ago
I'm going with option B. Inspection mode has to match, or else it's just not going to work. It's like trying to fit a square peg in a round hole.
upvoted 0 times
Candida
5 months ago
I think it's option B too. The inspection mode needs to match for it to work properly.
upvoted 0 times
...
...
Caprice
7 months ago
I believe option C is also a possibility, if the profile is already referenced elsewhere.
upvoted 0 times
...
Coleen
7 months ago
I agree with Bernardine, the inspection mode might not be matching.
upvoted 0 times
...
Adolph
7 months ago
Wait, is this a trick question? What if the real answer is that the web filter profile was named after a celebrity, and the firewall just can't handle that level of fame?
upvoted 0 times
Pok
6 months ago
B) The inspection mode in the firewall policy is not matching with web filter profile feature set.
upvoted 0 times
...
Laine
7 months ago
A) The firewall policy is in no-inspection mode instead of deep-inspection.
upvoted 0 times
...
...
Shelba
7 months ago
I bet the naming convention is the problem. Someone must have used some crazy characters that the firewall doesn't like.
upvoted 0 times
...
Remedios
8 months ago
The inspection mode must be matching the web filter profile. That's probably the issue here. No-inspection mode won't cut it.
upvoted 0 times
Lawrence
7 months ago
B) The inspection mode in the firewall policy is not matching with web filter profile feature set.
upvoted 0 times
...
Lorean
7 months ago
A) The firewall policy is in no-inspection mode instead of deep-inspection.
upvoted 0 times
...
...
Junita
8 months ago
The web filter profile is probably already referenced in another firewall policy. That's the most likely reason it's not showing up in the dropdown.
upvoted 0 times
Grover
6 months ago
C) The web filter profile is already referenced in another firewall policy.
upvoted 0 times
...
Tawny
7 months ago
B) The inspection mode in the firewall policy is not matching with web filter profile feature set.
upvoted 0 times
...
Tuyet
7 months ago
A) The firewall policy is in no-inspection mode instead of deep-inspection.
upvoted 0 times
...
...
Bernardine
8 months ago
I think the reason could be option B.
upvoted 0 times
...

Save Cancel